Validation Results for USPublicHealthProfilesLibrary

Generated Wed Aug 16 21:42:48 UTC 2023, FHIR version 4.0.1 for hl7.fhir.us.ph-library#1.0.0 (canonical = http://hl7.org/fhir/us/ph-library (history)). See Full QA Report

Quality Checks

Publisher Version:

IG Publisher Version: v1.3.28

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 ✓

9 Profiles not based on US Core

Publication Request:

package-id

hl7.fhir.us.ph-library

version

1.0.0

path

http://hl7.org/fhir/us/ph-library/STU1

Pub-Mode

milestone

status

trial-use

sequence

STU 1

desc

STU 1

Proposed path for this milestone publication should usually be canonical with either sequence or version appended

Supressed Messages:

20 Suppressed Issues

Dependency Checks:

Package	Version	FHIR	Canonical	Web Base	Comment
hl7.fhir.us.ph-library	1.0.0	R4	http://hl7.org/fhir/us/ph-library
hl7.terminology.r4	5.0.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/5.0.0	Latest Release is 5.2.0
hl7.fhir.us.core	5.0.1 O	R4	http://hl7.org/fhir/us/core	http://hl7.org/fhir/us/core/STU5.0.1	Latest Release is 6.1.0
hl7.terminology.r4	3.1.0 O	R4	http://terminology.hl7.org	http://terminology.hl7.org/3.1.0	Latest Release is 5.2.0
hl7.fhir.uv.bulkdata	2.0.0 M	R4	http://hl7.org/fhir/uv/bulkdata	http://hl7.org/fhir/uv/bulkdata/STU2
hl7.fhir.uv.smart-app-launch	2.0.0 O	R4	http://hl7.org/fhir/smart-app-launch	http://hl7.org/fhir/smart-app-launch/STU2	Latest Release is 2.1.0
us.nlm.vsac	0.7.0 O	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac	Latest Release is 0.11.0
hl7.fhir.uv.sdc	3.0.0 M	R4	http://hl7.org/fhir/uv/sdc	http://hl7.org/fhir/uv/sdc/STU3
hl7.fhir.r4.examples	4.0.1 O	R4	http://hl7.org/fhir	http://hl7.org/fhir/R4	Latest Release is 5.0.0
us.cdc.phinvads	0.12.0 M	R4	http://fhir.org/packages/us.cdc.phinvads	http://fhir.org/packages/us.cdc.phinvads
us.nlm.vsac	0.11.0 M	R4	http://fhir.org/packages/us.nlm.vsac	http://fhir.org/packages/us.nlm.vsac
hl7.fhir.uv.extensions	1.0.0 M	R5	http://hl7.org/fhir/extensions	http://hl7.org/fhir/extensions/1.0.0	FHIR Version Mismatch
hl7.terminology.r5	5.0.0 O	R5	http://terminology.hl7.org	http://terminology.hl7.org/5.0.0	FHIR Version Mismatch. Latest Release is 5.2.0

Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: current

Dependent IGs:

Global Profiles:

(none declared)

HTA Analysis:

R5 Dependencies:

(none)

Modifier Extensions:

(none)

Previous Version Comparison:

Comparison with version 1.0.0-ballot

IPA Comparison:

n/a

Summary:

errors = 0, warn = 0, info = 0, broken links = 0

Filename

Errors

Warnings

Hints

Build Errors

0

0

0

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

APPROVED by HL7 Cross Group Projects WG: Profiles do not derive from one of the base US profiles because they do not align with any of the US Core Observations (Minutes: https://confluence.hl7.org/pages/viewpage.action?pageId=97453270)

US FHIR Usage rules require that all profiles on Observation derive from one of the base US profiles (9 uses)

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

Code System URI 'urn:oid:1.0.3166.1' is unknown so the code cannot be validated (1 uses)
Code System URI 'urn:oid:2.16.840.1.114222.4.5.232' is unknown so the code cannot be validated (1 uses)
Code System URI 'urn:oid:2.16.840.1.114222.4.5.274' is unknown so the code cannot be validated (3 uses)
The definition for the Code System with URI 'http://terminology.hl7.org/CodeSystem/umls' doesnt provide any codes so the code cannot be validated (1 uses)
The definition for the Code System with URI 'urn:oid:2.16.840.1.113883.6.238' doesnt provide any codes so the code cannot be validated (12 uses)

US PH Composition doesn't define any specific slices - examples have optional slices that are not defined in the profile - not matching is expected behavior

INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[0].resource.extension[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-composition|1.0.0 (1 uses)
INFORMATION: Composition/us-ph-composition-example: Composition.extension[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-composition|1.0.0 (1 uses)

US PH Computable Library defines one slice for content but examples have optional slices that are not defined in the profile - not matching is expected behavior

INFORMATION: Library/us-ph-executable-library-rule-filters: Library.content[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-computable-library|1.0.0 (1 uses)

US PH Document Bundle only defines one slice (Composition) examples have optional slices that are not defined in the profile - not matching is expected behavior

INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)
INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)
INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[3]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)
INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[4]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)
INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[5]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)
INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[6]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)
INFORMATION: Bundle/us-ph-document-bundle-example: Bundle.entry[7]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-document-bundle|1.0.0 (1 uses)

US PH Executable Library defines two slices for content but examples have optional slices that are not defined in the profile - not matching is expected behavior

INFORMATION: Library/us-ph-executable-library-rule-filters: Library.content[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-executable-library|1.0.0 (1 uses)

US PH MessageHeader defines two extensions slices but examples have optional extension that are not defined in the profile - not matching is expected behavior

INFORMATION: Bundle/us-ph-response-bundle-example: Bundle.entry[0].resource.extension[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-messageheader|1.0.0 (1 uses)
INFORMATION: MessageHeader/us-ph-messageheader-response: MessageHeader.extension[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-messageheader|1.0.0 (1 uses)

US PH Value Set defines two slices for useContext but examples have optional slices that are not defined in the profile - not matching is expected behavior

INFORMATION: Bundle/us-ph-specification-bundle-example: Bundle.entry[1].resource.useContext[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/ph-library/StructureDefinition/us-ph-valueset|1.0.0 (1 uses)

Errors sorted by type