Current Build
Work Group Orders and Observations & Clinical Genomics Ballot Status: Informative

The Diagnostics Module provides an overview and guide to the FHIR content that addresses ordering and reporting of clinical diagnostics including laboratory testing, imaging and genomics.

The Diagnostics module covers the following resources:

The diagnostic resources and their relationships are shown below. The arrows represent the direction of the references between resources (for example, DiagnosticReport references ProcedureRequest). See the Workflow Module for information about the coordination of activities such as ordering and fulfilling of diagnostics.

Image showing the diagnostic resources

Note: See the Genomics Implementation Guidance for additional information about how to use the Diagnostic resources for Clinical Genomic Reporting and Analysis.

NameAliasesDescription
ObservationVital Signs, Measurement, ResultsMeasurements and simple assertions made about a patient, device or other subject.
DiagnosticReportReport, Test, Result, Results, LabsThe 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.
ProcedureRequestdiagnostic request, referral, referral requestA record of a request for diagnostic investigations, treatments, or operations to be performed.
ImagingStudyRepresentation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities.
ImagingManifestManifest, XDS-I summary, Key ImagesA text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection.
SequenceRaw data describing a biological sequence.
SpecimenA sample to be used for analysis.
BodyStructureanatomical locationRecord details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.

The diagnostic resources often represent patient-specific data, and as such are susceptible to data breaching. Necessary privacy and security provisions must be in place when searching and fetching this information. For more general considerations, see the Security and Privacy module.

Diagnostic resources are commonly used to plan, recommend, order and report clinical diagnostics:

There are many ways to use these resources independently as well. The Observation resource in particular is central to capturing many measurements and events in healthcare and is often used outside the context of diagnostic orders and reports.

  • recording vital signs such as temperature
  • recording other observations of a patient's social history such as tobacco use
  • recording other characteristics of a patient such as pregnancy status (note: The Condition resource may be used to represent these as well)
  • recording clinical assessment tool scores such as an Apgar score.
  • identifying and describing a specimen or body site

The resources that represent the basic information about a patient and a clinical encounter can be found in the Administration Module. Other resources that represent core clinical information generated by healthcare providers during the course of a patient encounter are detailed in the Clinical Summary Module and the Medications Module.

  • The Observation and Diagnostic Report resources have been tested and used in production tooling and as such have reached a maturity level FMM=4 where changes become less likely and require implementer community approval. Future work will focus on developing core profiles and clarifying use cases and boundaries and providing more domain specific examples. We anticipate Observation and Diagnostic Report reaching normative status by the end of this cycle.
  • The ImagingStudy resource has had some limited testing and use. Further use of this resource in production tooling in order for it to reach a more stable FMM level.
  • ImagingManifest: We expect to see more widespread use of this resource and future updates to its FMM level
  • The ProcedureRequest resources has undergone substantial changes since DSTU2. Foremost of which is the merging of DSTU2 DiagnosticOrder and ProcedureRequestinto a single resources. In addition, as a result of the addition of FHIR workflow for STU3, its structure and content have been updated to align with the general FHIR workflow "request" pattern. Because of these, it remains a relatively immature resource. No more sweeping changes to its structure are expected. However, its scope and boundaries vis a vis other resources will be the topic of future workgroup efforts. We anticipate its broad use by implementers and that it will mature as a resource throught the upcoming cycle.
  • The Specimen resource will be the focus of work group efforts for the upcoming cycle. A new SpecimenDefinition resource is planned for describing specimen types vs specimen instances and will take over some of the Specimen resourc'e's current scope. We expect to see more widespread use of this resource and future updates to its FMM level
  • The Sequence resource remains draft and we expect to see more widespread use of this resource and future updates to its FMM level
  • The BodyStructure resource is an immature resource with a FMM level of 1. To date there has been little implementation feedback.
  • The Media resource is the newest member to the Diagnostics module having undergone substantial scope and structural changes to create an specialized observation resource focused on digital media such as images and audio files. Future work will focus on developing core profiles and providing more domain specific examples.