The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports.

To support reporting for any diagnostic report into a clinical data repository.

This is intended to capture a single report, and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.

The local ID Identifiers assigned to the this report by the order filler, usually by the Information System of the diagnostic service provider. performer or other systems.

Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context.

Usually assigned by the Information System of the diagnostic service provider (filler id).

Details concerning a test or procedure requested.

This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon.

Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports.

The status of the diagnostic report as a whole.

Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports.

This is labeled as "Is Modifier" because applications need to take appropriate action if a report is withdrawn.

A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes.

The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code.

A code or name that describes this diagnostic report.

The subject of the report. Usually, but not always, this is a patient. However diagnostic services also perform analyses on specimens collected from a variety of other sources.

SHALL know the subject context.

The link to the health care healthcare event (encounter) when the order was made. (e.g. a patient and healthcare provider interaction) which this DiagnosticReport per is about.

Links the request to the Encounter context.

This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests).

The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself.

Need to know where in the patient history to file/present this report.

If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.

The date and time that this version of the report was released from the source diagnostic service.

Clinicians need to be able to check the date that the report was released.

May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report.

The diagnostic service that is responsible for issuing Indicates who or what participated in producing the report.

Need to know whom to contact if there are queries about the results. Also may need to track Describes the source type of reports for secondary data analysis. participation (e.g. a responsible party, author, or verifier).

Details concerning a test The reference to the practitioner or procedure requested. organization involved in producing the report. For example, the diagnostic service that is responsible for issuing the report.

Need to be able know whom to contact if there are queries about the results. Also may need to track completion the source of requests based on reports issued and also to report what diagnostic tests were requested (not always the same as what is delivered). for secondary data analysis.

Note: Usually there This is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note not necessarily the source of the atomic data items. It is the entity that there are also cases where one request leads to multiple reports. takes responsibility for the clinical report.

Details about the specimens on which this diagnostic report is based.

Need to be able to report information about the collected specimens on which the report is based.

If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per Observation observation or group.

Observations that are part of this diagnostic report. Observations can be simple name/value pairs (e.g. "atomic" results), or they can be grouping observations that include references to other members of the group (e.g. "panels").

Need to support individual results, or report groups of results, where the result grouping is arbitrary, but meaningful. This structure is recursive - observations can contain observations.

One or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images.

ImagingStudy and ImageObjectStudy ImageManifest and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.

A list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest).

Many diagnostic services include images in the report as part of their service.

A comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features.

The provider of the report should make a comment about each image included in the report.

The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.

Reference to the image source.

Concise and clinically contextualized narrative interpretation impression / summary of the diagnostic report.

Need to be able to provide a conclusion that is not lost among the basic result data.

Codes for the conclusion.

Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent.

Gives Laboratory laboratory the ability to provide its own fully formatted report for clinical fidelity.

"application/pdf" is recommended as the most reliable and interoperable in this context.