Chapter 04: Order Entry

This chapter covers orders for tests, drugs and diets. It defines the messages that place, change or cancel an order.

This chapter covers orders. An order is a request for a test, a drug, a diet or a supply. It also covers the messages that change, cancel or confirm an order. The main message type is ORM. The ORC segment carries the parts common to every order. Other segments carry the details of each kind of order, such as OBR for a test. The result of an order is not here. It is in chapter 7.

What is in this chapter

• 43 trigger eventsthe real-world things that cause one of these messages to be sent
• 20 segmentsthe lines these messages are built from, and the fields on each
• 58 code tablesthe value sets the fields in this chapter draw from
• 40 message typesBPS, BRP, BRT, BTS, OMB, OMD, OMG, OMI, OML, OMN, OMP, OMS, ORB, ORD, ORG, ORI, ORM, ORN, ORP, ORR, ORS, OSQ, OSR, RAR, RAS, RDE, RDR, RDS, RER, RGR, RGV, ROR, RRA, RRD, RRE, RRG, VXQ, VXR, VXU, VXX

Message types defined here

• BPSBlood product dispense status message

  1 structure, fired by 1 trigger event.

• BRPBlood product dispense status acknowledgement message

  1 structure, fired by 1 trigger event.

• BRTBlood product transfusion/disposition acknowledgement message

  1 structure, fired by 1 trigger event.

• BTSBlood product transfusion/disposition message

  1 structure, fired by 1 trigger event.

• OMBBlood product order message

  1 structure, fired by 1 trigger event.

• OMDDietary order

  1 structure, fired by 1 trigger event.

• OMGGeneral clinical order message

  1 structure, fired by 1 trigger event.

• OMIImaging order

  1 structure, fired by 1 trigger event.

• OMLLaboratory order message

  3 structures, fired by 3 trigger events.

• OMNNon-stock requisition order message

  1 structure, fired by 1 trigger event.

• OMPPharmacy/treatment order message

  1 structure, fired by 1 trigger event.

• OMSStock requisition order message

  1 structure, fired by 1 trigger event.

• ORBBlood product order acknowledgement message

  1 structure, fired by 1 trigger event.

• ORDDietary order acknowledgment message

  1 structure, fired by 1 trigger event.

• ORGGeneral clinical order acknowledgment message

  1 structure, fired by 1 trigger event.

• ORIImaging order acknowledgement message

  1 structure, fired by 1 trigger event.

• ORMPharmacy/treatment order message

  1 structure, fired by 1 trigger event.

• ORNNon-stock requisition - General order acknowledgment message

  1 structure, fired by 1 trigger event.

• ORPPharmacy/treatment order acknowledgment message

  1 structure, fired by 1 trigger event.

• ORRGeneral order response message response to any ORM

  1 structure, fired by 1 trigger event.

• ORSStock requisition - Order acknowledgment message

  1 structure, fired by 1 trigger event.

• OSQQuery response for order status

  1 structure, fired by 1 trigger event.

• OSRQuery response for order status

  1 structure, fired by 1 trigger event.

• RARPharmacy/treatment administration information

  1 structure, fired by 1 trigger event.

• RASPharmacy/treatment administration message

  1 structure, fired by 1 trigger event.

• RDEPharmacy/treatment encoded order message

  1 structure, fired by 2 trigger events.

• RDRPharmacy/treatment dispense information

  1 structure, fired by 1 trigger event.

• RDSPharmacy/treatment dispense message

  1 structure, fired by 1 trigger event.

• RERPharmacy/treatment encoded order information

  1 structure, fired by 1 trigger event.

• RGRPharmacy/treatment dose information

  1 structure, fired by 1 trigger event.

• RGVPharmacy/treatment give message

  1 structure, fired by 1 trigger event.

• RORPharmacy/treatment order response

  1 structure, fired by 1 trigger event.

• RRAPharmacy/treatment administration acknowledgment message

  1 structure, fired by 1 trigger event.

