The ORG (Practitioner Organization Unit) segment ties a practitioner to a specific organizational unit and the provider role they hold within it. It is the third member of the staff master file trio: STF identifies the person, PRA describes their professional detail, and ORG places them inside an organization unit with a provider type, classification, and area of specialization. ORG is exchanged inside MFN^M02 master file notification messages so that receiving systems know not only who a practitioner is but where and in what capacity they operate.
Purpose
The purpose of ORG is to record the relationship between a practitioner and an organizational unit. It captures the organization unit code and type, whether the unit is the practitioner's primary affiliation, the practitioner's identifier within that unit, the health care provider type and classification codes, the area of specialization, the effective date range, and approval and primary-care indicators. Because ORG follows STF (and usually PRA) within a master file entry, the unit relationship it describes is understood to belong to the person identified upstream.
Used in
ORG is used in MFN^M02 Master File Notification messages for staff and practitioner records. It appears after the STF and PRA segments within a master file entry group, and a practitioner who works across several units may have multiple ORG segments, each sequenced by its Set ID.
Field-by-field reference
Source: HAPI HL7v2 v2.5.1 javadocs (ORG) for sequence, name, data type, and repetition. Length is not published in the javadocs (—); Required and Table # are filled from the HL7 v2.5.1 standard where well-established.
| Seq | Name | Data Type | Length | Req | Repeat | Table # | Description |
|---|---|---|---|---|---|---|---|
| ORG-1 | Set ID - ORG | si | — | R | — | — | Sequence number for repeated ORG segments |
| ORG-2 | Organization Unit Code | ce | — | O | — | HL70474 | Code identifying the organization unit |
| ORG-3 | Organization Unit Type Code | ce | — | O | — | HL70474 | Type of organization unit |
| ORG-4 | Primary Org Unit Indicator | id | — | O | — | HL70136 | Indicates whether this is the primary unit |
| ORG-5 | Practitioner Org Unit Identifier | cx | — | O | — | — | Practitioner identifier within the organization unit |
| ORG-6 | Health Care Provider Type Code | ce | — | O | — | HL70452 | Provider type within the unit |
| ORG-7 | Health Care Provider Classification Code | ce | — | O | — | HL70453 | Provider classification within the unit |
| ORG-8 | Health Care Provider Area of Specialization Code | ce | — | O | — | HL70454 | Area of specialization within the unit |
| ORG-9 | Effective Date Range | dr | — | O | — | — | Date range the relationship is effective |
| ORG-10 | Employment Status Code | ce | — | O | — | HL70066 | Employment status within the unit |
| ORG-11 | Board Approval Indicator | id | — | O | — | HL70136 | Indicates board approval of the relationship |
| ORG-12 | Primary Care Physician Indicator | id | — | O | — | HL70136 | Indicates a primary care physician role |
Most-used fields
ORG-1, ORG-2, ORG-5, and ORG-6 carry most of the practical value. ORG-1 (Set ID) sequences the unit relationships when a practitioner belongs to more than one. ORG-2 (Organization Unit Code) names the unit itself, which is the field directories and routing logic key on. ORG-5 (Practitioner Org Unit Identifier) supplies the identifier the practitioner is known by within that unit, often distinct from their global identifier. ORG-6 (Health Care Provider Type Code) classifies the role they hold there. ORG-4 (Primary Org Unit Indicator) and ORG-12 (Primary Care Physician Indicator) are widely used where one affiliation must be flagged as primary.
Version differences (2.3 to 2.8.2)
ORG was introduced in HL7 v2.4 to extend the staff master file with organization-unit context, arriving with the twelve fields documented here. Version 2.5 and 2.5.1 retained the structure unchanged. Through versions 2.6 to 2.8.2 the field set remained stable while several coded fields had their table bindings refined and were progressively expressed with the CWE complex type in later releases; the provider type, classification, and specialization codes continued to point at the well-established provider tables. A 2.5.1 ORG segment therefore parses without loss under later-version engines.
Common mistakes
A common mistake is omitting ORG-1, which the standard defines as required to sequence multiple unit relationships; without it, receivers cannot reliably order or de-duplicate the ORG segments. Another is treating ORG-5 as the practitioner's global identifier rather than the unit-scoped one, which can collide with STF-2 or PRA-6. Integrators sometimes flag more than one ORG segment as the primary unit via ORG-4, producing an ambiguous record. Finally, leaving the provider type, classification, and area-of-specialization codes (ORG-6 through ORG-8) as free text instead of table-bound codes undermines the downstream filtering those fields are designed to support.
Examples
A minimal valid ORG segment with only the Set ID and unit code:
ORG|1|CARD^Cardiology Unit^L
A fully populated ORG segment:
ORG|1|CARD^Cardiology Unit^L|DEPT^Department^L|Y|U778899^^^HOSP^PRN|208^Physician^HL70452|260^Specialist^HL70453|RC^Cardiology^HL70454|20100701^20300101|F^Full Time^HL70066|Y|N
Annotated breakdown of the key fields:
ORG|1|CARD^Cardiology Unit^L|DEPT^Department^L|Y|U778899^^^HOSP^PRN|208^Physician^HL70452|260^Specialist^HL70453|RC^Cardiology^HL70454
| | | | | | | |
| | | | | | | +--> ORG-8 Area of Specialization Code
| | | | | | +-------------------------> ORG-7 Provider Classification Code
| | | | | +-------------------------------------------------> ORG-6 Health Care Provider Type Code
| | | | +--------------------------------------------------------------------> ORG-5 Practitioner Org Unit Identifier
| | | +----------------------------------------------------------------------> ORG-4 Primary Org Unit Indicator
| | +----------------------------------------------------------------------------------------> ORG-3 Organization Unit Type Code
| +----------------------------------------------------------------------------------------------------------------> ORG-2 Organization Unit Code
+------------------------------------------------------------------------------------------------------------------> ORG-1 Set ID - ORG
In-context excerpt inside an MFN^M02 message, placing a practitioner in a unit:
MSH|^~&|HRSYS|HOSP|DIRSVC|HOSP|20260610091500||MFN^M02^MFN_M02|MSG00020|P|2.5.1
MFI|PRA^Practitioner Master File^HL70175|HOSP|UPD|20260610091500||AL
MFE|MAD|PKEY020|20260610091500|1234^^^HOSP^PRN|CM
STF|1234^^^HOSP^PRN|987654^^^NPI|SMITH^JOHN^A|P|M|19700115|A
PRA|1234^^^HOSP^PRN|GRP01^Cardiology Group^L|FACPHY|RR|207RC0000X^Cardiology^NUCC
ORG|1|CARD^Cardiology Unit^L|DEPT^Department^L|Y|U778899^^^HOSP^PRN|208^Physician^HL70452||RC^Cardiology^HL70454|20100701
A second in-context excerpt describing a practitioner who works in two units:
MSH|^~&|HRSYS|HOSP|DIRSVC|HOSP|20260610095500||MFN^M02^MFN_M02|MSG00021|P|2.5.1
MFI|PRA^Practitioner Master File^HL70175|HOSP|UPD|20260610095500||AL
MFE|MUP|PKEY021|20260610095500|1234^^^HOSP^PRN|CM
STF|1234^^^HOSP^PRN|987654^^^NPI|SMITH^JOHN^A|P|||A
PRA|1234^^^HOSP^PRN||FACPHY||207RC0000X^Cardiology^NUCC
ORG|1|CARD^Cardiology Unit^L|DEPT^Department^L|Y|U778899^^^HOSP^PRN|208^Physician^HL70452
ORG|2|CATH^Cath Lab^L|DEPT^Department^L|N|U778900^^^HOSP^PRN|208^Physician^HL70452
FHIR mapping
No segment-level ConceptMap is published in the v2-to-FHIR IG for ORG. Conceptually the organization unit described by ORG corresponds to a FHIR Organization resource (the unit) referenced from a PractitionerRole: ORG-2 and ORG-3 map to Organization.name and Organization.type, ORG-5 to the practitioner's unit-scoped identifier on PractitionerRole, ORG-6 through ORG-8 to PractitionerRole.code and specialty, and ORG-9 to PractitionerRole.period. Because no formal segment-level ConceptMap exists, implementers define these mappings locally.
Engine considerations
Engines should enforce that ORG-1 is present and use it to order and de-duplicate multiple ORG segments for the same practitioner. Although ORG fields do not repeat individually, the segment itself repeats, so engines must collect ORG occurrences into a list keyed by Set ID. When validating the primary-unit flag (ORG-4), engines should warn if more than one ORG in a group is marked primary. Coded fields ORG-6 through ORG-8 should be validated against the provider tables, and engines that upgrade CE to CWE for later versions should preserve the original components. The effective date range (ORG-9) should be parsed as a DR so that open-ended relationships are handled correctly.
How Vorro parses and produces ORG
Vorro parses ORG by associating each occurrence with the practitioner established upstream by STF and PRA, indexing the segments by ORG-1 so repeated units stay ordered. The unit codes and provider type, classification, and specialization codes are resolved against the configured HL7 tables with original components retained, and the effective date range is decomposed into start and end so open-ended affiliations are represented faithfully. When producing ORG, Vorro emits a sequential ORG-1 per unit, populates the unit and provider-role codes from the normalized affiliation model, flags exactly one segment as primary via ORG-4, and leaves optional fields empty rather than sending placeholder values.
Related pages
- HL7 STF Segment: Staff Identification
- HL7 PRA Segment: Practitioner Detail
- HL7 MFN Message: Master File Notification
