HL7 ORG Practitioner Organization Unit
HL7 field reference ORG fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| ORG.1 | Set ID - ORG | Yes | No | SI | |
| ORG.2 | Organization Unit Code | No | No | CE | 0405 |
| ORG.3 | Organization Unit Type Code | No | No | CE | 0474 |
| ORG.4 | Primary Org Unit Indicator | No | No | ID | 0136 |
| ORG.5 | Practitioner Org Unit Identifier | No | No | CX | |
| ORG.6 | Health Care Provider Type Code | No | No | CE | 0452 |
| ORG.7 | Health Care Provider Classification Code | No | No | CE | 0453 |
| ORG.8 | Health Care Provider Area of Specialization Code | No | No | CE | 0454 |
| ORG.9 | Effective Date Range | No | No | DR | |
| ORG.10 | Employment Status Code | No | No | CE | 0066 |
| ORG.11 | Board Approval Indicator | No | No | ID | 0136 |
| ORG.12 | Primary Care Physician Indicator | No | No | ID | 0136 |
ORG describes the organization unit attached to a practitioner or staff record.
The standard describes ORG this way: The ORG segment relates a practitioner to an organization unit and adds detailed information regarding the practitioner's practicing specialty in that organization unit. An ORG segment may optionally follow an STF segment. An ORG segment must always have been preceded by a corresponding STF segment. If no organization unit is specified, this segment is used to relate practitioners with their practicing specialties, including effective and end dates. When it is not necessary to record organization unit or dates associated with the practicing specialty, this data is recorded in PRA-3-Practitioner Category.
Master-file segments update reference data rather than describing a single patient event. They define locations, staff, providers, test catalogs, charge items, inventory items, languages, certificates, and other shared records.
Because many downstream messages depend on this data, small changes here can have large effects. Use stable identifiers, effective dates, action codes, and clear ownership rules instead of treating a master-file feed like a loose spreadsheet export.
The v2.5.1 structures show ORG in MFN_M02 - Master file - staff practitioner, PMU_B01 - Add personnel record, PMU_B04 - Active practicing person, and RSP_K25 - RSP - Personnel Information by Segment Response. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
ORG-1 is the sequence number for this ORG segment within its repeating group. It keeps multiple ORG lines in order; it is not the business identifier for the master-file record.
ORG-2 identifies the Organization Unit Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0405; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ORG-3 identifies the Organization Unit Type Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0474; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ORG-4 tells the receiver the state of this master-file record. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0136 or the narrower table in the local profile.
ORG-5 identifies the Practitioner Org Unit Identifier for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
ORG-6 identifies the Health Care Provider Type Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0452; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ORG-7 identifies the Health Care Provider Classification Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0453; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ORG-8 identifies the Health Care Provider Area of Specialization Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0454; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ORG-9 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
ORG-10 tells the receiver the state of this master-file record. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0066 or the narrower table in the local profile.
ORG-11 tells the receiver the state of this master-file record. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0136 or the narrower table in the local profile.
ORG-12 tells the receiver the state of this master-file record. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0136 or the narrower table in the local profile.
Related links
- MFI - Master File Identification
- MFE - Master File Entry
- MFA - Master File Acknowledgment
- LOC - Location Identification
- STF - Staff Identification
- PRA - Practitioner Detail
- OM1 - General Segment
- CDM - Charge Description Master
- MFN_M02 - Master file - staff practitioner
- PMU_B01 - Add personnel record