Validation Results for GenomicsReporting

Generated Tue Nov 19 22:06:11 UTC 2024, FHIR version 4.0.1 for hl7.fhir.uv.genomics-reporting#3.0.0 (canonical = http://hl7.org/fhir/uv/genomics-reporting (history)). See Full QA Report

Quality Checks
Publisher Version:IG Publisher Version: v1.7.3
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
pathhttp://hl7.org/fhir/uv/genomics-reporting/STU3
Pub-Modeworking release
statustrial-use
Release-Labelrelease
sequenceSTU 3
descSTU3 update of Genomics Reporting IG
descmd

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')
  • This release is not labelled as a milestone or technical correction, so should have a patch version (3.0.0)
  • This release is labelled as a working release in the sequence 'STU 3'. This is an unexpected workflow - check that the sequence really is correct.
Supressed Messages:91 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.uv.genomics-reporting3.0.0R4http://hl7.org/fhir/uv/genomics-reporting
... hl7.terminology.r46.1.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0
... hl7.fhir.uv.extensions.r45.1.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0
Templates: hl7.fhir.template#0.10.1 -> hl7.base.template#0.10.1 -> fhir.base.template#0.8.1. Tools: 0.3.0
Dependent IGs:1 guide
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/r4 (details)
HTA Analysis:All OK
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 3.0.0-ballot
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 0, warn = 0, info = 0, broken links = 0
FilenameErrorsWarningsHints
Build Errors000

n/a Show Validation Information

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

CG has reviewed these CodeSystems and have decided to keep this in our IG

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

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 -- genenames -- https://terminology.hl7.org/CodeSystem-v3-hgnc.html

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

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://terminology.hl7.org/CodeSystem-SO.html

Each of these codes have been validated (as of Jul 5 2024), so suppressing these warnings until HPO becomes a supported code system.

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

In several places we use experimental ValueSets with experimental bindings. The elements are marked as experimental. So we suppress the warning. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/consent-content-code.20warning

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 Suppressing these messages.

Suppress all references to example CodeSystems

These slice messages have been reviewed, and our StructureDefinition apporpriately defines the slices of extension, and examples look valid. Have asked for feedback here: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/slicing.20in.20Observation.2Ecomponent.2Eextension.20information.20help.3F

These slice messages that have been reviewed. Each of these refer to (via derivedFrom) a Variant, and are a valid Variant instance. They are similar to ones mentioned on https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/slicing.20in.20Observation.2Ecomponent.2Eextension.20information.20help.3F

We define several experimental CodeSystems that we use, so OK to suppress this for all IG defined CSs

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.

the mappings in this concept map have been human reviewed and is correct

this code has been human reviewed and is correct

Errors sorted by type