HLTH 2026Vorro is at HLTH 2026, Las Vegas, Nov 15–18. Bring your toughest interoperability problem.Book a meeting
HL7 v2Segment⏱ 9 min read

HL7 ORC Segment: Common Order

In short

HL7 ORC segment explained: a field-by-field reference for the Common Order, ORC-1 order control, placer and filler order numbers, ordering provider, and the FHIR ServiceRequest mapping.

Need this HL7 v2 feed built or fixed?Contact Us

The ORC segment carries the data common to every order, regardless of what is being ordered. It pairs with a detail segment (OBR for observations/labs, RXO for pharmacy, etc.): ORC holds the order control code, the placer and filler order numbers, who ordered it and when, while the detail segment describes the specific service. ORC-1 (Order Control) is the verb of the message - it says whether this is a new order, a cancellation, a status update, and so on.

Purpose

ORC communicates order-level control information shared across all order types: the action being taken (ORC-1), the placer/filler identifiers that correlate the order across systems, the ordering provider, timing, and the entering organization. It is the common header that precedes an order's type-specific detail segment.

Used in

ORC appears in all order messages: ORM (general orders), OMG/OML/OMP and other OMx order messages, ORU (results, to echo the originating order), RDE/RDS (pharmacy encoded order / dispense), and OMI (imaging). See ORM and ORU.

Field-by-field reference

Source: the Vorro HL7 segment database (extracted from the official v2-to-FHIR IG). R = required (cardinality min ≥ 1). Repeat = field may repeat. Length is not carried by the FHIR source and is shown as -.

SeqNameData TypeLengthReqRepeatTable #Description
ORC-1Order ControlID-R-HL70119The action: NW new, CA cancel, SC status change, etc. The order verb.
ORC-2Placer Order NumberEI-O--The placing system's order id.
ORC-3Filler Order NumberEI-O--The filling system's order id.
ORC-4Placer Group NumberEI-O--Groups related orders placed together.
ORC-5Order StatusID-O-HL70038Status of the order (e.g. IP, CM, CA).
ORC-6Response FlagID-O-HL70121Level of response requested.
ORC-7Quantity/TimingTQ-OY-Deprecated; superseded by TQ1/TQ2 in v2.5.
ORC-8Parent OrderEIP-OY-Links a child order to its parent.
ORC-9Date/Time of Order EventDTM-O--When the ORC action occurred.
ORC-10Entered ByXCN-OY-Who entered the order.
ORC-11Verified ByXCN-OY-Who verified the order.
ORC-12Ordering ProviderXCN-OY-The clinician who placed the order.
ORC-13Enterer's LocationPL-O--Where the order was entered.
ORC-14Call Back Phone NumberXTN-OY-Phone for order callback.
ORC-15Order Effective Date/TimeDTM-O--When the order takes effect.
ORC-16Order Control Code ReasonCWE-O-HL70949Reason for the ORC-1 action.
ORC-17Entering OrganizationCWE-O--Organization entering the order.
ORC-18Entering DeviceCWE-O--Device used to enter the order.
ORC-19Action ByXCN-OY-Person who took the action.
ORC-20Advanced Beneficiary Notice CodeCWE-O-HL70339ABN status (US billing).
ORC-21Ordering Facility NameXON-OY-Facility that placed the order.
ORC-22Ordering Facility AddressXAD-OY-Address of the ordering facility.
ORC-23Ordering Facility Phone NumberXTN-OY-Phone of the ordering facility.
ORC-24Ordering Provider AddressXAD-OY-Address of the ordering provider.
ORC-25Order Status ModifierCWE-O-HL70950Refines ORC-5.
ORC-26Advanced Beneficiary Notice Override ReasonCWE-O-HL70552Reason an ABN was overridden.
ORC-27Filler's Expected Availability Date/TimeDTM-O--When the filler expects results.
ORC-28Confidentiality CodeCWE-O--Confidentiality of the order.
ORC-29Order TypeCWE-O-HL70482Inpatient vs outpatient order.
ORC-30Enterer Authorization ModeCNE-O-HL70483How the enterer was authorized.
ORC-31Parent Universal Service IdentifierCWE-O--Parent order's service id.
ORC-32Advanced Beneficiary Notice DateDT-O--ABN date.
ORC-33Alternate Placer Order NumberCX-OY-Alternate placer id.
ORC-34Order Workflow ProfileCWE-OYHL70934Workflow profile for the order.
ORC-35Action CodeID-O--Add/update/delete action on the segment.
ORC-36Order Status Date RangeDR-O--Period the status applies to.
ORC-37Order Creation Date/TimeDTM-O--When the order was created.
ORC-38Filler Order Group NumberEI-O--Filler-assigned group id.

Most-used fields

  • ORC-1 Order Control is the action verb. NW (new), CA (cancel), OC (order cancelled), SC (status change), RU (replacement) - receivers branch on this before anything else.
  • ORC-2 Placer Order Number and ORC-3 Filler Order Number are the correlation keys that tie the placing and filling systems' views of the same order together.
  • ORC-12 Ordering Provider identifies the responsible clinician and feeds care-team and result-routing logic.
  • ORC-5 Order Status reports lifecycle state and is often kept in sync with the detail segment's status.

Version differences (2.3 to 2.8.2)

  • 2.5: ORC-7 Quantity/Timing (TQ) deprecated in favor of the dedicated TQ1/TQ2 segments; new orders should use TQ1.
  • 2.5/2.6: ORC-29 Order Type, ORC-30 Enterer Authorization Mode, ORC-31 Parent Universal Service Identifier added.
  • 2.7+: ORC-32 through ORC-38 added (ABN date, alternate placer order number, workflow profile, action code, status date range, creation date, filler order group number).
  • Older receivers ignore trailing fields they do not recognize.