• RRDPharmacy/treatment dispense acknowledgment message

  1 structure, fired by 1 trigger event.

• RREPharmacy/treatment encoded order acknowledgment message

  1 structure, fired by 2 trigger events.

• RRGPharmacy/treatment give acknowledgment message

  1 structure, fired by 1 trigger event.

• VXQQuery for vaccination record

  1 structure, fired by 1 trigger event.

• VXRVaccination record response

  1 structure, fired by 1 trigger event.

• VXUUnsolicited vaccination record update

  1 structure, fired by 1 trigger event.

• VXXResponse for vaccination query with multiple PID matches

  1 structure, fired by 1 trigger event.

Segments defined here

These 20 segments are defined in chapter 04. Messages in other chapters may still carry them.

• BLGBilling Segment
• BPOBlood Product Order Segment
• BPXBlood Product Dispense Status Segment
• BTXBlood Product Transfusion/Disposition Segment
• IPCImaging Procedure Control Segment
• OBRObservation Request Segment
• ODSdietary orders, supplements, and preferences segment
• ODTdiet tray instructions segment
• ORCCommon Order Segment
• RQ1Requisition Detail-1 Segment
• RQDRequisition Detail Segment
• RXAsegment usage in vaccine messages
• RXCPharmacy/Treatment Component Order Segment
• RXDPharmacy/Treatment Dispense
• RXEPharmacy/Treatment Encoded Order Segment
• RXGPharmacy/Treatment Give Segment
• RXOPharmacy/Treatment Order Segment
• RXRPharmacy/Treatment Route Segment
• TQ1Timing/Quantity Segment
• TQ2Timing/Quantity Relationship

Trigger events

A trigger event is the thing that happens in the hospital and causes a message to be sent. Chapter 04 defines 43 of them.

• O01general order message
• O02general order response message response to any ORM
• O03Dietary Order
• O04dietary order acknowledgment
• O05stock requisition order message
• O06stock requisition order acknowledgment message
• O07non-stock requisition order message
• O08non-stock requisition order acknowledgment message
• O09Pharmacy/Treatment Order Message
• O10Pharmacy/Treatment Order Acknowledgment
• O11Pharmacy/Treatment Encoded Order Message
• O12Pharmacy/Treatment Encoded Order Acknowledgment
• O13Pharmacy/Treatment Dispense Message
• O14Pharmacy/Treatment Dispense Acknowledgement Message
• O15Pharmacy/Treatment Give Message
• O16Pharmacy/Treatment Give Acknowledgment Message
• O17Pharmacy/Treatment Administration Message
• O18Pharmacy/treatment administration acknowledgment
• O19general clinical order message
• O20general clinical order acknowledgement message
• O21laboratory order message
• O23Imaging Order Message
• O24Imaging Order Response Message To Any OMI
• O25Pharmacy/Treatment Refill Authorization Request Message
• O26Pharmacy/Treatment Refill Authorization Acknowledgement
• O27Blood Product Order Message
• O28Blood Product Order Acknowledgment
• O29Blood Product Dispense Status Message
• O30Blood Product Dispense Status Acknowledgment
• O31Blood Product Transfusion/Disposition Message
• O32Blood Product Transfusion/Disposition Acknowledgment
• O33Laboratory order for multiple orders related to a single specimen
• O35Laboratory order for multiple orders related to a single container of a specimen
• Q06query response for order status
• RAR
• RDR
• RER
• RGR
• RORPharmacy prescription order query response
• V01Query For Vaccination Record
• V02Response to vaccination query returning multiple PID matches
• V03Vaccination Record Response
• V04Unsolicited Vaccination Record Update

Other chapters

• 02Control
• 03Patient Administration
• 05Query
• 06Financial Management
• 07Observation Reporting
• 08Master Files
• 09Medical Records/Information Management
• 10Scheduling
• 11Patient Referral
• 12Patient Care
• 13Clinical Laboratory Automation
• 14Application Management
• 15Personnel Management