HL7 FHIR DiagnosticReport Resource: US Core Profiles, LOINC Categories, and Observation Links

The FHIR DiagnosticReport resource (DiagnosticReport in HL7 FHIR R4) is the core clinical diagnostics container used to exchange the findings, interpretation, atomic result references, and formatted narrative reports of diagnostic investigations—including clinical laboratory panels, anatomic pathology and histopathology reports, radiology and nuclear medicine studies, cardiology diagnostics (ECG, echocardiography), and genomic sequencing panels.

In health system interoperability and clinical research data pipelines, DiagnosticReport provides the clinical context wrapper around individual FHIR Observation resources and DICOMweb ImagingStudy instances, while differing structurally from narrative clinical documents exchanged via FHIR DocumentReference.

What Is the FHIR DiagnosticReport Resource?

When clinical data architects evaluate what is the FHIR DiagnosticReport resource, they distinguish between an atomic measurement (an Observation, such as a single serum sodium value of 140 mmol/L) and the overarching diagnostic report issued by a performing laboratory or imaging service (the DiagnosticReport, such as a Basic Metabolic Panel or a Chest CT Report). In HL7 FHIR R4, a DiagnosticReport combines four categories of data in a single JSON resource:

1. Order & Workflow Context: Links back to the initiating clinical order via basedOn (Reference(ServiceRequest)), the patient (subject), the clinical visit (encounter), the specimen analyzed (specimen), and the performing organization or interpreting clinician (performer and resultsInterpreter).
2. Report Classification & Status Lifecycle: Tracks the report’s verification state via status (registered | partial | preliminary | final | amended | corrected | appended | cancelled | entered-in-error | unknown), the diagnostic discipline via category, and the specific panel or study name via code (bound to LOINC).
3. Structured Atomic Results & Imaging Pointers: References zero or more discrete Observation resources in result[], DICOM metadata in imagingStudy[], and key diagnostic images in media[].
4. Clinical Synthesis & Formatted Presentation: Captures the pathologist’s or radiologist’s narrative impression in conclusion, coded diagnoses in conclusionCode[] (SNOMED CT), and the complete rendered report (such as a PDF or XHTML document) in presentedForm[] (Attachment).

Core FHIR R4 DiagnosticReport Elements and HL7 v2 OBR Crosswalk

In hospital interface engines translating legacy HL7 v2 ORU^R01 (Unsolicited Observation Result) messages into FHIR R4 Bundles, the HL7 OBR segment (Observation Request) maps directly to the parent DiagnosticReport resource, while the repeating child OBX segments map to referenced Observation resources:

