DICOM Attribute

Physician(s) of Record (0008,1048)

Keyword
PhysiciansOfRecord
VR
PN
VM
1-n

Definition

Names of the physician(s) who are responsible for overall Patient care at time of Study (see for Performing Physician).

From NEMA PS3.3 §C.7.2.1.

Attribute Metadata

This attribute is part of the current DICOM Standard. Its value representation is PN with multiplicity 1-n.

Used in 2 Modules

This attribute uses the PN Value Representation. Multiplicity 1-n 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.

FHIR Mapping

No direct FHIR ImagingStudy mapping published for this attribute. Some tags map indirectly via the Patient, Endpoint, or ImagingSelection resources — Phase 2b will expand coverage to those.

HL7 v2 Equivalent

  • PV1-9 Consulting Doctor site-dependent
    ADT

    PV1-9 repeats; DICOM PhysiciansOfRecord is PN multi-valued.

    Source: HL7 v2 standard

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 PhysiciansOfRecord or the broader (0008,1048) context: