The Common Order segment (ORC) is used to transmit fields that are common to all orders (all types of services that are requested). The ORC segment is required in the Order (ORM) message. ORC is mandatory in Order Acknowledgment (ORR) messages if an order detail segment is present, but is not required otherwise.
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.2FHIR
1..2-IDR1011900215ORC-1Order Control16 mappings
2..22-EIO*-00216ORC-2Placer Order Number413 mappings
3..22-EIC1-00217ORC-3Filler Order Number212 mappings
4..22-EIO1-00218ORC-4Placer Group Number313 mappings
5..2-IDO1003800219ORC-5Order StatusOptionalitystatus
6..1-IDO1012100220ORC-6Response FlagOptionality-
7..200-TQR1-00221ORC-7Quantity/Timing3$this
8..200-CM_EIPO1-00222ORC-8ParentOptionality-
9..26-TSO1-00223ORC-9Date/Time of TransactionName7 mappings
10..120-XCNO1-00224ORC-10Entered By33 mappings
11..120-XCNO1-00225ORC-11Verified By33 mappings
12..120-XCNO*-00226ORC-12Ordering Provider410 mappings
13..80-PLO1-00227ORC-13Enterer's Location2-
14..40-TNO2-00228ORC-14Call Back Phone NumberOptionality2 mappings
15..26-TSO1-00229ORC-15Order Effective Date/TimeName-
16..200-CEO1-00230ORC-16Order Control Code ReasonOptionality4 mappings
17..60-CEO1-00231ORC-17Entering OrganizationOptionalityagent[1].onBehalfOf(Organization)
18..60-CEO1-00232ORC-18Entering DeviceOptionalityagent[5].who(Device)
19..120-XCNO1-00233ORC-19Action By43 mappings
43