Common mistakes

  • Ignoring ORC-1 and inferring intent from the detail segment - the order control code is authoritative.
  • Correlating only on ORC-2 when the filler responds on ORC-3 (or vice versa); track both.
  • Continuing to populate ORC-7 instead of TQ1 in v2.5+ interfaces.
  • Dropping repeating provider fields (ORC-10/11/12/19) to a single value.

Examples

Minimal valid ORC (new order):

ORC|NW|PON12345^MERCYGEN

Fully-populated ORC:

ORC|NW|PON12345^MERCYGEN|FON98765^LAB||IP||||20260609130000|JDOE^DOE^JANE|JVER^VER^JOHN|1234^SMITH^JANE^A^^^MD|3WEST^^^MERCYGEN|^^PH^^^555^5550100|20260609130000

Annotated breakdown of the fully-populated example (selected fields):

ORC                              ← segment ID
NW                               ← ORC-1  Order Control (New order)
PON12345^MERCYGEN                ← ORC-2  Placer Order Number
FON98765^LAB                     ← ORC-3  Filler Order Number
IP                               ← ORC-5  Order Status (In Process)
20260609130000                   ← ORC-9  Date/Time of Order Event
JDOE^DOE^JANE                    ← ORC-10 Entered By
1234^SMITH^JANE^A^^^MD           ← ORC-12 Ordering Provider
3WEST^^^MERCYGEN                 ← ORC-13 Enterer's Location

In-context inside an ORM^O01 (order, ORC + OBR):

MSH|^~&|CPOE|MERCYGEN|LAB|MERCYGEN|20260609130000||ORM^O01^ORM_O01|MSG201|P|2.5.1
PID|1||MR12345^^^MERCYGEN^MR||DOE^JOHN^Q||19800101|M
ORC|NW|PON12345^MERCYGEN|||IP||||20260609130000||1234^SMITH^JANE^A^^^MD
OBR|1|PON12345^MERCYGEN||CBC^Complete Blood Count^L

In-context inside an ORU^R01 (result, ORC echoes the order):

MSH|^~&|LAB|MERCYGEN|EHR|MERCYGEN|20260609150000||ORU^R01^ORU_R01|MSG305|P|2.5.1
PID|1||MR12345^^^MERCYGEN^MR||DOE^JOHN^Q||19800101|M
ORC|RE|PON12345^MERCYGEN|FON98765^LAB
OBR|1|PON12345^MERCYGEN|FON98765^LAB|CBC^Complete Blood Count^L
OBX|1|NM|718-7^Hemoglobin^LN||13.5|g/dL|13.0-17.0|N|||F

FHIR mapping

Primary target resource: ServiceRequest. ORC also maps to Provenance (who entered/verified/authored, derived from ORC-1/9/10/11/12), and contributes to DiagnosticReport, Immunization, and MedicationAdministration depending on the order context. Official ConceptMaps: ServiceRequest, DiagnosticReport, Immunization, MedicationAdministration, Provenance.

Key ServiceRequest mappings:

ORC fieldFHIR target (ServiceRequest)
ORC-1 Order ControlServiceRequest.status + intent (+ businessEvent extension)
ORC-2 Placer Order NumberServiceRequest.identifier (type PLAC)
ORC-3 Filler Order NumberServiceRequest.identifier (type FILL)
ORC-4 Placer Group NumberServiceRequest.requisition (type PGN)
ORC-5 Order StatusServiceRequest.status
ORC-9 Date/Time of Order EventServiceRequest.authoredOn
ORC-12 Ordering ProviderServiceRequest.requester (Practitioner)
ORC-14 Call Back Phone Numberorder-callback-phone-number extension
ORC-16 Order Control Code Reasonrequest-statusReason extension
ORC-21 Ordering Facility Namerequester Organization
ORC-28 Confidentiality Codemeta.security
ORC-29 Order TypeServiceRequest.locationCode
ORC-33 Alternate Placer Order NumberServiceRequest.identifier (type PLAC)

Provenance: ORC-1 → Provenance.activity (CREATE/UPDATE/CANCEL); ORC-10/11/12 → Provenance.agent (enterer/verifier/author). Fields without a published target (ORC-6, ORC-13, ORC-15, ORC-25 through ORC-27, ORC-30 through ORC-32, ORC-34 through ORC-38) are control/billing details not represented on ServiceRequest.

Engine considerations

  • Required in practice: ORC-1 is required; most interfaces also require ORC-2 (placer) and the ordering provider (ORC-12).
  • Branch on ORC-1 first - cancel/replace actions must update or supersede the existing order, not create a new one.
  • Use ORC-2 and ORC-3 together as the correlation key across placer and filler systems.
  • In v2.5+ read timing from TQ1/TQ2, not the deprecated ORC-7.

How Vorro parses and produces ORC

Vorro routes on ORC-1, correlating orders by placer (ORC-2) and filler (ORC-3) numbers so updates and cancellations attach to the existing order. Repeating provider fields are preserved, timing is read from TQ1 in v2.5+ feeds, and on the FHIR side Vorro emits ServiceRequest with status/intent derived from ORC-1 plus a Provenance capturing who entered, verified, and authored the order.

  • OBR - the observation-request detail segment ORC pairs with.
  • OBX - the result observations that follow an order.
  • ORM messages - the order message ORC heads.

Sources

← Back to HL7 v2 Guide

Ready to Integrate This Into Your Workflow?

Talk to a Vorro expert about implementing HL7 v2 in your specific environment.