search

rbeckman-nextgen / test-mc5

0 stars 0 forks source link

MSH Segment 9 Not accepting MDM^T02 in the transformer #39

Closed rbeckman-nextgen closed 4 years ago

rbeckman-nextgen commented 4 years ago

When using the transformer and the sample hl7 below MDM is not a acceptable in MSH segment 9. Is this going to be corrected in the next release or is there a work around for this.

MSH|^~\&|SCW|WMC|COR||20060906102411||MDM^T02|0|C|2.2|||AL PID|||003000048474||Funny^Name||19800528|F||||||||||003000048474|555-11-1234||| OBR|||2443285|01|||200408182027|200408181738|||||||||||||||||U|||35709^^A~40246^^A~69||||040246|||JLG OBX|1|TX|01|1|Text Information goes here||||||P

Imported Issue. Original Details: Jira Issue Key: MIRTH-55 Reporter: dmcriane Created: 2006-09-20T08:47:12.000-0700

rbeckman-nextgen commented 4 years ago

Mirth can not parse the message because it is not valid HL7 (according to our parser).

Try this:

MSH|^~\&|SCW|WMC|COR||20060906102411||MDM^T02|0|C|2.3|||AL PID|||003000048474||Funny^Name||19800528|F||||||||||003000048474|555-11-1234||| OBR|||2443285|01|||200408182027|200408181738|||||||||||||||||U|||35709^^A~40246^^A~69||||040246|||JLG OBX|1|TX|01|1|Text Information goes here||||||P

By changing the version to 2.3, Mirth is able to process and parse the message. I'll have to do more research, but it appears that our parser doesn't have MDMT02 defined for HL7 v2.2, but for 2.3, 2.4, 2.5.

If you have no control over the incoming messages, there will be a way to handle this in the next Mirth release. See MIRTH-32

Imported Comment. Original Details: Author: chrisl Created: 2006-09-20T09:35:06.000-0700

rbeckman-nextgen commented 4 years ago

Message was invalid (version 2.2 rather than 2.3)

Imported Comment. Original Details: Author: chrisl Created: 2006-10-04T14:57:05.000-0700