The Common Order segment (ORC) is used to transmit data elements that are common to all orders (all types of services that are requested). The ORC segment is required in both the Order (ORM) and Order Acknowledgement (ORR) messages.
HL7 v2
If details are needed for a particular type of order segment (e.g., Pharmacy, Dietary), the ORC must precede any order detail segment (e.g., RXO, ODS). In some cases, the ORC may be as simple as the string ORC|OK|<placer order number>|<filler order number>|.
19
C.LenElementv2.1FHIR
1..2-IDR1011900215ORC-1Order Control216 mappings
2..75-CM_PLACERC1-00216ORC-2Placer Order Number313 mappings
3..75-CM_FILLERC1-00217ORC-3Filler Order Number312 mappings
4..75-CM_GROUP_IDO1-00218ORC-4Placer Group Number313 mappings
5..2-IDO1003800219ORC-5Order Status3status
6..1-IDO1012100220ORC-6Response Flag3-
7..200-TQO*-00221ORC-7Quantity / timing4$this
8..200-CM_EIPO1-00222ORC-8Parent3-
9..26-TSO1-00223ORC-9Date / time of transaction37 mappings
10..80-CN_PERSONO1-00224ORC-10Entered By33 mappings
11..80-CN_PERSONO1-00225ORC-11Verified By33 mappings
12..80-CN_PERSONO1-00226ORC-12Ordering Provider310 mappings
13..80-CM_UNDEFINEDO1-00227ORC-13Enterer's Location3-
14..40-TNO2-00228ORC-14Call Back Phone Number22 mappings
15..26-TSO1-00229ORC-15Order effective date / timeNEW-
16..200-CEO1-00230ORC-16Order Control Code ReasonNEW4 mappings
17..60-CEO1-00231ORC-17Entering OrganizationNEWagent[1].onBehalfOf(Organization)
18..60-CEO1-00232ORC-18Entering DeviceNEWagent[5].who(Device)
19..80-CN_PERSONO1-00233ORC-19Action byNEW3 mappings
4

Editorial Comments for ORC7

Field 12

= OBR-16 --> 4.3.1.12, 4.5.1.16

BSW
Field 14

= OBR-17 --> 4.3.1.14

BSW
Field 7

= OBR-27 --> 4.3.1.7

BSW
Field 3

= OBR-3 --> 4.3.1.3, 4.5.1.3

BSW
Field 2

= OBR-2 --> 4.3.1.2, 4.5.1.2

BSW
Field 8

= OBR-29 --> 4.3.1.8, 4.5.1.29

BSW
Field 9

--> 4.3.1.9

BSW