I've searched the faq and the entire site but was unable to find any hint about the following situation:
I'm trying to parse ORU R01 HL7 2.x messages with mirth 1.7
These are laboratory results in free text, and of course some OBX have OBX.5 (value) string elements like
" * CEFTAZIDIME <=8 S <=8 S"
It seems (after much fiddling!) that the mirth inbound message template parser will reject any message containing the "<" character no matter what I put for OBX.2 (value type) - I've tried TX and ST that I thought might allow those characters.
The ">" character is permitted, so I'm guessing it's not some confusion about XML delimiters.
I may be able to convince the people generating the message to do something about this, but I'm wondering if there's some value type I didn't yet try that will convince the parser to ignore any < characters inside an OBX.5?
Post edited by: fubar, at: 03/15/2008 13:32
Post edited by: fubar, at: 03/15/2008 13:33
Post edited by: fubar, at: 03/15/2008 13:33
Post edited by: fubar, at: 03/16/2008 10:47
I'm trying to parse ORU R01 HL7 2.x messages with mirth 1.7
These are laboratory results in free text, and of course some OBX have OBX.5 (value) string elements like
" * CEFTAZIDIME <=8 S <=8 S"
It seems (after much fiddling!) that the mirth inbound message template parser will reject any message containing the "<" character no matter what I put for OBX.2 (value type) - I've tried TX and ST that I thought might allow those characters.
The ">" character is permitted, so I'm guessing it's not some confusion about XML delimiters.
I may be able to convince the people generating the message to do something about this, but I'm wondering if there's some value type I didn't yet try that will convince the parser to ignore any < characters inside an OBX.5?
Post edited by: fubar, at: 03/15/2008 13:32
Post edited by: fubar, at: 03/15/2008 13:33
Post edited by: fubar, at: 03/15/2008 13:33
Post edited by: fubar, at: 03/16/2008 10:47
Comment