Chris:
Your idea is similar to another problem in this area: unique
identification of patient specimens for clinical lab procedures. This was
brought up in ASTM E-31 but was completed in CLSI (which is probably now a
working member of the new HITSP). Such a broad common convention should be
developed and adopted by one of the HITSP SDOs through participation of
all stakeholders. Nancy is a member of ASTM E-31, as is the VA, and this
could easily be introduced at the November ASTM E-31 meeting after the
upcoming VCM where the groundwork can be done. The ability to coordinate
this also with HL7 is in place and also communication with the
ONCHIT-established new guidance council. This is the way to get a
convention that will work and benefit all. I can work with Nancy on the
ASTM part if you and others can draft the basic rationale based on
existing examples and CMS input. I will look for my early versions of the CLSI
std and, if we need to we may be able to get the documents with ASTM
help. Let me know after this morning's CC.
Arden
On Thu, 6 Oct 2005, Chris Richardson wrote:
Cameron,
Couldn't we just create a new identifier segment that uses a number which
is unique to every medical facility in the world, their international
telephone number. If the string is 3 digits, then it is VA. If it is 7 or
more digits, then it is a non-VA faility. Isn't this a characteristic of
HL7 segment elements?
If this field is rigidly 3 characters, then couldn't we just define a
whole new HL7 record with that field of that segment defined as a string
rather than 3 numerics. Won't that work??
----- Original Message -----
From: "Cameron Schlehuber" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, October 06, 2005 11:31 AM
Subject: RE: [Hardhats-members] Station Numbers for institutions in VOE
The STATION NUMBER field should be kept as is for VA and be null for non-VA
sites. There is an IDENTIFIER sub-file field 9999 that uses a CODING SYSTEM
(the entries to select from are established in collaboration with the VA HL7
administrator) and an ID unique to that Coding System. What we need to do
with VistA for VOE, OpenVistA, etc, is to identify the places in code where
Institution identification should be based on that Code System-ID pair. I
know the Lab Service package has already had to embark on that effort since
lots of institutions with sharing agreements with VA do not have VA Station
Numbers.
Cameron Schlehuber
---------------------
JohnLeo Zimmer wrote:
Sent: Thursday, October 06, 2005 5:51 AM
Wouldn't it be more appropriate to provide a standard for station
numbers that can be generalized beyond the VA?. I had hoped that world
vista's open forum might serve that function.
Maybe the station number needs to be modified (with a alpha prefix
perhaps) to identify the side as VA vs Private Sector vs testbed, etc.
Robert DeWayne wrote:
Station numbers are a VA issue, we did not have time to eliminate this
code for VOE. This is a known issue. Why do you need a station number
for VOE?
Robert DeWayne
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
