Validation Results for DaVinciPayerDataExchange

Generated Fri Jul 31 19:08:47 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.davinci-pdex#2.2.0 (canonical = http://hl7.org/fhir/us/davinci-pdex (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.3.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:
package-idhl7.fhir.us.davinci-pdex
version2.2.0
pathhttp://hl7.org/fhir/us/davinci-pdex/STU2.2
Pub-Modemilestone
statustrial-use
Release-LabelSTU 2.2
Sequence (Group)STU2.2 (current: 'STU2.1', others = 'STU 1','STU1','STU2')
descThis STU 2.2 specification has undergone ballot and connectathon testing. It has been evolved to meet the requirements of the Advancing Interoperability and Prior Authorization rule. As part of that process. Feedback is welcome and may be submitted through the FHIR JIRA tracker indicating US Da Vinci PDex as the specification.
descmd

This STU 2.2 specification has undergone ballot and connectathon testing. It is expected to continue to evolve, possibly significantly, as part of that process. Feedback is welcome and may be submitted through the FHIR JIRA tracker indicating US Da Vinci PDex as the specification. If balloting on this IG, please submit your comments via the tracker and reference them in your ballot submission implementation guide.

This guide can be reviewed offline. Go to the Downloads section. Click on the link to download the full Implementation Guide as a zip file. Expand the zip file and use a web browser to launch the index.html file in the directory created by the zip extract process. External hyperlinks in the guide will not be available unless you have an active internet connection.

Financial Management is the Sponsoring Work Group for this Implementation Guide.

The Payer Data Exchange (PDex) Implementation Guide (IG) is provided for Payers/Health Plans to enable them to create a Health History for a Member using clinical resources (based on US Core 3.1.1 and 6.1.0 Profiles based on FHIR R4) which can be understood by providers and, if they choose to, committed to their Electronic Medical Records (EMR) System.