FHIR R4 DiagnosticReport Element	Cardinality	Data Type & Terminology Binding	HL7 v2 OBR / OBX Equivalent
identifier	0..*	Identifier (Placer / Filler report IDs)	OBR-2 (Placer Order #) / OBR-3 (Filler Order #)
basedOn	0..*	Reference(ServiceRequest | CarePlan)	ORC / OBR-2 initiating order reference
status	1..1	code (registered, preliminary, final, corrected)	OBR-25 (Result Status: O, P, F, C, X)
category	0..*	CodeableConcept (HL7 v2 Table 0074 or LOINC)	OBR-24 (Diagnostic Serv Sect ID: LAB, RAD, SP)
code	1..1	CodeableConcept (LOINC panel or study code)	OBR-4 (Universal Service Identifier)
effectiveDateTime / effectivePeriod	0..1	dateTime | Period (Clinically relevant time / collection time)	OBR-7 (Observation Date/Time) / OBR-8
issued	0..1	instant (When this report version was released)	OBR-22 (Results Rpt/Status Chng – Date/Time)
result	0..*	Reference(Observation) (Discrete panel analytes)	Repeating child OBX segments (OBX-2 = NM, ST, CE)
imagingStudy	0..*	Reference(ImagingStudy) (DICOM Study/Series/SOP)	OBX or ZDS DICOM Study Instance UID pointer
presentedForm	0..*	Attachment (Base64 or URL to PDF / HTML / RTF report)	OBX segment with OBX-2 = ED (Encapsulated Data) or RP

How Does DiagnosticReport Link to Observation and ImagingStudy?

Understanding how does DiagnosticReport link to Observation and ImagingStudy is essential for querying laboratory panels and radiology studies without duplicating clinical data:

ServiceRequest (Order: CBC w/ Diff or Chest CT)
      ^
      | basedOn
DiagnosticReport (LOINC 58410-2 CBC Panel or 24627-2 Chest CT)
  |---> result[]: Reference(Observation/hemoglobin), Reference(Observation/wbc), ...
  |---> specimen[]: Reference(Specimen/whole-blood-edta)
  |---> imagingStudy[]: Reference(ImagingStudy/dicom-study-1) --> WADO-RS DICOMweb Retrieve
  +---> presentedForm[]: Attachment (application/pdf or text/html narrative report)

• One-Way Graph Pointers (`DiagnosticReport.result` -> `Observation`): In FHIR R4, the link between a report and its constituent observations points outward from DiagnosticReport.result to each child Observation. An Observation does not contain a reverse pointer to DiagnosticReport; therefore, to retrieve a laboratory report and all of its numeric analytes in a single HTTP request, clients execute a FHIR _include query: GET /DiagnosticReport?patient=123&category=LAB&_include=DiagnosticReport:result.
• Radiology & Cardiology Workflow (`imagingStudy` and `media`): For diagnostic imaging, DiagnosticReport.imagingStudy references a FHIR ImagingStudy resource containing the DICOM Study Instance UID (2.25...), Series Instance UIDs, modality codes (CT, MR, US, CR), and a DICOMweb Endpoint for WADO-RS pixel retrieval. If the radiologist attaches 1 to 3 key annotated images directly to the report for rapid EHR viewing, those are linked via DiagnosticReport.media.link (Reference(Media)).

How Is FHIR DiagnosticReport Used in US Core?

In the United States, ONC certification under 45 CFR § 170.315(g)(10) and the US Core FHIR Implementation Guide (STU 6.1.0) split DiagnosticReport into two distinct profiles depending on whether the payload is structured laboratory data or a diagnostic narrative report:

1. US Core DiagnosticReport Profile for Laboratory Results Reporting (us-core-diagnosticreport-lab):
   • Requires category fixed to http://terminology.hl7.org/CodeSystem/v2-0074|LAB.
   • Requires code bound to LOINC laboratory panel/test codes.
   • Requires effectiveDateTime (specimen collection time) and issued (report release timestamp) when status is preliminary, final, amended, corrected, or appended.
   • Uses result to reference USCoreLaboratoryResultObservationProfile instances.
2. US Core DiagnosticReport Profile for Report and Note Exchange (us-core-diagnosticreport-note):
   • Used for radiology, cardiology, and pathology diagnostic reports.
   • Requires at least one LOINC diagnostic discipline code in category, specifically LP29684-5 (Radiology), LP29708-2 (Cardiology), or LP7839-6 (Pathology).
   • Supports narrative and multimedia exchange via presentedForm (PDF, plain text, or XHTML report attachment), media, and/or discrete result observations. (Note: US Core requires servers to expose diagnostic narratives via both DiagnosticReport and DocumentReference so client applications can query narrative reports consistently).

Frequently Asked Questions

What is the FHIR DiagnosticReport resource?

The HL7 FHIR DiagnosticReport resource represents the findings, clinical interpretation, metadata, and formatted output of a diagnostic investigation performed on a patient or specimen—such as a laboratory panel, pathology biopsy report, imaging study, or cardiology test.

How does DiagnosticReport link to Observation and ImagingStudy?

DiagnosticReport links to individual test measurements via its result array (Reference(Observation)), where each referenced Observation holds a single analyte value, unit (UCUM), and reference range. For radiology and cardiology imaging, DiagnosticReport.imagingStudy references an ImagingStudy resource containing DICOM Study/Series UIDs and DICOMweb WADO-RS retrieval endpoints, while presentedForm holds the radiologist’s formatted narrative report.

How is FHIR DiagnosticReport used in US Core?

The HL7 US Core Implementation Guide defines two profiles for DiagnosticReport: (1) the US Core DiagnosticReport Profile for Laboratory Results Reporting (category = LAB), which groups discrete laboratory Observation results, and (2) the US Core DiagnosticReport Profile for Report and Note Exchange, which uses LOINC category codes for Radiology (LP29684-5), Cardiology (LP29708-2), and Pathology (LP7839-6) to exchange diagnostic reports and presentedForm attachments.

Sources

• HL7 International — FHIR R4 DiagnosticReport Resource Specification
• HL7 US Core Implementation Guide — US Core DiagnosticReport Profile for Laboratory Results Reporting
• HL7 US Core Implementation Guide — US Core DiagnosticReport Profile for Report and Note Exchange