DICOM Attribute
Referring Physician Identification Sequence (0008,0096)
- Keyword
ReferringPhysicianIdentificationSequence- VR
SQ- VM
1
Definition
Identification of the Patient's referring physician. Only a single Item is permitted in this Sequence.
From NEMA PS3.3 §C.7.2.1.
Attribute Metadata
This attribute is part of the current DICOM Standard. Its value representation is SQ with multiplicity 1.
Used in 2 Modules
Value Representation
This attribute uses the SQ
Value Representation. Multiplicity 1 governs how many values may be encoded.
Integration Notes
Real-world integration guidance for engineers implementing this attribute in Mirth Connect, FHIR gateways, HL7 v2 bridges, and cloud DICOM services. Authoritative source data where available; reference examples and operational notes where they add value.
HL7 v2 Equivalent
-
PV1-8Referring Doctor (identifier subcomponents) site-dependentADTPV1-8 XCN identifies the referring doctor with multiple ID components (PV1-8.1, .9, .10, .13). DICOM ReferringPhysicianIdentificationSequence is a sequence of CodeValue/CodingSchemeDesignator/CodeMeaning items.
Source: common convention
Verify against IHE Radiology TF Vol 2 and your facility's interface specification before production use.
Cloud DICOM Support
AWS HealthImaging, Azure DICOM, and GCP Healthcare DICOM coverage rolls out by attribute. The QIDO-RS matching keys + Patient/Study/Series core (~50 attributes) are documented; lower-traffic attributes will be added as Saga teams encounter them in production.
Real-World Sample Values
No representative sample value available — this attribute isn't present in the de-identified pydicom fixture set. Add a fixture covering this attribute to expand coverage.
Mirth Connect Example
JavaScript transformer snippets for the most-queried tags will be added as coverage expands.
Common Operational Errors
Operational error patterns for the most-queried tags will be added as coverage expands.
DICOM Integration Services
Saga IT builds production DICOM integrations across Mirth Connect, FHIR gateways, and cloud imaging platforms. If you're working with ReferringPhysicianIdentificationSequence or the broader (0008,0096) context:
- Medical Imaging & DICOM Integration — end-to-end PACS, VNA, and cloud imaging deployments
- Mirth Connect Services — production-grade Mirth channel development
- Healthcare AI Integration — DICOM pipelines for AI/ML inference