Findings and interpretation of diagnostic tests, including lab results and radiology reports. This page documents the DiagnosticReport resource as served by the mock.health synthetic FHIR R4 sandbox — 7 search parameters, US Core 6.1 profiling, and the elements accepted on write.
GET https://api.mock.health/fhir/DiagnosticReport — searchGET https://api.mock.health/fhir/DiagnosticReport/{id} — read by logical idPOST https://api.mock.health/fhir/DiagnosticReport — create (Pro)PUT https://api.mock.health/fhir/DiagnosticReport/{id} — update (Pro)patient (reference) — required — Patient the report is aboutcode (token) — Report type code (LOINC)date (date) — Clinically relevant dateencounter (reference) — Encounter for the reportidentifier (token) — External identifiercategory (token) — LAB | RAD | etc.status (token) — registered | final | amendedFields accepted when creating or updating a DiagnosticReport. Required elements are base FHIR cardinality; the rest are US Core must-support.
status (code) — required — registered | partial | preliminary | final | amended | correctedcode (CodeableConcept) — required — Report type code (LOINC)subject (Reference(Patient)) — US Core MS — patient the report is aboutcategory (CodeableConcept[]) — US Core MS — LAB or RAD category codeeffectiveDateTime (dateTime) — US Core MS — clinically relevant dateresult (Reference(Observation)[]) — US Core MS (lab) — observation resultspresentedForm (Attachment[]) — US Core MS (note) — report content as attachmentRadiology reports include RAG-generated narrative text in presentedForm (base64-encoded) and an extracted IMPRESSION in the conclusion field. Lab reports reference Observation results.
Base definition: HL7 FHIR R4 DiagnosticReport. Category: Diagnostics.
ImagingStudy · Media · Observation · ServiceRequest · Specimen
API reference · Quickstart · USCDI compliance · SMART on FHIR