This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Work Group Orders and Observations & Clinical Genomics

Standards Status: Informative

10.0 Diagnostic Medicine Module

10.0.1 Introduction

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.

10.0.2 Index

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 ServiceRequest). See the Workflow Module for information about the coordination of activities such as ordering and fulfilling of diagnostics.

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

10.0.3 Security and Privacy

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.

10.0.4 Common Use Cases

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

• Planning a diagnostic test such as in this Careplan-example
• Recommending diagnostics such as is done by Clinical Decision Support tools. See the Clinical Reasoning module for more information.
• Ordering a Laboratory Test such as a lipid panel
• Reporting a Laboratory Test such as a lipid panel
• Ordering an imaging study such as a CT study
• Reporting an imaging study such as a CT study
• Ordering a genetic test such as a gene mutation analysis
• Reporting a genetic test such as HLA genotyping

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

10.0.5 Related Resources and Modules

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.

10.0.6 Developmental Roadmap

• 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 is needed for it to reach a more stable FMM level.
• The ServiceRequest resources has undergone substantial changes since DSTU2. Foremost of which is the merging of DSTU2 DiagnosticOrder and ServiceRequest into a single resource. 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 throughout 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 resource's current scope. We expect to see more widespread use of this resource and future updates to its FMM level
• The MolecularSequence 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 a 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.