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>|.
24
C.LenElementv2.3FHIR
1..2-IDR1011900215ORC-1Order Control16 mappings
2..22-EIC1-00216ORC-2Placer Order Number213 mappings
3..22-EIC1-00217ORC-3Filler Order Number12 mappings
4..22-EIO1-00218ORC-4Placer Group Number13 mappings
5..2-IDO1003800219ORC-5Order Statusstatus
6..1-IDO1012100220ORC-6Response Flag-
7..200-TQO1-00221ORC-7Quantity/TimingOptionality$this
8..200-EIPO1-00222ORC-8ParentData Type-
9..26-TSO1-00223ORC-9Date/Time of TransactionOptionality7 mappings
10..120-XCNO*-00224ORC-10Entered ByRepetition3 mappings
11..120-XCNO*-00225ORC-11Verified ByRepetition3 mappings
12..120-XCNO*-00226ORC-12Ordering Provider10 mappings
13..80-PLO1-00227ORC-13Enterer’s LocationName-
14..40-XTNO2-00228ORC-14Call Back Phone NumberData Type2 mappings
15..26-TSO1-00229ORC-15Order Effective Date/TimeOptionality-
16..200-CEO1-00230ORC-16Order Control Code Reason4 mappings
17..60-CEO1-00231ORC-17Entering Organizationagent[1].onBehalfOf(Organization)
18..60-CEO1-00232ORC-18Entering Deviceagent[5].who(Device)
19..120-XCNO*-00233ORC-19Action ByRepetition3 mappings
20..40-CE_0339O1033901310ORC-20Advanced Beneficiary Notice CodeNEW-
21..60-XONO*-01311ORC-21Ordering Facility NameNEW2 mappings
22..106-XADO*-01312ORC-22Ordering Facility AddressNEW2 mappings
23..48-XTNO*-01313ORC-23Ordering Facility Phone NumberNEW2 mappings
24..106-XADO*-01314ORC-24Ordering Provider AddressNEW2 mappings
32