STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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 R2

Detailed Descriptions for the elements in the DiagnosticReport resource.

DiagnosticReport
Definition

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.

Control1..1
Requirements

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

Alternate NamesReport; Test; Result; Results; Labs; Laboratory
Comments

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.

DiagnosticReport.identifier
Definition

The local ID assigned to the report by the order filler, usually by the Information System of the diagnostic service provider.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

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.

Alternate NamesReportID
Summarytrue
DiagnosticReport.status
Definition

The status of the diagnostic report as a whole.

Control1..1
Terminology BindingDiagnosticReportStatus (Required)
Typecode
Is Modifiertrue
Requirements

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

Summarytrue
Comments

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

DiagnosticReport.category
Definition

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.

Control0..1
Terminology BindingDiagnostic Service Section Codes (Example)
TypeCodeableConcept
Alternate NamesDepartment; Sub-department; service; discipline
Summarytrue
Comments

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.

DiagnosticReport.code
Definition

A code or name that describes this diagnostic report.

Control1..1
Terminology BindingLOINC Diagnostic Report Codes (Preferred)
TypeCodeableConcept
Summarytrue
DiagnosticReport.subject
Definition

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.

Control0..1
TypeReference(Patient | Group | Device | Location)
Requirements

SHALL know the subject context.

Alternate NamesPatient
Summarytrue
DiagnosticReport.encounter
Definition

The link to the health care event (encounter) when the order was made.

Control0..1
TypeReference(Encounter)
Summarytrue
DiagnosticReport.effective[x]
Definition

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.

Control0..1
TypedateTime|Period
[x] NoteSee Choice of Data Types for further information about how to use [x]
Requirements

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

Alternate NamesObservation time; Effective Time
Summarytrue
Comments

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.

DiagnosticReport.issued
Definition

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

Control0..1
Typeinstant
Requirements

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

Alternate NamesDate Created; Date published; Date Issued
Summarytrue
Comments

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.

DiagnosticReport.performer
Definition

The diagnostic service that is responsible for issuing the report.

Control0..*
TypeReference(Practitioner | Organization)
Requirements

Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis.

Alternate NamesLaboratory; Service; Practitioner; Department; Company
Summarytrue
Comments

This is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report.

DiagnosticReport.request
Definition

Details concerning a test or procedure requested.

Control0..*
TypeReference(DiagnosticRequest | ProcedureRequest | ReferralRequest)
Requirements

Need to be able to track completion of requests based on reports issued and also to report what diagnostic tests were requested (not always the same as what is delivered).

Comments

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.

DiagnosticReport.specimen
Definition

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

Control0..*
TypeReference(Specimen)
Requirements

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

Comments

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 or group.

DiagnosticReport.result
Definition

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").

Control0..*
TypeReference(Observation)
Requirements

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.

Alternate NamesData; Atomic Value; Result; Atomic result; Data; Test; Analyte; Battery; Organizer
DiagnosticReport.imagingStudy
Definition

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.

Control0..*
TypeReference(ImagingStudy | ImagingManifest)
Comments

ImagingStudy and 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.

DiagnosticReport.image
Definition

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).

Control0..*
Requirements

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

Alternate NamesDICOM; Slides; Scans
Summarytrue
DiagnosticReport.image.comment
Definition

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.

Control0..1
Typestring
Requirements

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

Comments

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.

DiagnosticReport.image.link
Definition

Reference to the image source.

Control1..1
TypeReference(Media)
Summarytrue
DiagnosticReport.conclusion
Definition

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

Control0..1
Typestring
Requirements

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

Alternate NamesReport
DiagnosticReport.codedDiagnosis
Definition

Codes for the conclusion.

Control0..*
Terminology BindingSNOMED CT Clinical Findings (Example)
TypeCodeableConcept
DiagnosticReport.presentedForm
Definition

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

Control0..*
TypeAttachment
Requirements

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

Comments

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