4

I am into HL7 parser development and still learning HL7. Read articles regarding Orders but still not clear about how to identify the HL7 order request corresponding to HL7 order response message.

Additional Info: About 'MessageControlId' in MSH segment: The receiving system echoes 'MessageControlId'(10th field of MSH segment) back to the sending system in the Message acknowledgment segment(MSA). By using this ID we can identify the ACK corresponding to the request. Need to confirm whether response message will also contain this message id.

It would be greatly appreciated if someone could provide some sample ORM and corresponding ORR messages.

Vidya
  • 196
  • 14

1 Answers1

1

The ORM message type was deprecated in version 2.4 and withdrawn in 2.7 so you really shouldn't be using it at all any more. But if you do decide to use it, the matching ORM and ORR messages should have the same value in the ORC-2 (placer order number) field. Note that for a single real world order there may be multiple ORM and ORR messages.

Nick Radov
  • 401
  • 2
  • 7
  • Thanks for your reply. – Vidya Dec 18 '15 at 06:29
  • Hi Nick, Can you able to provide some samples. Also what will be **type of response message** for ORM. (ORM for request , ORR for acknowledgment...) – Vidya Dec 18 '15 at 09:30
  • You can find a partial ORM sample in the HL7 2.6 Standard section 4.6.1. https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185 – Nick Radov Dec 18 '15 at 18:39
  • 1
    Indicating that this is a moot point since ORM is deprecated in later versions in 2.4 is not a safe assumption. Many EHR and LIS/RIS/*IS systems still run using HL7 v2.3, including Epic. ORMs are still very relevant as a day-to-day HL7 implementer. – Mark Olschesky Jun 08 '16 at 15:08