The PDex work group has made changes to the original version of the IG following the publication of the final CMS Interoperability and Patient Access Rule (CMS-9115_ and in STU 2.1 the IG has been expanded to meet the requirements of the CMS Prior Authorization Rule (CMS-0057).

This IG uses the same Member Health History payload for member-authorized exchange of information with other Health Plans, with Providers and with Third-Party Applications. It describes the interaction patterns that, when followed, allow the various parties involved in managing healthcare and payer data to more easily integrate and exchange data securely and effectively.

This IG covers the exchange of:

  • Claims-based information (without financials)
  • Clinical Information (such as Lab Results, Allergies and Conditions)
  • Prior Authorization information

This IG covers the exchange of this information using US Core and Da Vinci Health Record Exchange (HRex) Profiles. This superset of clinical profiles forms the Health History for a Health Plan Member.

This IG covers the exchange of the Health History for a member in the following scenarios:

  • Provider requested exchange using SMART-on-FHIR Bulk exchange
  • Health Plan Exchange using SMART-on-FHIR
  • Member-authorized Health Plan to Health Plan exchange
  • Member-authorized Health Plan to Third-Party Application exchange

The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability and Patient Access Final Rule.

There are items in this guide that are subject to update. This includes:

  • Value Sets
  • Vocabularies (X12, NUBC etc.)
  • Examples

The Vocabulary, Value Sets and codings used to express data in this IG are subject to review and will be reconciled with X12.

See the Table of Contents for more information.

changeschangehistory.html
RelatedIgs(None Found)
No Messages found - all good
Supressed Messages:245 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.davinci-pdex2.2.0R4http://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 9.0.0
.... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.3.0
.... 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 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3Latest Release is 4.0.0
..... 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.3.0
..... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 7.3.0
... 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 9.0.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.3.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.3.0
..... 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 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
..... 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.5.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 9.0.0
.... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2
..... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
.... 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)
.... 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.2.0 MR4http://hl7.org/fhir/us/carin-bbhttp://hl7.org/fhir/us/carin-bb/STU2.2
.... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
.... 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.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... us.nlm.vsac0.24.0 MR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsac
... hl7.fhir.us.davinci-crd2.2.1 MR4http://hl7.org/fhir/us/davinci-crdhttp://hl7.org/fhir/us/davinci-crd/2.2.1
.... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.xver-r5.r40.1.0 UR4http://hl7.org/fhir/uv/xverhttp://hl7.org/fhir/uv/xver-r5.r4/0.1.0
..... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
.... 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.sdc4.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU4
..... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
..... hl7.fhir.uv.xver-r5.r40.1.0 UR4http://hl7.org/fhir/uv/xverhttp://hl7.org/fhir/uv/xver-r5.r4/0.1.0 (as above)
..... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2 (as above)
..... hl7.fhir.r4.examples4.0.1 OR4http://hl7.org/fhirhttp://hl7.org/fhir/R4 (as above). Latest Release is 5.0.0
..... hl7.fhir.uv.extensions.r45.3.0-ballot-tc1 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0-ballot-tc1Latest Release is 5.3.0
...... hl7.terminology.r46.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0Latest Release is 7.3.0
....... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.us.davinci-hrex1.2.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/1.2.0 (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.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2 (as above)
.... hl7.fhir.uv.cds-hooks3.0.0-ballot IR4http://cds-hooks.hl7.orghttp://cds-hooks.hl7.org/2026Jan
..... hl7.terminology.r47.0.1 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.1Latest Release is 7.3.0
...... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.cds-hooks-library1.0.1 MR4http://cds-hooks.hl7.org/hookshttp://cds-hooks.hl7.org/hooks/STU1
..... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
... hl7.fhir.us.davinci-pas2.2.1 MR4http://hl7.org/fhir/us/davinci-pashttp://hl7.org/fhir/us/davinci-pas/2.2.1
.... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.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 9.0.0
.... hl7.fhir.uv.sdc4.0.0 MR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU4 (as above)
.... hl7.fhir.uv.xver-r5.r40.1.0 UR4http://hl7.org/fhir/uv/xverhttp://hl7.org/fhir/uv/xver-r5.r4/0.1.0 (as above)
.... hl7.fhir.us.davinci-crd2.2.1 MR4http://hl7.org/fhir/us/davinci-crdhttp://hl7.org/fhir/us/davinci-crd/2.2.1 (as above)
.... hl7.fhir.us.davinci-hrex1.2.0 MR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/1.2.0 (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.3.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0Latest Release is 5.3.0
..... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
..... 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 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1Latest Release is 1.2.0
...... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0Latest Release is 7.3.0
...... 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.3.0
...... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
...... 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)
...... 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 OR4http://hl7.org/fhir/us/davinci-pashttp://hl7.org/fhir/us/davinci-pas/STU2.1Latest Release is 2.2.1
...... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 7.3.0
...... 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.3.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 9.0.0
...... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
...... 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.3.0
....... 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.3.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 9.0.0
....... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
....... hl7.fhir.us.davinci-hrex1.0.0 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1Latest Release is 1.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 9.0.0
........ 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 9.0.0
....... 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 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above). Latest Release is 1.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
....... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.3.0
...... hl7.fhir.us.carin-bb2.0.0 OR4http://hl7.org/fhir/us/carin-bbhttp://hl7.org/fhir/us/carin-bb/STU2Latest 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.3.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 9.0.0
....... 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.carin-bb2.0.0 OR4http://hl7.org/fhir/us/carin-bbhttp://hl7.org/fhir/us/carin-bb/STU2 (as above). Latest Release is 2.2.0
..... hl7.fhir.us.davinci-dtr2.1.0 OR4http://hl7.org/fhir/us/davinci-dtrhttp://hl7.org/fhir/us/davinci-dtr/STU2.1Latest Release is 2.2.0
...... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 7.3.0
...... 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.3.0
...... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
...... 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 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
...... hl7.fhir.us.davinci-hrex1.1.0 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above). Latest Release is 1.2.0
...... hl7.fhir.us.davinci-crd2.1.0 OR4http://hl7.org/fhir/us/davinci-crdhttp://hl7.org/fhir/us/davinci-crd/STU2.1Latest Release is 2.2.1
....... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 7.3.0
....... 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.3.0
....... hl7.fhir.us.core7.0.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU7 (as above). Latest Release is 9.0.0
....... 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 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
....... hl7.fhir.us.davinci-hrex1.1.0 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above). Latest Release is 1.2.0
....... 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 OR4http://hl7.org/fhir/us/davinci-pashttp://hl7.org/fhir/us/davinci-pas/STU2.1 (as above). Latest Release is 2.2.1
..... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.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.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.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2 (as above)
... 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.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.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.1 (as above). Latest Release is 9.0.0
.... 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 9.0.0
.... 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.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.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 9.0.0
..... hl7.fhir.us.davinci-hrex1.1.0 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above). Latest Release is 1.2.0
.... hl7.fhir.us.davinci-hrex1.1.0 OR4http://hl7.org/fhir/us/davinci-hrexhttp://hl7.org/fhir/us/davinci-hrex/STU1.1 (as above). Latest Release is 1.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.us.davinci-cdex2.1.0 MR4http://hl7.org/fhir/us/davinci-cdexhttp://hl7.org/fhir/us/davinci-cdex/STU2.1 (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.3.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 9.0.0
.... 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.3.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 9.0.0
.... 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.3.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.3.0
..... 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 OR4http://hl7.org/fhir/us/davinci-dtrhttp://hl7.org/fhir/us/davinci-dtr/STU2.1 (as above). Latest Release is 2.2.0
... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0
.... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
... hl7.terminology.r47.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.2.0Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0 (as above)
... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2Internal Dependency. (as above)
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 = 0, warn = 3, info = 0, broken links = 0, pinned = 394 (when multiples).
FilenameErrorsWarningsHints
Build Errors010
/scratch/repo/fsh-generated/resources/ValueSet-PDexPAInstitutionalProcedureCodes010
/scratch/repo/fsh-generated/resources/ValueSet-PDexPAInstitutionalProcedureCodesVS010

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)

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

