- This topic has 7 replies, 5 voices, and was last updated 7 years, 3 months ago by .
I’m running Cloverleaf 5.5 rev1 on Red Hat Linux.
We’re bringing up a new vendor who is our first using HL7 2.5.1. They are using the new convention for coding message type in MSH-9, which now has 3 components: message type, event, and message structure. Here is a sample: ORU^R01^ORU_R01
Cloverleaf is not accepting this message and sends it to the database with state 101. Per the standard the vendor is correct. To verify that this is the problem, I replayed the message without the 3rd component and it worked.
I have HL7 selected as my TRXID determination, but in this version you may not select a variant. Is there a way for Cloverleaf to recognize this message type (short of stripping off the 3rd component)?
- The forum ‘Cloverleaf’ is closed to new topics and replies.