FHIR DiagnosticReport

The HL7 FHIR resource for a diagnostic report.¹ In OIDM it is the documented interchange encoding of an Exam Finding List: “DiagnosticReport containing a list of Observation objects, with a finding code on each Observation and a list of components with attribute codes and values (especially present/absent and change from prior).”² In an Imaging Problem List, DiagnosticReports are what each observation points back to, giving the exam date and LOINC exam type.²

The lineage sample shows the shape with real data: a report with a SNOMED and HL7 category, a LOINC code, an inline ImagingStudy, result references to three Observations, and conclusion with SNOMED conclusionCode.³

Synonyms and near-synonyms

• Report and radiology report usually mean the narrative document; this is the resource that carries it plus its structured results.
• diagnosticReportId is the Exam Finding List field that holds its identifier.
• Imaging Diagnostic Report (IHE IDR) is the profile that constrains this resource for radiology; it is not the resource.
• ImagingStudy is a separate resource for the study itself, present inline in the lineage samples.

Identifier form

A FHIR resource identifier. The Exam Finding List samples use UUID strings.

Where it is used

FHIR mapping, Exam Finding List, and IHE IDR alignment.

Conflicts

The mapping is documented and unimplemented. No FHIR resource classes exist in the extraction platform’s source, and a search for DiagnosticReport across it returns nothing; the only real FHIR documents in the repository are two input samples. Those input samples also do not use the presence and change-from-prior component pattern the specification prescribes, because that pattern describes the output.² Separately, IHE IDR would encode the attribute layer with hasMember rather than components.⁴

Footnotes

1. DiagnosticReport resource, HL7 FHIR ↩

2. imaging-problem-list README ↩ ↩² ↩³

3. Lung screening DiagnosticReport sample ↩

4. IHE IDR Phase II extract ↩