PathSeverityMessageValidating
ValueSet​.where(id = 'PDexPAInstitutionalProcedureCodes')warningError from https://tx.fhir.org/r4: Error: A definition for CodeSystem 'https://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' could not be found, so the value set cannot be expanded (from server, see log) --

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

PathSeverityMessageValidating
ValueSet​.where(id = 'PDexPAInstitutionalProcedureCodesVS')warningError from https://tx.fhir.org/r4: Error: A definition for CodeSystem 'https://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets' could not be found, so the value set cannot be expanded (from server, see log) --

Suppressed Messages (Warnings, hints, broken links)

CARIN BB / R4 core / HL7 Terminology / VSAC — multi-version collisions

DTR 3.0.1 was published superseding 2.1.0. PDex's reference to DTR is via inherited CRD dependencies; bumping DTR independently of CRD is not a coherent change. CRD was bumped to 2.2.1 in this update; DTR remains at 2.1.0 to match CRD 2.2.1's own DTR dependency. Will be revisited in a future cycle alongside any further CRD bump.

Da Vinci HRex — pinned to 1.2.0 (from 1.0.0 / 1.1.0 / 1.2.0)

Da Vinci PAS — pinned to 2.2.1 (from 2.1.0 / 2.2.1). The PAS 2.1.0 package remains reachable in the dependency graph via Da Vinci CRD 2.2.1's own PAS dependency declaration; PDex declares PAS 2.2.1 directly under FHIR-57521. pin-multiples disambiguates each PAS-extension canonical to 2.2.1. Enumerated explicitly per FMG guidance.

PDexProvenance.html — 2 messages (both "no conformance term")

Reason for suppression: CPT (Current Procedural Terminology) codes are American Medical Association proprietary intellectual property. AMA does not permit free enumeration of CPT codes by public terminology servers, so the IG Publisher's terminology validator cannot bulk-expand or validate CPT bindings. CPT references in PDex examples are correct US healthcare usage; the warning is a licensing artifact.

