Integration Reference
DICOM to HL7 v2 Mapping
49 DICOM ↔ HL7 v2 field mappings grouped by HL7 segment. Authoritative mappings come from IHE Radiology Technical Framework Vol 2 and HL7 v2 standard conventions. 26 of 49 are flagged as authoritative; the rest carry a site-dependent badge because Accession Number routing (OBR-18 vs OBR-3 vs ZDS-1) and similar conventions vary by facility.
By HL7 Segment
Each HL7 v2 segment lists the DICOM tags that populate (or are populated by) its fields. Clicking a tag lands on its per-attribute reference with sample Mirth Connect code.
MSH: Message Header
-
MSH-3Sending Application site-dependentApproximate mapping. DICOM StationName usually identifies the modality (CT scanner serial); MSH-3 identifies the application that sent the HL7 message. Equivalent only when the imaging device sends both.
-
MSH-4Sending Facility site-dependentLoose mapping. MSH-4 identifies the sending application's facility; DICOM InstitutionName names the institution that operates the imaging equipment. Often equivalent in single-site deployments.
-
MSH-7 (of MPPS message, time portion)Message Date/Time site-dependentTime portion of MPPS message timestamp. Date portion goes to (0040,0244).
-
MSH-7 (of MPPS message)Message Date/Time site-dependentDICOM PerformedProcedureStepStartDate is set when the modality emits an MPPS N-CREATE message. The HL7 v2 equivalent is the message timestamp.
PID: Patient Identification
-
PID (calculated)Patient Age (derived)HL7 v2 has no direct Patient Age field — receivers calculate from PID-7 (Date of Birth) and the message's reference date. DICOM PatientAge is AS (e.g., '045Y'); the modality computes it.
-
PID-11Patient AddressPID-11 is XAD (extended address) and repeating. DICOM PatientAddress is a single LO field — typically the home address (PID-11.7 = 'H') is used.
-
PID-13Phone Number — Home site-dependentPID-13 (home) and PID-14 (business) both repeating. DICOM PatientTelephoneNumbers is multi-valued — implementations vary on which to map.
-
PID-17Religion site-dependentBoth fields are CWE — code values may differ between facilities; map by code system or pass-through string.
-
PID-22Ethnic GroupBoth DICOM (0010,2160) and PID-22 are deprecated in newer revisions for privacy reasons. Avoid in new interfaces.
-
PID-3Patient Identifier ListPID-3 is a repeating CX field; DICOM PatientID typically maps to the MRN entry (PID-3.1 with PID-3.5 = 'MR').
-
PID-4Alternate Patient IDPID-4 was retired in HL7 v2.5+ in favor of repeating PID-3. Only meaningful for v2.4 and earlier interfaces.
-
PID-5Patient NameDirect mapping. PID-5 uses XPN (Extended Person Name) which decomposes the same 5 components as DICOM PN VR (family/given/middle/prefix/suffix).
-
PID-7Date/Time of BirthPID-7 is a TS (timestamp) — DICOM consumes only the date portion (YYYYMMDD).
-
PID-8Administrative SexSame code values: M, F, O, U (and DICOM-only A for Ambiguous when absent in HL7 v2).
-
PID-9Patient AliasPID-9 is XPN repeating; DICOM OtherPatientNames is PN multi-valued.
PV1: Patient Visit
-
PV1-19Visit NumberBoth fields identify the encounter/visit. AdmissionID in DICOM = Visit Number in HL7 v2. Authoritative per IHE.
-
PV1-3 / OBR-19Assigned Patient Location / Placer Field 2 site-dependentScheduledStationName in DICOM hints at the room assigned to perform the procedure; HL7 v2 PV1-3 names the patient's current location (room/bed). Loose match — not always equivalent in radiology workflows.
-
PV1-44Admit Date/TimePV1-44 is TS; DICOM AdmittingDate is DA (date only) — strip the time portion.
-
PV1-8Referring DoctorAlso frequently appears in OBR-16 (Ordering Provider) for orders. Both PID PV1-8 and OBR-16 are XCN.
-
PV1-8Referring Doctor (phone subcomponent) site-dependentPV1-8 is XCN; phone numbers live in subcomponents PV1-8.13 / PV1-8.14. DICOM ReferringPhysicianTelephoneNumbers is multi-valued SH.
-
PV1-8Referring Doctor (identifier subcomponents) site-dependentPV1-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.
-
PV1-9Consulting Doctor site-dependentPV1-9 repeats; DICOM PhysiciansOfRecord is PN multi-valued.
PV2: Patient Visit Additional
-
PV2-3 / NTEAdmit Reason / Note site-dependentDICOM AdditionalPatientHistory is LT free text. PV2-3 (Admit Reason) is one source; NTE-3 segments are another. Sometimes assembled from multiple HL7 v2 fields.
AL1: Allergy Information
-
AL1-3Allergen Code/Mnemonic/Description site-dependentDICOM MedicalAlerts is free-text LO multi-valued; AL1 is a structured repeating segment. Concatenate AL1 instances as text for DICOM, or vice-versa.
-
AL1-3Allergen Code/Mnemonic/Description site-dependentLike MedicalAlerts (0010,2000), DICOM Allergies is free-text LO; AL1 is structured. Same concatenation pattern.
ORC: Common Order
-
ORC-21 / PV1-39Ordering Facility Name / Servicing Facility site-dependentScheduledStationAETitle is the DICOM AE title of the modality — there is no HL7 v2 field for AE titles. Some facilities convey the AE via a Z-segment or via ORC-21 (Ordering Facility Name) by convention.
OBR: Observation Request
-
OBR-15Specimen Source (or body site) site-dependentLoose mapping. OBR-15 is intended for lab specimens; radiology often uses it for body site as a courtesy. Newer interfaces use SPM segment + OBR-44 procedure code.
-
OBR-18Placer Field 1 (Accession Number)Most common mapping per IHE RAD-TF — Accession Number is conveyed in OBR-18 (Placer Field 1) for radiology orders. Some sites use OBR-3 (Filler Order Number) or a Z-segment instead. Always confirm with facility convention.
-
OBR-19Placer Field 2 (Study ID) site-dependentOlder convention. DICOM StudyID is SH 16 chars; OBR-19 (or sometimes OBR-20) carries it in radiology workflows.
-
OBR-24Diagnostic Service Section IDOBR-24 carries the modality code (CT, MR, US, NM, etc.) using the same DICOM CID 30 / table 6029 codes. Often also encoded in OBR-21 (Filler Field 1).
-
OBR-3 / ORC-3Filler Order NumberScheduledProcedureStepID in DICOM matches the filler-side identifier of the order. ORC-3 is the formal field; OBR-3 mirrors it.
-
OBR-32Principal Result InterpreterOBR-32 is NDL — name with date and location. DICOM PerformingPhysicianName is PN.
-
OBR-32Principal Result Interpreter (XCN.2 + XCN.3) site-dependentScheduledPerformingPhysicianName maps from OBR-32 in result messages, or from custom Z-segments in scheduling messages.
-
OBR-4Universal Service IdentifierOBR-4 is CWE coded with text — DICOM StudyDescription typically uses the text component. Same field also feeds (0040,1003) RequestedProcedureCode + ProcedureCodeSequence.
-
OBR-4Universal Service IdentifierScheduledProcedureStepDescription draws from OBR-4 (Universal Service Identifier text component). Same source as StudyDescription (0008,1030).
-
OBR-44Procedure CodeOBR-44 is CWE; DICOM RequestedProcedureCodeSequence carries CodeValue, CodingSchemeDesignator, CodeMeaning — all three components map directly.
-
OBR-7Observation Date/Time (date portion)OBR-7 is TS; DICOM StudyDate consumes the YYYYMMDD portion. The time portion goes to (0008,0030) StudyTime.
-
OBR-7Observation Date/Time (time portion)Time portion of the OBR-7 timestamp. Date portion goes to (0008,0020) StudyDate.
OBX: Observation / Result
-
OBX (PATIENT HEIGHT loinc)Patient Height observation site-dependentHL7 v2 conveys patient height as OBX with LOINC 8302-2. DICOM PatientSize is DS in meters. Unit conversion (in/cm/m) may be required.
-
OBX (PATIENT WEIGHT loinc)Patient Weight observation site-dependentHL7 v2 conveys patient weight as an observation (OBX with LOINC 29463-7 or similar). DICOM PatientWeight is DS in kg. Unit conversion may be required (lb ↔ kg).
-
OBX-16Responsible Observer site-dependentOBX-16 (XCN repeating) carries the reading physician for an observation. DICOM NameOfPhysiciansReadingStudy is PN multi-valued.
-
OBX-23 / OBR-13Performing Organization Name / Relevant Clinical Info site-dependentLoose mapping. DICOM InstitutionalDepartmentName names the imaging department; HL7 v2 carries similar info in OBX-23 (Performing Organization Name) for results.
-
OBX-3 / TXA-3Observation Identifier (or Document Type) site-dependentDICOM SeriesDescription is free LO; HL7 v2 has no direct equivalent. Often left blank or filled at the modality.
TQ1: Timing / Quantity
-
TQ1-9 / OBR-27.6PriorityTQ1-9 in HL7 v2.5+ (or OBR-27.6 in older versions). Code values: STAT, ASAP, ROUTINE, etc. — often mapped one-to-one to DICOM RequestedProcedurePriority.
NTE: Notes and Comments
-
NTE-3Comment site-dependentNTE segments concatenate into ImagingServiceRequestComments. Multiple NTEs join with newlines.
IPC: Imaging Procedure Control (IHE RAD)
-
IPC-1 or OBR-19Accession Identifier (IHE RAD) or Placer Field 2RequestedProcedureID is the IHE workflow's primary identifier of a requested procedure. IHE RAD-TF SWF profile uses IPC-1. Older interfaces overload OBR-19.
OTHER: Segment
-
n/a(no HL7 v2 equivalent)Manufacturer is set by the modality from its own configuration; HL7 v2 has no field that conveys imaging equipment manufacturer.
-
n/a(no HL7 v2 equivalent)ManufacturerModelName is a modality-side attribute; not conveyed in HL7 v2 messages.
ZDS: Segment
-
ZDS-1 / OBR-3Study Instance UID (custom Z-segment) or Filler Order NumberIHE RAD-TF defines ZDS-1 (a Z-segment) as the formal carrier for Study Instance UID. Many facilities instead overload OBR-3 (Filler Order Number) or include the UID as a comment NTE. Confirm with facility convention.
HL7 v2 ↔ DICOM Interfaces
Modality Worklist SCPs feeding from HL7 v2 ORM → DICOM MWL, MPPS N-CREATE/N-SET back to the RIS, or ORU results flowing with DICOM study references. These are Mirth Connect and Saga IT imaging integration staples. If your facility's conventions differ from what's shown here, flag it and we'll help reconcile.