Validation Results for DaVinciPayerDataExchange

Generated Fri Feb 06 16:46:27 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.davinci-pdex#2.1.1 (canonical = http://hl7.org/fhir/us/davinci-pdex (history)). See Full QA Report & IP

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

Snomed: The IG specifies the US edition of SNOMED CT ✓

1 Profiles not based on US Core

Language Info:Stated Languages: n/a. IG Resource Lang: n/a. 11 of 187 (5%) of resources have a language. Population Policy: NONE
Publication Request:
RelatedIgs(None Found)
  • Publication Request is for v'2.1.0' but package version is v2.1.1
  • Publication Request is for version v2.1.0 which is already published
Supressed Messages:58 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.davinci-pdex2.1.1R4http://hl7.org/fhir/us/davinci-pdex
... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7Latest Release is 8.0.1
.... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.0.1
.... 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.24.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-snapshot1 OR5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch. Latest Release is 5.2.0
..... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 7.0.1
... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1
.... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1Latest Release is 8.0.1
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 7.0.1
..... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.2.0
..... hl7.fhir.uv.bulkdata2.0.0 OR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2Latest Release is 3.0.0
..... 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.0 (as above). Latest Release is 7.0.1
..... us.nlm.vsac0.11.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
..... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above)
..... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads (as 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.4.0
... hl7.fhir.us.core.3.1.13.1.1 UR4http://hl7.org/fhir/us/core/3.1.1http://hl7.org/fhir/us/core/3.1.1
.... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1Latest Release is 8.0.1
.... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0Latest Release is 7.0.1
.... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0Latest Release is 5.2.0
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
.... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
.... 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.1 (as above). Latest Release is 8.0.1
.... us.nlm.vsac0.19.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
... hl7.fhir.us.carin-bb2.1.0 MR4http://hl7.org/fhir/us/carin-bbhttp://hl7.org/fhir/us/carin-bb/STU2.1
.... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 7.0.1
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0
.... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1 (as above). Latest Release is 8.0.1
.... hl7.fhir.us.core.3.1.13.1.1 UR4http://hl7.org/fhir/us/core/3.1.1http://hl7.org/fhir/us/core/3.1.1 (as above)
.... us.nlm.vsac0.21.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
... hl7.fhir.us.davinci-crd2.1.0 MR4http://hl7.org/fhir/us/davinci-crdhttp://hl7.org/fhir/us/davinci-crd/STU2.1
.... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 7.0.1
.... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
.... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
.... hl7.fhir.us.core.v3113.1.1 UR4http://hl7.org/fhir/us/core/v311http://hl7.org/fhir/us/core/STU3.1.1 (as above)
.... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above)
.... hl7.fhir.us.davinci-hrex1.1.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above)
.... us.nlm.vsac0.19.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsac (as above). Latest Release is 0.24.0
... hl7.fhir.us.davinci-pas2.1.0 MR4http://hl7.org/fhir/us/davinci-pashttp://hl7.org/fhir/us/davinci-pas/STU2.1
.... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 7.0.1
.... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
.... hl7.fhir.us.core.v3113.1.1 UR4http://hl7.org/fhir/us/core/v311http://hl7.org/fhir/us/core/STU3.1.1 (as above)
.... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
.... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above)
.... hl7.fhir.us.davinci-crd2.0.0 VR4http://hl7.org/fhir/us/davinci-crdhttp://hl7.org/fhir/us/davinci-crd/STU2
..... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0Latest Release is 7.0.1
..... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0 (as above). Latest Release is 5.2.0
..... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1 (as above). Latest Release is 8.0.1
..... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above)
..... hl7.fhir.us.davinci-hrex1.0.0 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1Latest Release is 1.1.0
...... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1 (as above). Latest Release is 8.0.1
...... hl7.fhir.us.udap-security0.1.0 OR4http://hl7.org/fhir/us/udap-securityhttp://hl7.org/fhir/us/udap-security/2021SepLatest Release is 2.0.0
....... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1 (as above). Latest Release is 8.0.1
..... us.nlm.vsac0.11.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsac (as above). Latest Release is 0.24.0
.... hl7.fhir.us.davinci-hrex1.1.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above)
.... hl7.fhir.uv.subscriptions-backport.r41.1.0 MR4http://hl7.org/fhir/uv/subscriptions-backporthttp://hl7.org/fhir/uv/subscriptions-backport/STU1.1FHIR Version Mismatch
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.0.1
.... hl7.fhir.us.carin-bb2.0.0 OR4http://hl7.org/fhir/us/carin-bbhttp://hl7.org/fhir/us/carin-bb/STU2Latest Release is 2.1.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.0.1
..... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1 (as above). Latest Release is 8.0.1
..... us.nlm.vsac0.7.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
... hl7.fhir.us.davinci-atr2.1.0 MR4http://hl7.org/fhir/us/davinci-atrhttp://hl7.org/fhir/us/davinci-atr/STU2.1
.... hl7.terminology.r46.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.3.0Latest Release is 7.0.1
..... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
.... hl7.fhir.us.core.3.1.13.1.1 UR4http://hl7.org/fhir/us/core/3.1.1http://hl7.org/fhir/us/core/3.1.1 (as above)
.... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
.... hl7.fhir.uv.bulkdata2.0.0 OR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2 (as above). Latest Release is 3.0.0
.... hl7.fhir.uv.smart-app-launch2.1.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.1 (as above). Latest Release is 2.2.0
.... hl7.fhir.us.davinci-pdex-plan-net1.2.0 MR4http://hl7.org/fhir/us/davinci-pdex-plan-nethttp://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.2
..... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0 (as above). Latest Release is 7.0.1
..... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
..... hl7.fhir.us.core.v3113.1.1 UR4http://hl7.org/fhir/us/core/v311http://hl7.org/fhir/us/core/STU3.1.1 (as above)
..... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
..... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
..... hl7.fhir.us.davinci-hrex1.1.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above)
.... hl7.fhir.us.davinci-hrex1.1.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above)
.... hl7.fhir.uv.subscriptions-backport.r41.1.0 MR4http://hl7.org/fhir/uv/subscriptions-backporthttp://hl7.org/fhir/uv/subscriptions-backport/STU1.1FHIR Version Mismatch (as above)
.... hl7.fhir.us.davinci-cdex2.1.0 MR4http://hl7.org/fhir/us/davinci-cdexhttp://hl7.org/fhir/us/davinci-cdex/STU2.1
..... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0 (as above). Latest Release is 7.0.1
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
..... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
..... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
..... hl7.fhir.us.core.v3113.1.1 UR4http://hl7.org/fhir/us/core/v311http://hl7.org/fhir/us/core/STU3.1.1 (as above)
..... hl7.fhir.us.davinci-hrex1.1.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above)
..... hl7.fhir.us.davinci-pas2.1.0 MR4http://hl7.org/fhir/us/davinci-pashttp://hl7.org/fhir/us/davinci-pas/STU2.1 (as above)
..... hl7.fhir.us.carin-bb2.0.0 OR4http://hl7.org/fhir/us/carin-bbhttp://hl7.org/fhir/us/carin-bb/STU2 (as above). Latest Release is 2.1.0
..... hl7.fhir.us.davinci-dtr2.1.0 MR4http://hl7.org/fhir/us/davinci-dtrhttp://hl7.org/fhir/us/davinci-dtr/STU2.1
...... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 7.0.1
...... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
...... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 8.0.1
...... hl7.fhir.us.core.v6106.1.0 UR4http://hl7.org/fhir/us/core/v610http://hl7.org/fhir/us/core/STU6.1 (as above)
...... hl7.fhir.us.core.v3113.1.1 UR4http://hl7.org/fhir/us/core/v311http://hl7.org/fhir/us/core/STU3.1.1 (as above)
...... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above)
...... hl7.fhir.us.davinci-hrex1.1.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above)
...... hl7.fhir.us.davinci-crd2.1.0 MR4http://hl7.org/fhir/us/davinci-crdhttp://hl7.org/fhir/us/davinci-crd/STU2.1 (as above)
...... hl7.fhir.us.davinci-pas2.1.0 MR4http://hl7.org/fhir/us/davinci-pashttp://hl7.org/fhir/us/davinci-pas/STU2.1 (as above)
..... hl7.fhir.uv.sdc3.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above)
..... hl7.fhir.uv.subscriptions-backport.r41.1.0 MR4http://hl7.org/fhir/uv/subscriptions-backporthttp://hl7.org/fhir/uv/subscriptions-backport/STU1.1FHIR Version Mismatch (as above)
... hl7.fhir.us.davinci-pdex-plan-net1.2.0 MR4http://hl7.org/fhir/us/davinci-pdex-plan-nethttp://hl7.org/fhir/us/davinci-pdex-plan-net/STU1.2 (as above)
... hl7.fhir.us.ndh1.0.0 MR4http://hl7.org/fhir/us/ndhhttp://hl7.org/fhir/us/ndh/STU1
.... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0 (as above). Latest Release is 7.0.1
.... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1 (as above). Latest Release is 8.0.1
.... hl7.fhir.us.udap-security1.0.0 OR4http://hl7.org/fhir/us/udap-securityhttp://hl7.org/fhir/us/udap-security/STU1Latest Release is 2.0.0
..... hl7.terminology.r44.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/4.0.0Latest Release is 7.0.1
..... hl7.fhir.us.core3.1.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU3.1.1 (as above). Latest Release is 8.0.1
.... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0 (as above). Latest Release is 5.2.0
.... hl7.fhir.uv.subscriptions-backport.r41.1.0 MR4http://hl7.org/fhir/uv/subscriptions-backporthttp://hl7.org/fhir/uv/subscriptions-backport/STU1.1FHIR Version Mismatch (as above)
.... hl7.fhir.uv.bulkdata2.0.0 OR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2 (as above). Latest Release is 3.0.0
.... ihe.iti.mcsd3.8.0 OR4https://profiles.ihe.net/ITI/mCSDhttps://profiles.ihe.net/ITI/mCSD/3.8.0Matched to latest patch release (3.8.x->3.8.0). Latest Release is 4.0.0
..... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0Latest Release is 7.0.1
..... ihe.iti.balp1.1.0 OR4https://profiles.ihe.net/ITI/BALPhttps://profiles.ihe.net/ITI/BALP/1.1.0Latest Release is 1.1.4
... hl7.fhir.us.davinci-dtr2.1.0 MR4http://hl7.org/fhir/us/davinci-dtrhttp://hl7.org/fhir/us/davinci-dtr/STU2.1 (as above)
... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
... hl7.terminology.r46.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.3.0 (as above). Latest Release is 7.0.1
... hl7.fhir.uv.tools.r40.9.0 OR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/0.9.0Internal Dependency. Latest Release is 1.0.0
Templates: hl7.davinci.template#1.0.0 -> hl7.fhir.template#1.0.0 -> hl7.base.template#1.0.0 -> fhir.base.template#1.0.0
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/r4, https://tx-nordics.fhir.org/fhir/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:All OK
R5 Dependencies:
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 2.1.0
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 6, warn = 8, info = 57, broken links = 0, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors0235
/scratch/repo/fsh-generated/resources/DocumentReference-provider-attestation-doc-1011
/scratch/repo/fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex500
/scratch/repo/fsh-generated/resources/StructureDefinition-member-provider-treatment-relationship-group020
/scratch/repo/fsh-generated/resources/StructureDefinition-opt-out-details010
/scratch/repo/fsh-generated/resources/StructureDefinition-opt-out-reason010
/scratch/repo/fsh-generated/resources/StructureDefinition-treatment-relationship-details010
/scratch/repo/fsh-generated/resources/ValueSet-X12278ReviewDecisionReasonCode100