Reason for suppression: Examples reference a binary attachment and a canonical IG URL as illustrative placeholders, not resolvable links. IG Publisher 2.0.3 introduced a broader "URL value" link check that flags these.

Reason for suppression: HIPPS (Health Insurance Prospective Payment System) codes are published by CMS at the cited URL but CMS does not host a FHIR CodeSystem resource at that URL. The reference is correct (matches the pattern used by CARIN BB), but the IG Publisher cannot fetch a definition.

Reason for suppression: Multiple PDex profiles slice elements (typically Group.characteristic and Consent.provision) using extensible discriminators. The validator emits "this element does not match any known slice" when an instance includes a slice variant outside the closed set, which is by design in PDex (the slicing is open, not closed). This pattern is broad rather than enumerated because the same warning fires in dozens of example instances across the IG; narrowing it would require listing every affected instance and would obscure the underlying design choice.

Reason for suppression: NDC code 54458-872-10 is recognised by the public terminology snapshot but flagged as inactive in the FDA database. The code is used in an example resource (illustrating MedicationDispense coding) and remains a valid demonstration of the data shape. Reviewed and accepted for use in examples — corresponds to a historical product NDC that is semantically correct for the example narrative.

Reason for suppression: PDex defines local code systems that have not been moved to terminology.hl7.org. The IG Publisher emits an informational note encouraging migration to a THO URL. The TSMG (Terminology Sub-Management Group) reviewed the PDex-defined code systems on 2025-04-21 and granted an explicit exception (motion passed 8-0-0). The minutes are at https://confluence.hl7.org/spaces/TSMG/pages/325464658/2025-04-21+TSMG+Agenda+and+Minutes Exception covers: IdentifierTypeCS, MtlsObjectCodeCS, OrgTypeCS, PDexAdjudicationCS, PDexAdjudicationDiscriminator, PDexIdentifierType, PDexPayerAdjudicationStatus, PDexSupportingInfoType, PdexMemberAttributionCS, PdexMultiMemberMatchResultCS, PriorAuthorizationValueCodes, ProvenanceAgentRoleType, ProvenancePayerDataSource.

Reason for suppression: PDex depends on hl7.terminology.r4 7.2.0 directly, but the dependency graph also reaches older terminology.r4 versions transitively (CARIN BB via 5.5.0, CRD via 6.3.0, other Da Vinci deps via 3.1.0). When the same CodeSystem or ValueSet canonical URL is defined in multiple terminology.r4 versions with different per-resource version metadata, `pin-canonicals: pin-multiples` resolves to the per-resource version found in the highest-numbered terminology.r4 package — i.e., 7.2.0 — and emits an information-level note documenting the pin. This is the desired behaviour: the latest HL7 Terminology release is the intended source for CodeSystem and ValueSet definitions, so resolving every multi- version reference to the 7.2.0 entry ensures PDex artifacts validate against the current code definitions rather than an older snapshot. Each enumerated entry below records one per-resource pin produced by the resolver. If the direct terminology.r4 dependency is bumped beyond 7.2.0 in a future PDex release, the per-resource version strings on these lines may need to be updated to match the new package's per-resource versions.

Reason for suppression: PDex example resources reference synthetic payer URLs (xxxhealthplan.com, exampleplan.com, mtls-dev-dmdh.safhir.io) in `identifier.system`, `Endpoint.address`, and similar slots. These URLs do not — and intentionally should not — resolve, because the resources are illustrative examples, not real-world endpoints. The IG Publisher emits a "No definition could be found for URL value" WARNING at each such reference. Patterns enumerate the source resource path (Bundle id, Patient id, Endpoint id, ExplanationOfBenefit id) and use the IG Publisher's startsWith semantics ("text%" — no leading `%`) so the trailing URL or further detail varies per occurrence while the suppression remains scoped to the specific example resource. New example resources that introduce additional synthetic URLs will surface as unmatched warnings for explicit review.

