Genomics Reporting Implementation Guide
3.0.0 - STU3 International flag

Genomics Reporting Implementation Guide, published by HL7 International / Clinical Genomics. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/genomics-reporting/ and changes regularly. See the Directory of published versions

Resource Profile: Genomic Report

Official URL: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-report Version: 3.0.0
Active as of 2024-12-12 Computable Name: GenomicReport

Genomic profile of DiagnosticReport.

Scope and Usage

The genomic report is the focus of all genomic reporting. It conveys metadata about the overall report (what kind of report it was, when it was written, who wrote it, final vs. draft, etc.). It also typically includes a rendered version for review by a clinician. It also groups together all relevant information found as part of the genomic analysis (Rules for relevancy will depend on the type of testing ordered, the reason for testing and the policies of the lab). Most of the structured genomic information is expressed as FHIR Observations. Any recommendations that come with the report are expressed as FHIR Tasks. The report can be organized into sub-reports using core DiagnosticReport extensions like extends or summaryOf, which is especially useful for later analysis steps. Additionally, an observation can be used to group content for viewing purposes or to indicate a higher-level panel (with a specific LOINC panel code in the Observation.code for example).

Class diagram showing the high-level categories of the component parts in a genomic diagnostic report

Genomic Report Overview

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from DiagnosticReport

NameFlagsCard.TypeDescription & Constraintsdoco
.. DiagnosticReport DiagnosticReport
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... recommended-action 0..* Reference(Medication Recommendation | Followup Recommendation) Recommended Action
URL: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/recommended-action
.... genomic-risk-assessment 0..* Reference(RiskAssessment) Genomic Risk Assessment
URL: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-risk-assessment
.... coded-note 0..* CodedAnnotation Comments about the report that also contain a coded type
URL: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-report-note
.... supporting-info 0..* Reference(Resource) Other information that may be relevant to this event.
URL: http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo
.... genomic-study 0..* Reference(Genomic Study) Reference to full details of an genomic study associated with the diagnostic report
URL: http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/genomic-study-reference
.... hla-genotyping-results-allele-database 0..1 CodeableConcept Allele Database
URL: http://hl7.org/fhir/StructureDefinition/hla-genotyping-results-allele-database
.... hla-genotyping-results-glstring 0..1 (Complex) glstring
URL: http://hl7.org/fhir/StructureDefinition/hla-genotyping-results-glstring
.... workflow-relatedArtifact 0..* RelatedArtifact Documentation relevant to the 'parent' resource
URL: http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact
... Slices for category 1..* CodeableConcept Service category
Slice: Unordered, Open by value:coding
.... category:Genetics 1..1 CodeableConcept Service category
..... coding 1..1 Coding Code defined by a terminology system
Required Pattern: At least the following
...... system 1..1 uri Identity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0074
...... code 1..1 code Symbol in syntax defined by the system
Fixed Value: GE
... code 1..1 CodeableConcept Name/Code for this diagnostic report
Required Pattern: At least the following
.... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
..... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
..... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 51969-4
... Slices for result 0..* Reference(Observation) Observations
Slice: Unordered, Open by profile:resolve()
.... result:diagnostic-implication 0..* Reference(Diagnostic Implication) Diagnostic Implication
.... result:therapeutic-implication 0..* Reference(Therapeutic Implication) Therapeutic Implication
.... result:molecular-consequence 0..* Reference(Molecular Consequence) Molecular Consequence
.... result:variant 0..* Reference(Variant) Variant
.... result:sequence-phase-relation 0..* Reference(Sequence Phase Relationship) Sequence Phase Relationship
.... result:genotype 0..* Reference(Genotype) Genotype
.... result:haplotype 0..* Reference(Haplotype) Haplotype
.... result:biomarker 0..* Reference(Molecular Biomarker) MolecularBiomarker
... conclusion 0..1 string Assessment of overall results
... conclusionCode 0..* CodeableConcept Coarse overall interpretation of the genomic results

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Overall Interpretation and Conclusion

On the report, it is important to answer the question "Did you find anything when you did the test I asked you to do?" The data sender can use attributes of conclusionCode and conclusion to represent the summary result of the test (e.g., Positive, Negative, Unknown) and a textual summary. These are typically used when the genomic test was looking for a particular genomically-based disease. It allows indication of whether genomic results known to be associated with the disease were found or not.

Linking To Genomic Observations

Results observation profiles, like genomic observations, are typically referenced directly by a Genomic Report. The genetic findings and implication profiles all contain links to computably define their composite relationships (e.g., the variant observation is referenced within the implication profile using derivedFrom). However, observations could be organized into groups by other observations. See this grouping guidance for an overview with examples and considerations for processing reports. Be aware that consumers of Genomic Diagnostic Report MUST navigate through all hasMember relations and navigate through derivedFrom relationships to ensure processing of all clinically relevant information.

Risk Assessments

In some cases, the lab or other reporting organization may generate risk assessments as part of their reports. These are referenced from a report or an observation from the Genomic Risk extension.

Presented Form

When sending a copy of the report (e.g., PDF or other document containing the written report), use presentedForm. Note this is different from the Related Artifact extension, which is used to reference citations, evidence and other supporting documentation for the observation or report. Another approach which should be avoided (at least for this current release) is the DiagnosticReport.media attribute. Its definition focuses on "Key images associated with this report" which does not align well with this use case.

Complex Reports

If needed, large or complex genomic reports may be broken down into sub-reports using core DiagnosticReport extensions like extends or summaryOf. This approach is particularly useful when different labs or services are performing later steps in the analysis, for example. Or a panel Observation.code can be used.