Validation Results for USPublicHealthProfilesLibrary

Generated Tue Dec 23 02:25:07 UTC 2025, FHIR version 4.0.1 for hl7.fhir.us.ph-library#2.0.0 (canonical = http://hl7.org/fhir/us/ph-library (history)). See Full QA Report & IP

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

Snomed: The IG specifies the US edition of SNOMED CT

Profiles: All OK

Language Info:Stated Languages: n/a. IG Resource Lang: en. 51 of 145 (35%) of resources have a language. Population Policy: NONE
Publication Request:
package-idhl7.fhir.us.ph-library
version2.0.0
pathhttp://hl7.org/fhir/us/ph-library/2.0.0
Pub-Modemilestone
statustrial-use
Release-LabelSTU 2
Sequence (Group)STU 2 (current: 'STU 1', others = '','STU 2')
descSTU 2 of the Public Health Profiles Library, aligns with USCDI+ Public Health Case Reporting Use Case data elements and updates to US Core 6.1.0
changeschange-log.html
RelatedIgs(None Found)
Dependency on hl7.fhir.uv.fhir-clinical-document is to the current version - not allowed
Supressed Messages:102 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.ph-library2.0.0R4http://hl7.org/fhir/us/ph-library
... hl7.terminology.r47.0.1 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.1
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0
... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
... 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
..... 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
.... 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
... us.nlm.vsac0.23.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
... hl7.fhir.uv.crmi1.0.0 MR4http://hl7.org/fhir/uv/crmihttp://hl7.org/fhir/uv/crmi/STU1
.... hl7.terminology5.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.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.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0Latest Release is 5.2.0
... hl7.fhir.uv.cql2.0.0 MR4http://hl7.org/fhir/uv/cqlhttp://hl7.org/fhir/uv/cql/STU2
.... hl7.terminology.r46.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.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.uv.fhir-clinical-documentcurrent VR4http://hl7.org/fhir/uv/fhir-clinical-documenthttps://build.fhir.org/ig/HL7/fhir-clinical-document/Cannot be published with a dependency on a current build version
.... hl7.terminology.r47.0.1 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.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.fhir.uv.tools.r40.9.0 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/0.9.0Internal Dependency
Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir2.base.template#current
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/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.0.0-snapshot
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 1, warn = 2, info = 0, broken links = 0, pinned = 107 (when multiples).
FilenameErrorsWarningsHints
Build Errors010
/scratch/repo/fsh-generated/resources/ImplementationGuide-hl7.fhir.us.ph-library100
/scratch/repo/fsh-generated/resources/PlanDefinition-us-ph-plandefinition-example010

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/ImplementationGuide-hl7.fhir.us.ph-library.json Show Validation Information (1)

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

Editor's Comment: 19: This will be fixed in a later version of the IG Publisher (see: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0.2E24.20-.20error.20in.20local.20build) Type_Specific_Checks_DT_URL_Resolve

fsh-generated/resources/PlanDefinition-us-ph-plandefinition-example.json Show Validation Information (1)

PathSeverityMessage
fsh-generated​/resources​/PlanDefinition-us-ph-plandefinition-example​.jsonwarningArtifact library could not be found so no data requirements were inferred.

Suppressed Messages (Warnings, hints, broken links)

01: External value sets/code systems - these codes have all been checked and are valid

02: US Core 6.1.0 is the version that is cited in regulation for 2026, the next release of the US Public Health Profiles Library will move to the next cited release of US Core

03: Use of the Extension: Max value set is inherited from the base FHIR v4.0.1 Observation resource on the Observation.language.binding.extension

04: Inherited from US Core Slicing

05: Inherited from US Core

06: These are the correct pinned versions

07: US PH Composition does not define any specific slices - examples show slices that are not defined in the profile - not matching is expected behavior

08: US PH Document Bundle defines a specific entry slice - examples show slices that are not defined in the profile - not matching is expected behavior

09: US PH Reporting Bundle defines specific entry slices - examples show slices that are not defined in the profile - not matching is expected behavior

10: US PH Value Set defines specific useContext slices - examples show slices that are not defined in the profile - not matching is expected behavior

11: US PH MessageHeader defines specific extension slices - examples show extension that are not defined in the profile - not matching is expected behavior

12: US PH Response Bundle defines specific entry slices - examples show slices that are not defined in the profile - not matching is expected behavior

13: US PH Supplemental ValueSet defines specific extension slices - examples show slices that are not defined in the profile - not matching is expected behavior

14: US PH Triggering ValueSet defines specific extension slices - examples show slices that are not defined in the profile - not matching is expected behavior

15: US Public Health Exposure Contact Information defines specific (optional) code slices - examples have slices that are not defined in the profile

16: These extensions are the structuredefinition-wg and the structuredefiniton-standards-status extensions - they are not defined in the crmi-shareablevalueset profile but hae been intentionally added

17: TSMG granted exceptions for these code systems - see minutes: https://confluence.hl7.org/spaces/TSMG/pages/358879370/2025-06-30+TSMG+Agenda+and+Minutes

18: us-ph-patient is based on and further constrains us-core-patient so multiple matches are expected

19: This will be fixed in a later version of the IG Publisher (see: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0.2E24.20-.20error.20in.20local.20build)

20: This is generated IP Statement text

21: These are not conformance clauses, they are statements explaining what SHALL, SHOULD, and MAY mean

Errors sorted by type


Type_Specific_Checks_DT_URL_Resolve

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