Reason for suppression: PDex examples and profiles reference code systems whose status in the upstream HL7 terminology repository is "draft" or "experimental". The references are stable canonical URLs; the upstream status is a publication-cycle artifact that does not affect PDex's use of the codes. PDex is not the controlling IG for these code systems. The entries below fall into three groups, all sharing the same suppression rationale: 1. HL7 v3 vocabularies (v3-ActCode, v3-ActReason) — foundational code systems mandated by HIPAA / X12 / EDI and reused by FHIR R4 base bindings (Consent.purpose, security labels, treatment categories). Status "draft" in terminology.hl7.org is an HL7 publication-process artifact; the vocabularies are in widespread regulatory production use. 2. FHIR R4 base / Claims-foundation bindings (consent-provision-type, consent-state-codes, consentscope, consentpolicycodes, consentaction, ex-relatedclaimrelationship, ex-diagnosistype, adjudication, fundsreserve, contractsignertypecodes, organization-type). These are inherited from base R4 ElementDefinition bindings on Consent, Claim, EOB, Contract, Organization — PDex cannot remove or alter the binding; the draft status is governed upstream. 3. PDex-author-controlled references (professional-credential-status, provenance-participant-type). PDex chose to reference these because no alternative coding existed at authoring time; promotion to active status is awaited upstream.

Reason for suppression: PDex profiles use `discriminator.type = #pattern`, which the IG Publisher flags as deprecated when it validates the IG against the R5+ slicing semantics. PDex targets FHIR R4, where `pattern` discriminators are the standard idiom. Replacing them with R5-style discriminators is not appropriate for an R4 IG; the deprecation note is advance notice for a future R6 migration, not an R4 issue.

Reason for suppression: PDex's mTLS Endpoint example uses `application/x-x509-ca-cert` as the MIME type identifying the X.509 CA certificate exchanged during mTLS trust establishment. The FHIR validator's signature-format check has built-in knowledge of only two signature formats — `application/jose` (JWS / JWT) and `application/pkcs7-signature` — and emits an information-level note when it encounters any other signature-format value. `application/x-x509-ca-cert` is the IANA-registered media type for X.509 CA certificates and is correct for the mTLS trust anchor exchange described in the mTLS Endpoint profile. The validator's inability to verify the format is a tooling limitation, not a profile defect; cert validation is performed by TLS infrastructure outside FHIR.

Reason for suppression: Reviewed and identified as not being actual embedded HTML tags. The flagged string values are intentional examples (e.g., data that contains characters incidentally resembling tag syntax). No XSS risk exists because the values are not rendered as HTML.

Reason for suppression: The IHE FormatCode code system identified by URL `http://ihe.net/fhir/ValueSet/IHE.FormatCode.codesystem` is the system referenced by the FHIR R4 base ValueSet `formatcodes` (the binding for DocumentReference.content.format). The URL has "ValueSet" in its path as a FHIR R4 base-spec artifact, but it IS the official identifier the FHIR R4 binding expects — see the `compose.include[0].system` element of the R4 `formatcodes` ValueSet. IHE does not publish a resolvable FHIR CodeSystem resource at this URL, so the IG Publisher's terminology validator cannot expand it or confirm code membership, and emits both a "CodeSystem could not be found" warning AND a "code is not in the value set" recommendation- level info on every use. Both are suppressed; the references in PDex examples are correct US Core / FHIR R4 usage.

Reason for suppression: The PDex Device profile is constrained on the base R4 Device resource (not on US Core ImplantableDevice). PDex needs to convey non-implantable device data (e.g., DME items, supplies) that the US Core ImplantableDevice profile cannot represent. The Cross-Group Projects (CGP) Variance Approval process formally granted this variance (Drew Torres / Eric Haas vote 9-0-0) under JIRA FHIR-29796. The variance approval link is https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process

