Validation Results for PhdImplementationGuide

Generated Wed Nov 11 00:57:23 AEDT 2026, FHIR version 4.0.1 for hl7.fhir.uv.phd#2.0.1 (canonical = http://hl7.org/fhir/uv/phd (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v3.0.3
Publication Code:phd . PackageId = hl7.fhir.uv.phd, Canonical = http://hl7.org/fhir/uv/phd
Realm Check for UV:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: en. 2 of 71 (2%) of resources have a language. Population Policy: NONE
Publication Request:
package-idhl7.fhir.uv.phd
version2.0.1
pathhttp://hl7.org/fhir/uv/phd/2.0.1
Pub-Modemilestone
statustrial-use
Release-LabelSTU 2
Sequence (Group)STU 2 (current: 'STU 2', others = 'STU 1')
descSTU 2 erratum correction.
changesinput/pagecontent/changes.md
RelatedIgs(None Found)
No Messages found - all good
Supressed Messages:21 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
hl7.fhir.uv.phd2.0.1R4http://hl7.org/fhir/uv/phd
hl7.fhir.uv.phd / hl7.terminology.r47.5.0 Latest Milestone Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/7.5.0
hl7.fhir.uv.phd / hl7.fhir.uv.extensions.r45.4.0 Latest Milestone Release. R4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.4.0
hl7.fhir.uv.phd / hl7.fhir.uv.extensions.r4 / hl7.terminology.r47.5.0 Latest Milestone Release. R4http://terminology.hl7.orghttp://terminology.hl7.org/7.5.0 (as above)
hl7.fhir.uv.phd / hl7.fhir.uv.pocd0.3.0 Outdated Release. R4http://hl7.org/fhir/uv/pocdhttp://hl7.org/fhir/uv/pocd/2021SepLatest Release is null
hl7.fhir.uv.phd / hl7.fhir.uv.tools.r41.3.0 Latest Milestone Release. R4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.3.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):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
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 0, warn = 0, info = 2, broken links = 0, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors000

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

Example observation in this IG are supposed to be device generated with often an unknown performer. There is text in the IG to explain this. The affected example observations / bundles are: bits-observation.json, bundle-continuousnonin.json, bundle-example-1.json, coin-20181119174911.json, coin-20181119202022.json, coin-example-1.json, coin-example-timefault.json, glucose-1.0.0.4.json, numeric-observation-not-a-number.json, numeric-spotnumeric.json, stringenum-1234.json

Publisher process choice - can safely be ignored

Reference to external draft code system...

The eventOrState and source property values in CodeSystem/ASN1ToHL7 are concepts in that code system, so validating them as internal codes is appropriate.

These six code systems are PHD specific. A TSMG exemption is not yet required due to the IG maturity level being less than 3, but will be requested together with a next update of this IG.

This informational message is due to inheriting this extension from the core specification.

This is generated for all observations that use the vital signs category. The vitals sign category element does not match the slice for the `phd` category. This warning can be ignored safely.

This warning is generated on purpose in two examples that use a private code on purpose. This warning can hence safely be ignored.

This warning is generated when different categories are required in resources that comply with different profiles like vitals-signs and phd:

When a Phd compound observation is also a vital sign this warning is generated. The LOINC coding does not match the slice for the MDC coding. This is not a real problem.

When a vital signs observation is also checked against the vital signs profile these warnings are generated. The vitals sign category element does not match the slice for the `phd` category. These are no real problems.

Errors sorted by type


VALUESET_UNKNOWN_FILTER_PROPERTY_NO_CS

fsh-generated/resources/ValueSet-MDCnotObject.jsonNo definition can be found for the system urn:iso:std:iso:11073:10101, and the property 'partition' is not a generally known property, so the property might not be valid, or understood by the terminology ecosystem. In case it's useful, the list of generally known properties for all systems is concept,code,status,inactive,effectiveDate,deprecationDate,retirementDate,notSelectable,synonym,comment,itemWeight--
fsh-generated/resources/ValueSet-MDCobject.jsonNo definition can be found for the system urn:iso:std:iso:11073:10101, and the property 'partition' is not a generally known property, so the property might not be valid, or understood by the terminology ecosystem. In case it's useful, the list of generally known properties for all systems is concept,code,status,inactive,effectiveDate,deprecationDate,retirementDate,notSelectable,synonym,comment,itemWeight--