Molecular Definition Implementation Guide for Molecular Data Types
1.0.0-ballot1 - ci-build
Molecular Definition Implementation Guide for Molecular Data Types, published by HL7 International / Clinical Genomics. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/molecular-definition-data-types/ and changes regularly. See the Directory of published versions
Page standards status: Informative |
This implementation guide, along with its included artifacts, has been meticulously designed and developed to address practical use cases involving the exchange of genomic molecules and their associated data across diverse institutions and systems. By providing standardized frameworks and code systems, the guide facilitates seamless interoperability and accurate data representation. This section presents example use cases that demonstrate how this implementation guide can be leveraged to represent real genomic concepts as FHIR resource instances, thereby illustrating its applicability and effectiveness in real-world genomic data exchange scenarios. The following subsections provides example instances of MolecularDefinition resource and their corresponding profiles.
The following MolecularDefinitions show examples of a sequence represented as a literal leveraging the Sequence profile. The moleculeType and encoding attributes enable unambiguous interpretation of the sequence value.
The following MolecularDefinitions show examples of a sequence represented as a code using an accession number leveraging the Sequence profile.
The following MolecularDefinitions show examples of a sequence represented as a resolvable URL leveraging the Sequence profile. This example shows how the DocumentReference resource is utilized to represent the corresponding URL.
To illustrate the interaction of various MolecularDefinition profiles, we begin with a foundational example: an instance of a Sequence profile representing the raw coding sequence of HLA00001.1, which corresponds to the HLA-A01:01:01:01 allele. Building upon this, two distinct sets of Allele profiles are introduced, each encompassing five individual alleles derived from the HLA-A01:01:01:01 and HLA-A*01:02:01:01 groups, respectively. Each Allele set is then aggregated into a corresponding Haplotype instance, capturing the linkage of alleles on a single chromosome. Finally, these two Haplotype instances are integrated into an instance of Genotype profile, representing the combined allelic composition across both chromosomes at the HLA-A locus. This stepwise construction exemplifies how complex genetic information can be systematically modeled from raw sequence data through allelic and haplotypic layers to a comprehensive genotype representation. The following is the set of Molecular Definition instances that represent this use case:
The CYP2C19 gene encodes an enzyme essential for metabolizing several medications, including anti-coagulants, anti-depressants, and proton pump inhibitors. Variations in an individual's CYP2C19 genotype can significantly influence drug response, affecting efficacy and risk of adverse effects. In this example, the genotype instance is represented as a composite of two haplotypes, CYP2C191.002](MolecularDefinition-example-haplotype-cyp2c19-1002.html) and [CYP2C193.002, each defined by two alleles located at positions 661 and 1016 within the reference sequence context. This genomic information involves representing these haplotypes and their constituent alleles by leveraging the Molecular Definition profiles, i.e., Genotype, Haplotype, Allele and Sequence, through a series of interconnected profile instances. The following nested list shows this example and corresponding MolecularDefinition instances.