This is the initial release of the Clinical Genomics Incubator Implementation Guide for Additional Resources for initial ballot May 2026.
first
true
category
Diagnostics
title
Clinical Genomics Incubator Implementation Guide for Additional Resources
introduction
The Clinical Genomics Incubator Implementation Guide for Additional Resources hosts two main genomic resources, Genomic Study and Molecular Definition, to be leveraged by Genomics Reporting and Molecular Definition Data Types Implementation Guides.
Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/uv/cg-incubator (Problem #1 with package-list.json at http://hl7.org/fhir/uv/cg-incubator: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
This IG is version 6.0.0-ballot3, while the IG 'hl7.terminology.r5' is from version 5.0.0
ImplementationGuide/hl7.fhir.uv.cg-incubator
error
This IG is version 6.0.0-ballot3, while the IG 'hl7.fhir.uv.extensions.r5' is from version 5.0.0
ImplementationGuide/hl7.fhir.uv.cg-incubator
error
This IG is version 6.0.0-ballot3, while the IG 'hl7.fhir.uv.tools.r5' is from version 5.0.0
error
There is no jira specification file defined with the expected name of FHIR-cg-incubator in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
en/StructureDefinition-MolecularDefinition.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The resolvable element can be used to represent a sequence by reference, but it also implies that the sequence is accessible and SHOULD be resolvable (although a security layer may be present). This element makes use of the Document Reference resource, which contains the content.attachment element. The Attachment datatype can be used to represent sequences that are captured as a formatted file (using .contentType and .data) or as a URL (using .contentType and .url).'CONFORMANCE_STATEMENT_WORD
ImplementationGuide/hl7.fhir.uv.cg-incubator: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
ImplementationGuide.dependsOn[0] (l1/c2559)
warning
The ImplementationGuide is based on FHIR version 6.0.0-ballot3 but package hl7.terminology.r5#7.1.0 is based on FHIR version 5.0.0. In general, this version mismatch should be avoided - some tools will try to make this work with variable degrees of success, but others will not even tryIG_DEPENDENCY_VERSION_WARNING
--
ImplementationGuide.dependsOn[1] (l1/c2921)
error
The canonical URL http://hl7.org/fhir/extensions/ImplementationGuide/hl7.fhir.uv.extensions points to the package hl7.fhir.uv.extensions which is inconsistent with the stated packageId of hl7.fhir.uv.extensions.r5IG_DEPENDENCY_CLASH_PACKAGEID
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
A definition for CodeSystem 'http://www.sequenceontology.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.genenames.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.genenames.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.sequenceontology.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.sequenceontology.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
Error from https://tx.fhir.org/r5: Error: A definition for CodeSystem 'http://www.genenames.org' could not be found, so the value set cannot be expanded
(from server, see log)
The type MolecularDefinition is not legal because it is not defined in the FHIR specification. Other types must have a namespace on themSD_TYPE_NOT_LOCAL
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
A definition for CodeSystem 'http://www.pharmvar.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.pharmvar.org' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.ebi.ac.uk/ipd/imgt/hla' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
A definition for CodeSystem 'http://www.ncbi.nlm.nih.gov/refseq' could not be found, so the code cannot be validated (from https://tx.fhir.org/r5) UNKNOWN_CODESYSTEM
Error from https://tx.fhir.org/r5: Error: A definition for CodeSystem 'http://www.ncbi.nlm.nih.gov/refseq' could not be found, so the value set cannot be expanded
(from server, see log)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG)
The canonical URL http://hl7.org/fhir/extensions/ImplementationGuide/hl7.fhir.uv.extensions points to the package hl7.fhir.uv.extensions which is inconsistent with the stated packageId of hl7.fhir.uv.extensions.r5
The ImplementationGuide is based on FHIR version 6.0.0-ballot3 but package hl7.terminology.r5#7.1.0 is based on FHIR version 5.0.0. In general, this version mismatch should be avoided - some tools will try to make this work with variable degrees of success, but others will not even try
hl7.fhir.uv.cg-incubator
hl7.fhir.uv.tools.r5