A GenomicStudy is a set of analyses performed to analyze and generate genomic data.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resource id depends on the given use case.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. For DomainResources, if more than one implicitRules policy applies, additional policies may be conveyed using the additionalImplicitRules extension.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

IETF language tag for a human language

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. Contained resources may be a resource type defined in the FHIR specification, or an additional resource.

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifiers for this genomic study.

The status of the genomic study.

The status of the GenomicStudy.

The type of the study, e.g., Familial variant segregation, Functional variation detection, or Gene expression profiling.

The type relevant to GenomicStudy.

The primary subject of the genomic study.

The healthcare event with which this genomics study is associated.

When the genomic study was started.

Event resources that the genomic study is based on.

Healthcare professional who requested or referred the genomic study.

Healthcare professionals who interpreted the genomic study.

Why the genomic study was performed.

The defined protocol that describes the study.

The URL pointing to an externally maintained protocol that describes the study.

Comments related to the genomic study.

Description of the genomic study.

The details about a specific analysis that was performed in this GenomicStudy.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifiers for the analysis event.

Type of the methods used in the analysis, e.g., Fluorescence in situ hybridization (FISH), Karyotyping, or Microsatellite instability testing (MSI).

The method type of the GenomicStudy analysis.

Type of the genomic changes studied in the analysis, e.g., DNA, RNA, or amino acid change.

The change type relevant to GenomicStudy analysis.

The reference genome build that is used in this analysis.

Human reference sequence NCBI build ID

The genomic source class of the specimens used in the analysis, e.g., somatic or germline.

The genomic source class (e.g., somatic, germline) of the specimens being analyzed.

The defined protocol that describes the analysis.

The URL pointing to an externally maintained protocol that describes the analysis.

Name of the analysis event (human friendly).

The focus of a genomic analysis when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, child, or sibling. For example, in trio testing, the GenomicStudy.subject would be the child (proband) and the GenomicStudy.analysis.focus of a specific analysis would be the parent.

If the focus of the analysis is not known, the value of this field SHALL use the data absent extension.

The specimen used in the analysis event.

The date of the analysis event.

Any notes capture with the analysis event.

High-level quality metrics about the sequencing analysis that was performed.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The average read depth (number of reads for a position) for the sequencing analysis.

This value is typically represented with an 'x' after the number (30x). Share the quantity value only.

The percentage of the studied regions that were sequenced.

This value is typically represented with a '%' after the number (95%). Share the quantity value only.

Freetext description of the coverage and quality metrics for the sequencing analysis.

The protocol that was performed for the analysis event.

A set of genomic regions associated with this analysis, classified by their relationship to the analysis outcome (studied, called, or uncalled). Each repetition represents one group of regions sharing the same type.

Use one repetition per region type. For example, include one entry with type=studied for the full panel scope, one with type=called for regions with sufficient coverage to produce calls, and one with type=uncalled for regions where calls could not be produced. All three types may be present in a single analysis, or only a subset, as appropriate.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The type of this region group, indicating the relationship of these regions to the analysis outcome.

Use 'studied' for the full intended scope of the analysis. Use 'called' for regions where sufficient coverage and data quality enabled variant calling. Use 'uncalled' for regions within the studied scope where calls could not be produced (e.g., due to low coverage or poor mapping quality). An 'uncalled' entry does not imply that a pathogenic variant is present or was missed; it indicates a technical limitation. Use genomicRegion.description to document the reason.

The type of genomic region group. Use studied, called, or uncalled where applicable; other codes may be used for methodology-specific region classifications not covered by this value set.

The genomic regions belonging to this group. May be expressed as a coded list of HGNC gene symbols (using CodeableReference.concept) or as a reference to a BED file (using CodeableReference.reference to a DocumentReference).

For coded genes, use the HGNC gene symbol as display text and the HGNC gene ID as the code. If no HGNC code has been issued, use NCBI gene IDs. If region details beyond a coded gene list are needed (e.g., sub-gene coordinates), reference a BED file via DocumentReference. Multiple repetitions may be used to list individual genes or to combine a BED file reference with supplementary coded entries.

HGNC gene names for coded gene lists.

Expressed as a coded list of HGNC gene symbols or a reference to a BED file (DocumentReference).

Free-text notes providing additional context about this group of regions. Particularly useful for 'uncalled' entries to document the reason calls could not be produced (e.g., 'low coverage <20x', 'poor mapping due to repetitive sequence', 'homopolymer region exceeding assay limit').

Inputs for the analysis event.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

File containing input data.

Type of input data, e.g., BAM, CRAM, or FASTA.

The data format of the data file.

The analysis event or other GenomicStudy that generated this input file.

Outputs for the analysis event.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

File containing output data.

Type of output data, e.g., VCF, MAF, or BAM.

The data format of the data file.

Performer for the analysis event.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The organization, healthcare professional, or others who participated in performing this analysis.

Role of the actor for this analysis.

