version 2.5.1 question

[Kevin Crist]

Here is a test message from our lab for our 2.5.1 version and it’s kind of crazy looking. Can anyone explain what the # is that is in the encoding characters?  

MSH|^~&#|OSC Harvest^2.16.840.1.113883.3.1833.2^ISO|OSC Harvest DB^2.16.840.1.113883.3.1833.2.1.1035.1408673021^ISO|||20141204153613-0500||ORU^R01^ORU_R01|2A03D9E892BDFC4D85E91D43FDAF22BE|P|2.5.1|||AL|NE|||||LRI_Common_Component^HL7^2.16.840.1.113883.9.16^ISO~LRI_NG_Component^HL7^2.16.840.1.113883.9.13^ISO~LRI_RU_Component^HL7^2.16.840.1.113883.9.14^ISO

SFT|Orchard Software Corporation^L^^^^Orchard Software&2.16.840.1.113883.3.1833.1&ISO^XX^^^OSC123|9.0|OSC Harvest|140627.140828||20140904

PID|1||121772^^^^MR~^^^SSN&2.16.840.1.113883.4.1&ISO^SS^SSA&2.16.840.1.113883.3.184&ISO||LORD^STAR||19790505|M||WHIT^White^L^^^^1408673021|2123 GOTG DRIVE^^Bruceville^IN^47516||^PRN^^^^000^1001000|^WPN^^^^002^0020002||||||||1^HISPANIC^L^^^^1408673021||||||||N

PV1|1|U|||||||||||||||||9129004611^^^^VN|||||||||||||||||||||||||20141204145725

ORC|RE|L65738-1|221^1035O.5.21^2.16.840.1.113883.3.1833.2.5.21.1035.1408673021^ISO|||||||||2057^STINE^SCOTT^^^^^^^^^^PRN||^^FX^^^^8852758

OBR|1|L65738-1|221^1035O.5.21^2.16.840.1.113883.3.1833.2.5.21.1035.1408673021^ISO|5902-2^^LN^INRPT^PROTIME TEST^L^^1408673021^PROTIME TEST|||20141204153515|20141204153515||||||||2057^STINE^SCOTT^^^^^^^^^^PRN|^^FX^^^^8852758|COAG||3058037||20141204153603-0500|||F

OBX|1|SN|5902-2^^LN^PTPAT^PROTIME TEST^L^^1408673021^PROTIME TEST||^12.1|secs^^L^^^^1408673021|9.3-11.7|H|||F|||20141204153515|||||20141204153539||||GOOD SAMARITAN HOSPITAL

OBX|2|SN|NMN^NORMAL PATIENT MEAN^L^^^^1408673021^^NORMAL PATIENT MEAN||^10.5|secs^^L^^^^1408673021|10.5-10.5||||F|||20141204153515|||||||||GOOD SAMARITAN HOSPITAL

OBX|3|SN|6301-6^^LN^INRV^INR^L^^1408673021^INR||^1.2|NA^^HL70353^^^^2.5.1|0.9-1.2||||F|||20141204153515|||||20141204153539||||GOOD SAMARITAN HOSPITAL

NTE|1||INR/Prothrombin Time Condition:   Recommended INR:~********************************  ****************~Prevention or Treatment of DVT       2.0 – 3.0~Prevention of Systemic Embolism      2.0 – 3.0~Tissue Heart Valves                  2.0 – 3.0~Mechanical Heart Valves              2.5 – 3.5~Normal INR range for patients~not on anticoagulants                0.9 – 1.1~

SPM|1|^C30&1035O.5.242&2.16.840.1.113883.3.1833.2.5.242.1035.1408673021&ISO||56^PLASMA^L^^^^1408673021^^PLASMA|||||||P^Patient^HL70369^P^Patient^L^2.5.1^V1||||||20141204153515^20141204153515|20141204153515

Topic

[Jim Kosloskey]

Well I don’t think that was added for 2.5.1 I think it was added in a later version of HL/7 —- but —-

That is the new truncation character (it has its own prescribed escape sequence as well).

If a field is being truncated the charcter can be put as the last character of the field to indcate to the receiving system the field has been truncated.

Cloverleaf (at least 6.0.0) does not do anything with that such as placing that character in the field if the field is being truncated for you.

Now you need to ask the Lab if they actuallly use that in their messages and decide what you are going to do about it.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Kevin Crist]

i questioned them about it and they told me “. A new delimiter was introduced with v2.5.1 that will be sent in the MSH Header. ” We are doing v2.5.1 for immunizations and syndromic to the state and those dont have the # in them but those come from mckesson. Will this effect anything if i try to send to an application that doesnt support v.2.5.1? Since these are lab results we send them to many places.

[Jim Kosloskey]

Actually the truncation encoding character was not defined until 2.7.

However, some vendors have deployed ‘early adoption’ which I think is a euphamism for ‘we don’t want to spend the time, effort, or money to actuallly adopt the 2.7 standard – we just want to cherry pick what we want’.

In any case, the impact downstream vis-a-vis the MSH-2 is really dependent on the receiving systems. So I think an impact analysis is in order.

A more thorny issue is probably if they actually use that character in any fields to indicate the field has been truncated – I think you need to get clarification from the source system on that one and then react accordingly (may be another more intricatee impact analysis).

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Charlie Bursell]

Just for kicks, I experimented with this.

If it is a 2.5.1 message with the # separator character and you sent it through a Xlate configured as 2.5.1 in and out  the Xlate engine will strip off the # in the output.  I did a BULKCOPY followed by a simple copy.

If you define the in and out as 2.7 in your Xlate configuration, the # will be maintained even though it is a 2.5.1 message.

The bottom line is, how do you want to send it on, with or without the #?

[Author]

Replies