Validation Results for DaVinciHealthRecordExchangeHRex

Generated Wed Nov 13 17:56:23 UTC 2024, FHIR version 4.0.1 for hl7.fhir.us.davinci-hrex#1.1.0 (canonical = http://hl7.org/fhir/us/davinci-hrex (history)). See Full QA Report

Quality Checks
Publisher Version:IG Publisher Version: v1.7.2
Publication Code:davinci-hrex . PackageId = hl7.fhir.us.davinci-hrex, Canonical = http://hl7.org/fhir/us/davinci-hrex
Realm Check for US:

Snomed: The IG specifies the US edition of SNOMED CT

2 Profiles not based on US Core

Publication Request:
package-idhl7.fhir.us.davinci-hrex
version1.1.0
pathhttp://hl7.org/fhir/us/davinci-hrex/STU1.1
Pub-Modemilestone
statustrial-use
Release-LabelSTU 1.1
sequenceSTU 1.1
descSTU 1.1.0 Release
descmd

STU 1.1.0 release with US Core 3.1, 6.1, and 7.0. See list of changes

Proposed path for this milestone publication should usually be canonical with either sequence or version appended
Supressed Messages:39 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.davinci-hrex1.1.0R4http://hl7.org/fhir/us/davinci-hrex
... hl7.terminology.r46.0.2 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.0.2
... hl7.fhir.uv.extensions.r45.1.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0
... hl7.fhir.us.core.v7007.0.0 UR4http://hl7.org/fhir/us/core/v700http://hl7.org/fhir/us/core/STU7
.... hl7.fhir.us.core7.0.0 MR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7
..... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 6.0.2
..... hl7.fhir.uv.smart-app-launch2.0.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2Latest Release is 2.2.0
..... us.nlm.vsac0.18.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.20.0
..... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3
...... hl7.fhir.r4.examples4.0.1 OR4http://hl7.org/fhirhttp://hl7.org/fhir/R4Latest Release is 5.0.0
..... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads
..... hl7.fhir.uv.extensions5.1.0-cibuild VR5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch
...... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 6.0.2
... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1Latest Release is 7.0.0
.... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 6.0.2
.... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.1.0
.... hl7.fhir.uv.bulkdata2.0.0 MR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2
.... hl7.fhir.uv.smart-app-launch2.1.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.1Latest Release is 2.2.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0see above. Latest Release is 6.0.2
.... us.nlm.vsac0.11.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.20.0
.... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3see above
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvadssee above
.... ihe.formatcode.fhir1.1.0 OR4https://profiles.ihe.net/fhir/ihe.formatcode.fhirhttps://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0Latest Release is 1.3.0
... hl7.fhir.us.core.v3113.1.1 UR4http://hl7.org/fhir/us/core/v311http://hl7.org/fhir/us/core/STU3.1.1
.... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1Latest Release is 7.0.0
... us.nlm.vsac0.19.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.20.0
Templates: hl7.davinci.template#current -> hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: 0.3.0
Dependent IGs:10 guides
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/r4 (details)
HTA Analysis:All OK
R5 Dependencies:
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 1.0.0
Comparison with version 1.1.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)

HRex needs Coverage pointing to a patient with no identifier - submitted to US Core https://jira.hl7.org/browse/FHIR-46468

HRex needs a patient with no identifier - US Realm approved: https://jira.hl7.org/browse/FHIR-33538, new proposal https://jira.hl7.org/browse/FHIR-46468

Narrative doesn't make sense in resources passed to a real-time operation

The patterns are only locking down the system, which is the discriminator for the slices, so this is fine.

The terminology validation here is incorrect in R4, but these codes are both valid

There is no location in the IG where it makes sense to use this profile. It's created for downstream IGs. The definition is sufficiently simple that there's no possibility of errors in the construction.

These additional coverage classes are not (currently) part of the profile and are not expected to match slices

These are inherited from US Core

These are termerminology server limitations

These are tested by the parameters input examples

These code systems are not currently supported by the Tx server - and the X12 ones likely won't ever be

These code systems should not be draft in THO. The terminology work group is trying to fix these

These identifiers are 'extra' and aren't expected to match any slice

This is an issue in the core spec

This is an issue with the underlying R5 terminology and should be addressed via a system-wide update

This will be done in a future release

Errors sorted by type