Devices used for the analysis (e.g., instruments, software), with settings and parameters.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Device used for the analysis.

Specific function for the device used for the analysis.

A GenomicStudy is a set of analyses performed to analyze and generate genomic data.

Identifiers for this genomic study.

The status of the genomic study.

The status of the GenomicStudy.

The type of the study, e.g., Familial variant segregation, Functional variation detection, or Gene expression profiling.

The type relevant to GenomicStudy.

The primary subject of the genomic study.

The healthcare event with which this genomics study is associated.

When the genomic study was started.

Event resources that the genomic study is based on.

Healthcare professional who requested or referred the genomic study.

Healthcare professionals who interpreted the genomic study.

Why the genomic study was performed.

The defined protocol that describes the study.

The URL pointing to an externally maintained protocol that describes the study.

Comments related to the genomic study.

Description of the genomic study.

The details about a specific analysis that was performed in this GenomicStudy.

Identifiers for the analysis event.

Type of the methods used in the analysis, e.g., Fluorescence in situ hybridization (FISH), Karyotyping, or Microsatellite instability testing (MSI).

The method type of the GenomicStudy analysis.

Type of the genomic changes studied in the analysis, e.g., DNA, RNA, or amino acid change.

The change type relevant to GenomicStudy analysis.

The reference genome build that is used in this analysis.

Human reference sequence NCBI build ID

The genomic source class of the specimens used in the analysis, e.g., somatic or germline.

The genomic source class (e.g., somatic, germline) of the specimens being analyzed.

The defined protocol that describes the analysis.

The URL pointing to an externally maintained protocol that describes the analysis.

Name of the analysis event (human friendly).

The focus of a genomic analysis when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, child, or sibling. For example, in trio testing, the GenomicStudy.subject would be the child (proband) and the GenomicStudy.analysis.focus of a specific analysis would be the parent.

If the focus of the analysis is not known, the value of this field SHALL use the data absent extension.

The specimen used in the analysis event.

The date of the analysis event.

Any notes capture with the analysis event.

High-level quality metrics about the sequencing analysis that was performed.

The average read depth (number of reads for a position) for the sequencing analysis.

This value is typically represented with an 'x' after the number (30x). Share the quantity value only.

The percentage of the studied regions that were sequenced.

This value is typically represented with a '%' after the number (95%). Share the quantity value only.

Freetext description of the coverage and quality metrics for the sequencing analysis.

The protocol that was performed for the analysis event.

A set of genomic regions associated with this analysis, classified by their relationship to the analysis outcome (studied, called, or uncalled). Each repetition represents one group of regions sharing the same type.

Use one repetition per region type. For example, include one entry with type=studied for the full panel scope, one with type=called for regions with sufficient coverage to produce calls, and one with type=uncalled for regions where calls could not be produced. All three types may be present in a single analysis, or only a subset, as appropriate.

The type of this region group, indicating the relationship of these regions to the analysis outcome.

Use 'studied' for the full intended scope of the analysis. Use 'called' for regions where sufficient coverage and data quality enabled variant calling. Use 'uncalled' for regions within the studied scope where calls could not be produced (e.g., due to low coverage or poor mapping quality). An 'uncalled' entry does not imply that a pathogenic variant is present or was missed; it indicates a technical limitation. Use genomicRegion.description to document the reason.

The type of genomic region group. Use studied, called, or uncalled where applicable; other codes may be used for methodology-specific region classifications not covered by this value set.

The genomic regions belonging to this group. May be expressed as a coded list of HGNC gene symbols (using CodeableReference.concept) or as a reference to a BED file (using CodeableReference.reference to a DocumentReference).

For coded genes, use the HGNC gene symbol as display text and the HGNC gene ID as the code. If no HGNC code has been issued, use NCBI gene IDs. If region details beyond a coded gene list are needed (e.g., sub-gene coordinates), reference a BED file via DocumentReference. Multiple repetitions may be used to list individual genes or to combine a BED file reference with supplementary coded entries.

HGNC gene names for coded gene lists.

Expressed as a coded list of HGNC gene symbols or a reference to a BED file (DocumentReference).

Free-text notes providing additional context about this group of regions. Particularly useful for 'uncalled' entries to document the reason calls could not be produced (e.g., 'low coverage <20x', 'poor mapping due to repetitive sequence', 'homopolymer region exceeding assay limit').

Inputs for the analysis event.

File containing input data.

Type of input data, e.g., BAM, CRAM, or FASTA.

The data format of the data file.

The analysis event or other GenomicStudy that generated this input file.

Outputs for the analysis event.

File containing output data.

Type of output data, e.g., VCF, MAF, or BAM.

The data format of the data file.

Performer for the analysis event.

The organization, healthcare professional, or others who participated in performing this analysis.

Role of the actor for this analysis.

Devices used for the analysis (e.g., instruments, software), with settings and parameters.

Device used for the analysis.