Reason for suppression: The `elementdefinition-maxValueSet` extension is deprecated in favour of `additionalBinding` per the IG Publisher 5.3.0- ballot+ cycle. The deprecated extension is *inherited* from base FHIR R4 element definitions (e.g., `Bundle.type` on MtlsBundle) — it is not added by any PDex FSH source. SUSHI's snapshot generator copies the base element's extensions into the derived profile's snapshot, so the deprecated extension surfaces in PDex even though PDex did not author it. Cannot be removed at the FSH level; awaits either base R4 snapshot regeneration or the IG Publisher stripping deprecated extensions automatically.

Reason for suppression: The mTLS Endpoint profile binds Endpoint.payloadMimeType to the FHIR R4 MIME types value set (http://hl7.org/fhir/ValueSet/mimetypes|4.0.1). That value set is backed by the full IANA media-type registry, which is too large for the public terminology server (tx.fhir.org) to expand within the validator's timeout. The binding is correct and intentional; the expansion failure is a tooling limitation, not a profile defect.

Reason for suppression: When a profile applies a pattern to a repeating element, the IG Publisher emits an informational note that the pattern applies to all repeats. This is the intended semantic for PDex's slicing of Consent.provision.actor and similar elements; the note is purely informational and reflects correct authoring.

Reason for suppression: `expansion-params.json` is a SUSHI configuration resource referenced via `path-expansion-params` in sushi-config.yaml. It sets the SNOMED US edition for terminology expansion at build time. It is not a navigable IG page, so the IG Publisher's "not included in the IG" warning is a false positive against the IG Publisher's page tracker.

StructureDefinition-pdex-member-opt-out.html — 1 message ("html source contains")

StructureDefinition-pdex-priorauthorization.html — 4 messages (all "html source contains")

The Da Vinci template requires an h3 section on index.html. PDex's index.md uses h2 for its main sections, by convention adopted for this IG.

The Da Vinci template wants a JIRA-tracker link on every change-history section heading; the PDex changehistory uses table-cell links per ticket instead (more granular). Reviewed and confirmed appropriate.

US Core 3.1.1 / 6.1.0 / 7.0.0 — StructureDefinition canonicals

US Core 8.x and 9.0.0 were published superseding 7.0.0. Da Vinci IGs (PDex included) currently support US Core 3.1.1, 6.1.0, and 7.0.0 in parallel (see sushi-config.yaml dependencies). Migration to a post-7.0.0 US Core baseline is a coordinated Da Vinci-wide effort planned for a future PDex major release (see changehistory entry for FHIR-56443 — US Core 3.1.1 retirement is the precursor to the new-baseline add). Both the 8.0.1 and 9.0.0 forms of the "most recent appropriate version" message are enumerated below so the suppression survives a publisher refresh that picks up either tx-server snapshot.

US Core — pinned to 7.0.0 (from 3.1.1 / 6.1.0 / 7.0.0)

UUEncode the Jira link to avoid an XML error with issuetype. The current Propose-a-Change link uses the URL-encoded form that the JIRA tracker expects but doesn't match the template's strict-prefix check.

artifacts.html — 1 message ("html source contains")

changehistory.html — 66 messages (29 "no conformance term", 37 "html source contains")

codesystem.x12.org/005010 (X12 005010 transaction-set code lists)

handlingdataprovenance.html — 1 message ("no conformance term")

overview.html — 1 message ("no conformance term")

payertopayerbulkexchange.html — 17 messages (6 "no conformance term", 11 "html source contains")

provider-access-api-v2.html — 11 messages (4 "no conformance term", 7 "html source contains")

provider-access-api.html — 2 messages (both "html source contains")

valueset.x12.org/x217 (X12 health-care-services-review value sets) The IG Publisher emits several distinct message formats for the same missing X12 valueset.x12.org URL depending on whether the validator is checking an instance, a StructureDefinition snapshot, or a differential binding. All formats refer to the same two licensed value sets and are suppressed for the same reason as the codesystem.x12.org entries above.

x12.org/codes (top-level code lists) Two message variants per code system: "code cannot be validated" fires during instance validation; "value set cannot be expanded" fires when the terminology server (tx.fhir.org) attempts to expand a ValueSet that includes the code system.

Errors sorted by type