Reference·ORC Segment·ORC-12
HL7 v2 Reference

HL7 v2 ORC-12 Field Guide: Ordering Provider Codes and Common Mistakes

Jul 27, 2026 · 4 min read
← ORC-9

ORC-12 and the ordering provider field on OBR are populated independently by most sending systems, so a covering-provider substitution applied to one doesn't always make it into the other — and reports built off just one of the two can quietly name the wrong physician.

Quick answer

ORC-12 is the twelfth field of the HL7 v2 ORC segment — it identifies the provider responsible for the order at the ORC level, using the same XCN component structure (ID, family name, given name, credentials) as provider fields elsewhere in HL7 v2.

What this field contains

Component 1
provider ID number, usually an internal or NPI identifier
Component 2
family name
Component 3
given name
Component 4
middle initial
Component 7
degree or credential suffix, e.g. MD

Example

Synthetic example Generated by Synthibase
ORC|NW|ORD44219^SYNTHIB|FIL98831^SYNTHIB||IP||||20260726090000|||3021^HAYES^DEREK^A^^^MD

3021^HAYES^DEREK^A^^^MD in the twelfth field identifies Dr. Derek A. Hayes as the ordering provider. Synthetic provider — not a real person.

Where this trips people up

Because ORC and OBR each carry their own ordering-provider field, some sending systems populate them from different sources — one from the order-entry screen, the other from the provider tied to the diagnostic service. Most of the time they match, but when a covering provider signs on behalf of the ordering physician, or an order gets amended, it's easy for only one of the two fields to get updated. Test data that always sets both fields identically will never surface a report or label that's pulling the stale provider name from the field nobody remembered to update.

How to Test HL7 v2 ORC: A Field-by-Field Breakdown
How to Write EDI Test Cases That Actually Catch Go-Live Failures
HL7 ADT Messages: A01 through A08 Explained
Test provider fields across ORC and OBR together
Synthibase generates synthetic order messages with realistic ordering-provider scenarios, including covering-provider substitutions, so mismatches between ORC-12 and OBR get caught in testing instead of in a clinical report.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.