Specific function for the device used for the analysis.

A GenomicStudy is a set of analyses performed to analyze and generate genomic data.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resource id depends on the given use case.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. For DomainResources, if more than one implicitRules policy applies, additional policies may be conveyed using the additionalImplicitRules extension.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

IETF language tag for a human language

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. Contained resources may be a resource type defined in the FHIR specification, or an additional resource.

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifiers for this genomic study.

The status of the genomic study.

The status of the GenomicStudy.

The type of the study, e.g., Familial variant segregation, Functional variation detection, or Gene expression profiling.

The type relevant to GenomicStudy.

The primary subject of the genomic study.

The healthcare event with which this genomics study is associated.

When the genomic study was started.

Event resources that the genomic study is based on.

Healthcare professional who requested or referred the genomic study.

Healthcare professionals who interpreted the genomic study.

Why the genomic study was performed.

The defined protocol that describes the study.

The URL pointing to an externally maintained protocol that describes the study.

Comments related to the genomic study.

Description of the genomic study.

The details about a specific analysis that was performed in this GenomicStudy.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifiers for the analysis event.

Type of the methods used in the analysis, e.g., Fluorescence in situ hybridization (FISH), Karyotyping, or Microsatellite instability testing (MSI).

The method type of the GenomicStudy analysis.

Type of the genomic changes studied in the analysis, e.g., DNA, RNA, or amino acid change.

The change type relevant to GenomicStudy analysis.

The reference genome build that is used in this analysis.

Human reference sequence NCBI build ID

The genomic source class of the specimens used in the analysis, e.g., somatic or germline.

The genomic source class (e.g., somatic, germline) of the specimens being analyzed.

The defined protocol that describes the analysis.

The URL pointing to an externally maintained protocol that describes the analysis.

Name of the analysis event (human friendly).

The focus of a genomic analysis when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, child, or sibling. For example, in trio testing, the GenomicStudy.subject would be the child (proband) and the GenomicStudy.analysis.focus of a specific analysis would be the parent.

If the focus of the analysis is not known, the value of this field SHALL use the data absent extension.

The specimen used in the analysis event.

The date of the analysis event.

Any notes capture with the analysis event.

High-level quality metrics about the sequencing analysis that was performed.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The average read depth (number of reads for a position) for the sequencing analysis.

This value is typically represented with an 'x' after the number (30x). Share the quantity value only.

The percentage of the studied regions that were sequenced.

This value is typically represented with a '%' after the number (95%). Share the quantity value only.

Freetext description of the coverage and quality metrics for the sequencing analysis.

The protocol that was performed for the analysis event.

A set of genomic regions associated with this analysis, classified by their relationship to the analysis outcome (studied, called, or uncalled). Each repetition represents one group of regions sharing the same type.

Use one repetition per region type. For example, include one entry with type=studied for the full panel scope, one with type=called for regions with sufficient coverage to produce calls, and one with type=uncalled for regions where calls could not be produced. All three types may be present in a single analysis, or only a subset, as appropriate.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The type of this region group, indicating the relationship of these regions to the analysis outcome.

Use 'studied' for the full intended scope of the analysis. Use 'called' for regions where sufficient coverage and data quality enabled variant calling. Use 'uncalled' for regions within the studied scope where calls could not be produced (e.g., due to low coverage or poor mapping quality). An 'uncalled' entry does not imply that a pathogenic variant is present or was missed; it indicates a technical limitation. Use genomicRegion.description to document the reason.

The type of genomic region group. Use studied, called, or uncalled where applicable; other codes may be used for methodology-specific region classifications not covered by this value set.

The genomic regions belonging to this group. May be expressed as a coded list of HGNC gene symbols (using CodeableReference.concept) or as a reference to a BED file (using CodeableReference.reference to a DocumentReference).

For coded genes, use the HGNC gene symbol as display text and the HGNC gene ID as the code. If no HGNC code has been issued, use NCBI gene IDs. If region details beyond a coded gene list are needed (e.g., sub-gene coordinates), reference a BED file via DocumentReference. Multiple repetitions may be used to list individual genes or to combine a BED file reference with supplementary coded entries.

HGNC gene names for coded gene lists.

Expressed as a coded list of HGNC gene symbols or a reference to a BED file (DocumentReference).

Free-text notes providing additional context about this group of regions. Particularly useful for 'uncalled' entries to document the reason calls could not be produced (e.g., 'low coverage <20x', 'poor mapping due to repetitive sequence', 'homopolymer region exceeding assay limit').

Inputs for the analysis event.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

File containing input data.

Type of input data, e.g., BAM, CRAM, or FASTA.

The data format of the data file.

The analysis event or other GenomicStudy that generated this input file.

Outputs for the analysis event.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

File containing output data.

Type of output data, e.g., VCF, MAF, or BAM.

The data format of the data file.

Performer for the analysis event.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The organization, healthcare professional, or others who participated in performing this analysis.