n/a Show Validation Information

warningThe jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
FHIRAccessPermissions.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The Payer-to-Payer APIs have a member-match operation that, in the case of a single member, returns a Patient/{FHIR_id} after a successful match. In the case of a bulk member-match, the matched members are returned in a Matched Member Group resource. In both scenarios the requesting (New) Payer may perform this match operation multiple times and SHOULD only be granted access to data for the matched members, whether in a Group or after a single match. An Implementer could choose to record the matched Id (either Patient or Group) in a Group record that is associated with the requesting entity. Subsequently, when the requesting entity performs the data request (e.g. via the Da Vinci Data Export Operation) the target FHIR_id could be checked against the Group Resource associated with the requesting entity. Access to data would be granted if the target Patient or Group Id is found in the Requesting Entities Group record.' CONFORMANCE_STATEMENT_WORD
PDexMedicationDispense.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' The Da Vinci PDex MedicationDispense profile SHALL be used to record a member's prescription drug claims when sharing data using the US Core 3.1.1 Implementation Guide. When using the US Core 6.1.0 Implementation Guide to exchange data the US Core MedicationDispense profile SHOULD be used.' CONFORMANCE_STATEMENT_WORD
PDexProvenance.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '§pdex-04: This SHOULD be used to:' CONFORMANCE_STATEMENT_WORD
PDexProvenance.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This guide SHALL define extensions to the provenance value sets as required to document the provenance of the information exchange.' CONFORMANCE_STATEMENT_WORD
SearchParameter-group-code.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'The FHIR Store MAY only have records for pdexprovidergroup, as used by the Provider Access API, and match, as used by the Payer-to-Payer Bulk API for members that successfully matched.' CONFORMANCE_STATEMENT_WORD
SearchParameter-pdex-medicationdispense-patient​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-pdex-medicationdispense-status​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = SHALL)' CONFORMANCE_STATEMENT_WORD
StructureDefinition-pdex-member-match-group​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' SHALL support searching for code for a Group. Group_Code Search Parameter GET [base]/Group?code={code} Example: GET [base]/Group?code="match" NOTE: Server should limit responses to records that requesting user or service (i.e. Payer in case of Member-Match) is permitted to access. For example, Matched Group lists for a Payer. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-pdex-priorauthorization​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Payers SHALL make available pending and active prior authorization decisions and related clinical documentation and forms for items and services, not including prescription drugs, including the date the prior authorization was approved, the date the authorization ends, as well as the units and services approved and those used to date, no later than one (1) business day after a provider initiates a prior authorization for the beneficiary or there is a change of status for the prior authorization.' CONFORMANCE_STATEMENT_WORD
StructureDefinition-pdex-provider-group​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' SHALL support searching for code for a Group. Group_Code Search Parameter GET [base]/Group?code={code} Example: GET [base]/Group?code="pdexprovidergroup" NOTE: Server should limit responses to records that requesting user or service is permitted to access. For example, Attributed Group lists for Practitioners working in a Facility where the system accessing is accessing on behalf of the facility. ' CONFORMANCE_STATEMENT_WORD
USCoreProcedure.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Note: Procedure records SHOULD only be created from ExplanationOfBenefit or CPCDS resources for items that are clinical procedures. Medications, facility charges and supplies SHOULD NOT be created as procedure records.' CONFORMANCE_STATEMENT_WORD
USCoreProcedure.htmlinformationThe html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: 'Note: Procedure records SHOULD only be created from ExplanationOfBenefit or CPCDS resources for items that are clinical procedures. Medications, facility charges and supplies SHOULD NOT be created as procedure records.' CONFORMANCE_STATEMENT_WORD
changehistory.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Change SHOULD to SHALL' CONFORMANCE_STATEMENT_WORD
datamapping.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Where a US Core 3.1.1. FHIR R4, US Core 6.1.0. FHIR R4 or US Core 7.0.0. §pdex-71: FHIR R4 Resource is not defined Health Plans SHALL map claims and clinical information to FHIR Profiles defined in this IG, or the Da Vinci HRex IG. §' CONFORMANCE_STATEMENT_WORD
datamapping.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'This Section describes the expected capabilities of the PDex with US Core 6.1 Support Server actor which is responsible for providing responses to the queries submitted by the PDex Requesters. The complete list of FHIR profiles, RESTful operations, and search parameters supported by PDex and US Core Servers are defined. Systems implementing this capability statement SHOULD meet the ONC 2015 Common Clinical Data Set (CCDS) access requirement for Patient Selection 170.315(g)(7) and Application Access - Data Category Request 170.315(g)(8) and the ONC U.S. Core Data for Interoperability (USCDI) Version 3 July 2022. PDex Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.' CONFORMANCE_STATEMENT_WORD
overview.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'To understand how to read an Implementation Guide implementers SHOULD refer to the How to Read page in the FHIR Specification.' CONFORMANCE_STATEMENT_WORD
overview.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'This IG also utilizes resources from the FHIR R4 Base Specification. Implementers SHOULD therefore refer to the following resources from the base specification:' CONFORMANCE_STATEMENT_WORD
overview.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'If the same data element is included in the member’s record from multiple sources for the same event, that information only needs to be mapped to FHIR and made available via the Patient Access API once. Payers SHOULD look at the data they maintain and ensure that information relevant to the member’s care and treatment over time is accurately represented – in this way, it may not be appropriate to include a single data element only once across multiple events.' CONFORMANCE_STATEMENT_WORD
payertopayerbulkexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' The PDex multi-member-match operation SHALL be performed as an Asynchronous operation. This SHOULD follow the methods identified in the Asynchronous Request Pattern defined in FHIR R4. Implementers SHALL follow the guidance provided in the Bulk Data Status Request section of the Async Request Pattern.' CONFORMANCE_STATEMENT_WORD
payertopayerbulkexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Registering of a client application or service to perform the bulk Payer-to-Payer Exchange SHOULD be registered in accordance with the approach defined in the SMART App Launch IG. That IG also encourages the use of the OAuth2.0 Dynamic Client Registration Protocol (DCRP). An alternative approach that is closely aligned with the DCRP protocol is to use the B2B protocols detailed in the HL7 Security for Scalable Registration, Authentication, and Authorization IG.' CONFORMANCE_STATEMENT_WORD
payertopayerexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'If a Consent is provided by an Authorized Representative, the person's demographic details SHOULD be included as a contained resource (such as Patient or RelatedPerson) within the consent record. The Authorized Representative SHOULD be identified as an actor with an appropriate SecurityRoleType, such as "DPOWATT", "HPOWATT" or similar value.' CONFORMANCE_STATEMENT_WORD
payertopayerexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' Payer-to-Payer Data Exchange SHOULD support the use of Bulk FHIR methods, as defined in the HL7 FHIR Bulk Data Access Implementation Guide. The §pdex-194: request/retrieval of data SHOULD use the FHIR Bulk Data Patient Level § Export and theBulk Data Export Operation Request Flow.' CONFORMANCE_STATEMENT_WORD
payertopayerexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The Patient Export Operation for Payer-to-Payer exchange SHOULD be constrained to the resources and profiles that the requester is permitted to access, such as the profiles identified in the table in the Data Retrieval Methods section of this page.' CONFORMANCE_STATEMENT_WORD
payertopayerexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Each Payer will create an mTLS bundle. The bundle will be signed by a Certificate Authority (CA) using public/private keys. The public key is included in the Endpoint record that is provided in the bundle. A public key SHOULD also be provided by the Trust Framework that is overseeing the Payer-to-Payer exchange process. The Associated Servers Extension will identify the PDex IG Base URI and the OAuth2.0 Dynamic Client Registration Protocol Endpoint. The PDex Capability Statement can be retrieved from [BASE URI]/metadata. The security section within the Capability Statement will define the SMART-on-FHIR endpoints for Access Tokens. The Registration Endpoint will only be accessible via the mTLS connection established using the mTLS endpoint information in the bundle.' CONFORMANCE_STATEMENT_WORD
payertopayerexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Upon completion of the submission process the Payer creates the endpoint and includes the signed payer public identity certificate and the public Trust Framework signing certificate into an Endpoint resource. This is incorporated into a bundle that includes the Payer's organization record and the organization record for the organization that manages the endpoint. Where the organization is both the payer and the managing organization there SHOULD still be two Organization records created.' CONFORMANCE_STATEMENT_WORD
payertopayerexchange.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'In step 3 of the Member-match process, the requesting Payer will have received a FHIR ID for the matched member (the MemberMatch ID). This Id SHOULD be submitted to the Access Token Endpoint with a JWT where the subject Id is the MemberMatch ID. The Authorization Server SHOULD use the Subject ID, confirms that consent for the Requesting Payer to access the Matched Member is still valid and therefore issue an access token that is scoped to the FHIR ID of the matched member, consequently bounding any subsequent FHIR API request to that specific Patient FHIR ID.' CONFORMANCE_STATEMENT_WORD
pdeximplementationactorsinteractionsdatapayloadsandmethods​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'All exchanges in this IG are for an individual. Where one member has permission to access the information for another member of the health plan, they SHOULD provide appropriate credentials to enable the exchange for that individual.' CONFORMANCE_STATEMENT_WORD
provider-access-api-v2.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '' CONFORMANCE_STATEMENT_WORD
provider-access-api-v2.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Members who fail any check SHALL be returned in separate Group resources: Non-matched members in a PDex Member No Match Group Treatment attestation constrained members in a PDex Member No Match Group Opt-out constrained members in a Member Opt-Out Group - The provider SHALL use the Matched Group Id to make subsequent $davinci-data-export operation requests to retrieve data for all, or a subset, of members. Alternatively, the provider MAY perform a new Provider-mMember-Match operation to receive a new Matched Member Group. - The matched group resource MAY be a short-lived group. No specific time limit is defined in this IG. An initial recommendation, subject to implementer feedback, is to make the group valid for 30 days. - Implementer feedback is sought on whether requests for less than 10 members SHOULD be handled as an interactive request, with larger bulk requests being processed as an asynchronous process. ' CONFORMANCE_STATEMENT_WORD
provider-access-api-v2.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Registering of a client application or service to perform the bulk Payer-to-Payer Exchange SHOULD be registered in accordance with the approach defined in the SMART App Launch IG. That IG also encourages the use of the OAuth2.0 Dynamic Client Registration Protocol (DCRP). An alternative approach that is closely aligned with the DCRP protocol is to use the B2B protocols detailed in the HL7 Security for Scalable Registration, Authentication, and Authorization IG.' CONFORMANCE_STATEMENT_WORD
provider-access-api.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'A health plan member is entitled to opt-out of data sharing via the Provider Access API. PDex defines a consent profile that enables a member to deny sharing via the Provider Access API. A member SHOULD also be able to update their preference to revoke a previous denial.' CONFORMANCE_STATEMENT_WORD
provider-access-api.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' Attribution lists SHALL be searchable via a secure RESTful API. Access to the Group resource to READ attribution lists SHOULD be scoped to the appropriate Organization, Facility, Provider or their authorized representative that is acting on the behalf of the Provider.' CONFORMANCE_STATEMENT_WORD
provider-access-api.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Registering of a client application or service to perform the bulk Payer-to-Payer Exchange SHOULD be registered in accordance with the approach defined in the SMART App Launch IG. That IG also encourages the use of the OAuth2.0 Dynamic Client Registration Protocol (DCRP). An alternative approach that is closely aligned with the DCRP protocol is to use the B2B protocols detailed in the HL7 Security for Scalable Registration, Authentication, and Authorization IG.' CONFORMANCE_STATEMENT_WORD
securityandprivacy.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The PDex IG adopts the Security and Privacy approach detailed in the Health Record Exchange (HRex) IG. Implementers SHOULD also take note of the guidance in the FHIR R4 specification on the HL7 core security page. The Security and Privacy section of the HRex IG addresses:' CONFORMANCE_STATEMENT_WORD
usecasescenarios.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' A payer MAY choose to support FHIR resource data versioning in their API including Patient, Practitioner, Organization and Location resources. In such cases resources SHOULD follow the vread guidance in the HTTP section of the FHIR specification.' CONFORMANCE_STATEMENT_WORD
5warningThe HTML fragment 'expansion-params.xhtml' is not included anywhere in the produced implementation guide

