Validation Results for GenomicsReporting

Generated Mon Dec 18 22:55:10 UTC 2023, FHIR version 4.0.1 for hl7.fhir.uv.genomics-reporting#3.0.0-ballot (canonical = http://hl7.org/fhir/uv/genomics-reporting (history)). See Full QA Report

Quality Checks
Publisher Version:IG Publisher Version: v1.5.8
Publication Code:genomics-reporting . PackageId = hl7.fhir.uv.genomics-reporting, Canonical = http://hl7.org/fhir/uv/genomics-reporting
Realm Check for UV:
  • n/a
Publication Request:
package-idhl7.fhir.uv.genomics-reporting
version3.0.0-ballot
pathhttp://hl7.org/fhir/uv/genomics-reporting/2024Jan
Pub-Modeworking release
statusballot
sequenceSTU 3
descBallot version for STU3 update of Genomics Reporting IG
descmd

Ballot version for STU3 update of Genomics Reporting IG

Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
Supressed Messages:51 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.uv.genomics-reporting3.0.0-ballotR4http://hl7.org/fhir/uv/genomics-reporting
... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0Latest Release is 5.4.0
... hl7.fhir.uv.extensions.r41.0.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0
Templates: hl7.fhir.template#0.8.0 -> hl7.base.template#0.8.0 -> fhir.base.template#0.6.0. Tools: current
Dependent IGs:no references
Global Profiles:(none declared)
HTA Analysis:All OK
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 2.0.0
IPA Comparison: n/a
IPS Comparison: n/a
Summary: errors = 0, warn = 1, info = 2, broken links = 0
FilenameErrorsWarningsHints
Build Errors000
C:\temp\hl7.fhir.uv.genomics-reporting#3.0.0-ballot\fsh-generated\resources\ValueSet-condition-inheritance-mode-vs010

n/a Show Validation Information


C:\temp\hl7.fhir.uv.genomics-reporting#3.0.0-ballot\fsh-generated\resources\ValueSet-condition-inheritance-mode-vs.json Show Validation Information (1)

PathSeverityMessage
ValueSet.compose.include[0]warningUnknown System 'http://human-phenotype-ontology.org' specified, so Concepts and Filters can't be checked (Details: Resolved system http://human-phenotype-ontology.org (v1.0.0), but the definition doesn't include any codes, so the code has not been validated)

Suppressed Messages (Warnings, hints, broken links)

An example of DiagnosticImplication<Observation>.derivedFrom() that we slice to only allow our profiles. In this example, we did not define specific Variant instances and just refer to some variants by identifier (rather than a full resource), so ignoring these warnings

Code Systems for diseases - MONDO - https://terminology.hl7.org/CodeSystem-MONDO.html

Code has been checked and are correct

CodeSystem and ValueSets - dbSNP - https://terminology.hl7.org/CodeSystem-v3-dbSNP.html

CodeSystem and ValueSets - gtr - https://terminology.hl7.org/CodeSystem-GTR.html

CodeSystem and ValueSets - refseq - https://terminology.hl7.org/CodeSystem-v3-refSeq.html

CodeSystems and ValueSets - ISCN - https://terminology.hl7.org/CodeSystem-ISCN.html

CodeSystems and ValueSets - imgt HLA alleles - https://jira.hl7.org/browse/HTA-127.

CodeSystems and ValueSets not supported yet - clinvar - https://terminology.hl7.org/CodeSystem-ClinVarV.html

CodeSystems and ValueSets not supported yet -- clinicaltrials - https://jira.hl7.org/browse/HTA-126

CodeSystems and ValueSets not supported yet -- glstring - https://jira.hl7.org/browse/HTA-84

CodeSystems and ValueSets not supported yet -- https://terminology.hl7.org/CodeSystem-v3-hgnc.html

CodeSystems and ValueSets not supported yet -- human-phenotype-ontology - https://terminology.hl7.org/CodeSystem-HPO.html

CodeSystems and ValueSets not supported yet -- pharmvar - https://jira.hl7.org/browse/HTA-85

CodeSystems and ValueSets not supported yet -- sequenceontology - https://jira.hl7.org/browse/HTA-37 (should be in THO soon)

GenomicReport<DiagnosticReport>.result referencing Observation instances. We have defined our report profile to slice .result with our Observation profiles. We allow slicing, so we can ignore informational message

Observation.component instances that do not match our slices, but is OK (and this is ok since we use open slicing)

Our Observation profiles require a code from the Observation Category value set (LAB), but in some cases require additional codes from other value sets. Since this binding is "Preferred" the resources are still conformant, so we are supressing these messages.

These slice messages that have been reviewed. Each of these refer to (via derivedFrom) a Variant, and it seems it is a valid Variant instance. So, not clear why it does not match a known slice:

This is a publisher induced issue. The extension in question is introduced by the publisher. See https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/New.20ConceptMap.20Warning.20--.20induced.20by.20IG.20Publisher

the IG Validator returns different warnings on this error: https://github.com/HL7/fhir-ig-publisher/issues/420 - in short, the validator returns the "among choices" profiles in a different order different times.

Errors sorted by type