fsh-generated/resources/DocumentReference-provider-attestation-doc-1.json Show Validation Information (1)

PathSeverityMessage
DocumentReference​.content[0]​.format​.system (l53​/c8)warningA definition for CodeSystem 'http://ihe.net/fhir/ValueSet/IHE.FormatCode.codesystem' could not be found, so the code cannot be validated (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM
DocumentReference​.content[0]​.format (l53​/c8)informationThe code provided (http://ihe.net/fhir/ValueSet/IHE.FormatCode.codesystem#urn:ihe:iti:xds:2017:mimeTypeSufficient) is not in the value set 'DocumentReference Format Code Set' (http://hl7.org/fhir/ValueSet/formatcodes|4.0.1), and a code is recommended to come from this value set (from server, see log, or see the servers logic) Terminology_TX_Confirm_6

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex.json Show Validation Information (1)

PathSeverityMessage
ImplementationGuide​.definition​.extension[29]​.url (l1​/c16844)errorNo definition could be found for URL value 'http://hl7.org/fhir/tools/StructureDefinition/expansion-parameters'

Editor's Comment: Tools extension not found - this is generated by the IG Publisher Type_Specific_Checks_DT_URL_Resolve
ImplementationGuide​.dependsOn[1] (l1​/c9286)errorThe canonical URL http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core points to the package hl7.fhir.us.core which is inconsistent with the stated packageId of hl7.fhir.us.core.v610

Editor's Comment: Implementation Guide Errors v610@npm: format fails for v610 or V311 IG_DEPENDENCY_CLASH_PACKAGEID
ImplementationGuide​.dependsOn[1] (l1​/c9286)errorThe packageId hl7.fhir.us.core.v610 points to the canonical http://hl7.org/fhir/us/core/v610 which is inconsistent with the stated canonical of http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core

Editor's Comment: Implementation Guide Errors v610@npm: format fails for v610 or V311 IG_DEPENDENCY_CLASH_CANONICAL
ImplementationGuide​.dependsOn[2] (l1​/c9678)errorThe canonical URL http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core points to the package hl7.fhir.us.core which is inconsistent with the stated packageId of hl7.fhir.us.core.3.1.1

Editor's Comment: Implementation Guide Errors v610@npm: format fails for v610 or V311 IG_DEPENDENCY_CLASH_PACKAGEID
ImplementationGuide​.dependsOn[2] (l1​/c9678)errorThe packageId hl7.fhir.us.core.3.1.1 points to the canonical http://hl7.org/fhir/us/core/3.1.1 which is inconsistent with the stated canonical of http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core

Editor's Comment: Implementation Guide Errors v610@npm: format fails for v610 or V311 IG_DEPENDENCY_CLASH_CANONICAL

fsh-generated/resources/StructureDefinition-member-provider-treatment-relationship-group.json Show Validation Information (1)

PathSeverityMessage
StructureDefinition​.snapshot (l1​/c108562)warningThe slice 'valueReference' on path 'Group.characteristic.value[x]' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/us​/davinci-pdex​/StructureDefinition​/member-provider-treatment-relationship-group')warningThe Implementation Guide contains no examples for this profile

fsh-generated/resources/StructureDefinition-opt-out-details.json Show Validation Information (1)

PathSeverityMessage
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/us​/davinci-pdex​/StructureDefinition​/opt-out-details')warningThe Implementation Guide contains no examples for this extension

fsh-generated/resources/StructureDefinition-opt-out-reason.json Show Validation Information (1)

PathSeverityMessage
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/us​/davinci-pdex​/StructureDefinition​/opt-out-reason')warningThe Implementation Guide contains no examples for this extension

fsh-generated/resources/StructureDefinition-treatment-relationship-details.json Show Validation Information (1)

PathSeverityMessage
StructureDefinition​.where(url = 'http:​/​/hl7​.org​/fhir​/us​/davinci-pdex​/StructureDefinition​/treatment-relationship-details')warningThe Implementation Guide contains no examples for this extension

fsh-generated/resources/ValueSet-X12278ReviewDecisionReasonCode.json Show Validation Information (1)

PathSeverityMessage
ValueSet​.where(id = 'X12278ReviewDecisionReasonCode')errorError from https://tx.fhir.org/r4: A definition for CodeSystem 'https://codesystem.x12.org/external/886' could not be found, so the value set cannot be expanded (from server, see log)

Suppressed Messages (Warnings, hints, broken links)

DTR STU2.0.1 is being reported as newer than STU2.1

DTR version warnings

Da Vinci Template Warnings

Example link - Warning introduced in Publisher 2.0.3

Example link to binary resource - Warning introduced in Publisher 2.0.3

FHIR-29796 PDex Device uses base resource not US Core Implantable Device Profile. Pdex-Device enables payers to record non-implantable device data. CGP Voted on variance approval: Drew Torres/Eric Haas: 9-0-0

FHIR-49009 Raised for issue in US Core 7.0.0 failing to recognize THO CodeSystem.

HL7 Terminology version warnings

Implementation Guide Errors v610@npm: format fails for v610 or V311

Information: Reference to draft CodeSystem

Information: Repeating Element

References to Experimental CodeSystem

Reviewed and identified as not being HTML tags.

Slicing Warnings

TSMG 2025-04-21 Motion passes 8-0-0 https://confluence.hl7.org/spaces/TSMG/pages/325464658/2025-04-21+TSMG+Agenda+and+Minutes. Exceptions Granted for PDex specific code systems: IdentifierTypeCS, MtlsObjectCodeCS, OrgTypeCS, PDexAdjudicationCS, PDexAdjudicationDiscriminator, PDexIdentifierType, PDexPayerAdjudicationStatus, PDexSupportingInfoType, PdexMemberAttributionCS, PdexMultiMemberMatchResultCS, PriorAuthorizationValueCodes, ProvenanceAgentRoleType, ProvenancePayerDataSource

Tools extension not found - this is generated by the IG Publisher

US Core 8.0.0 released but Da Vinci Guides are supporting US Core 3.1.1, 6.1.0 and 7.0.0

UUEncode the Jira link to avoid an XML error with issuetype

Unable to Check HIPPS Codes

Warning introduced in Publisher 1.8.23+

Warnings for non-existent URLs in examples

X12 Code Systems and Value Sets that are referenced in the guide but not freely available

Errors sorted by type

BUNDLE_SIGNATURE_NOT_CHECKED_KIND

fsh-generated/resources/Bundle-example-mtls-endpoint-bundle.jsonThe signature format 'application/x-x509-ca-cert' is not checked (known formats: application/jose and application/pkcs7-signature)

IG_DEPENDENCY_CLASH_CANONICAL

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex.jsonThe packageId hl7.fhir.us.core.v610 points to the canonical http://hl7.org/fhir/us/core/v610 which is inconsistent with the stated canonical of http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core
fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex.jsonThe packageId hl7.fhir.us.core.3.1.1 points to the canonical http://hl7.org/fhir/us/core/3.1.1 which is inconsistent with the stated canonical of http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core

IG_DEPENDENCY_CLASH_PACKAGEID

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex.jsonThe canonical URL http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core points to the package hl7.fhir.us.core which is inconsistent with the stated packageId of hl7.fhir.us.core.v610
fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex.jsonThe canonical URL http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core points to the package hl7.fhir.us.core which is inconsistent with the stated packageId of hl7.fhir.us.core.3.1.1

MSG_DRAFT

fsh-generated/resources/Consent-provider-treatment-attestation-1.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/Consent-provider-treatment-attestation-1.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/Consent-treatment-attestation-ex1.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/Consent-treatment-attestation-ex1.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/Consent-treatment-attestation-ex2.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/Consent-treatment-attestation-ex2.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/Parameters-provider-bulk-member-match-in.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/Parameters-provider-bulk-member-match-in.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/Parameters-provider-member-match-request-001.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/Parameters-provider-member-match-request-001.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/Parameters-provider-member-match-request-001.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/Parameters-provider-member-match-request-001.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/ValueSet-attestation-provision-type-valueset.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-provision-type|4.0.1
fsh-generated/resources/ValueSet-attestation-status-valueset.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1
fsh-generated/resources/ValueSet-attestation-status-valueset.jsonReference to draft CodeSystem http://hl7.org/fhir/consent-state-codes|4.0.1

MSG_EXPERIMENTAL

fsh-generated/resources/Group-Example-PDex-Provider-Group.jsonReference to experimental CodeSystem http://hl7.org/fhir/us/davinci-atr/CodeSystem/atr-attribution-list-status|2.1.0

Terminology_TX_Confirm_6

fsh-generated/resources/DocumentReference-provider-attestation-doc-1.jsonThe code provided (http://ihe.net/fhir/ValueSet/IHE.FormatCode.codesystem#urn:ihe:iti:xds:2017:mimeTypeSufficient) is not in the value set 'DocumentReference Format Code Set' (http://hl7.org/fhir/ValueSet/formatcodes|4.0.1), and a code is recommended to come from this value set

Type_Specific_Checks_DT_URL_Resolve

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.davinci-pdex.jsonNo definition could be found for URL value 'http://hl7.org/fhir/tools/StructureDefinition/expansion-parameters'

UNKNOWN_CODESYSTEM

fsh-generated/resources/DocumentReference-provider-attestation-doc-1.jsonA definition for CodeSystem 'http://ihe.net/fhir/ValueSet/IHE.FormatCode.codesystem' could not be found, so the code cannot be validated

VALUESET_CODE_CONCEPT_HINT

fsh-generated/resources/ValueSet-PDexAdjudication.jsonWrong Display Name 'Coinsurance' for http://hl7.org/fhir/us/carin-bb/CodeSystem/C4BBAdjudication#coinsurance. Valid display is 'Co-insurance' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
fsh-generated/resources/ValueSet-attestation-provision-type-valueset.jsonWrong Display Name 'Permit' for http://hl7.org/fhir/consent-provision-type#permit. Valid display is 'Opt In' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code