Validation Results for PhdImplementationGuide

Generated Mon Nov 18 13:58:46 UTC 2024, FHIR version 4.0.1 for hl7.fhir.uv.phd#1.1.0 (canonical = http://hl7.org/fhir/uv/phd (history)). See Full QA Report

Quality Checks
Publisher Version:IG Publisher Version: v1.7.2
Publication Code:phd . PackageId = hl7.fhir.uv.phd, Canonical = http://hl7.org/fhir/uv/phd
Realm Check for UV:
  • n/a
Publication Request:
  • Version 1.1.0 has already been published
  • Publication Request is for v'2.0.0-ballot' but package version is v1.1.0
  • Publication Request is for version v2.0.0-ballot which is already published
Supressed Messages:11 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.uv.phd1.1.0R4http://hl7.org/fhir/uv/phd
... hl7.terminology.r46.0.2 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.0.2Latest Release is 6.1.0
... hl7.fhir.uv.extensions.r45.1.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0
... hl7.fhir.uv.pocd0.3.0 IR4http://hl7.org/fhir/uv/pocdhttp://hl7.org/fhir/uv/pocd/2021Sep
Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: 0.3.0
Dependent IGs:1 guide
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/r4 (details)
HTA Analysis:All OK
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison:
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 1, warn = 1, info = 4, broken links = 0
FilenameErrorsWarningsHints
Build Errors010
/scratch/repo/input/examples/string-observation-1100

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)

input/examples/string-observation-1.json Show Validation Information (1)

PathSeverityMessage
Observation​.code​.coding[0]​.code (l27​/c3)errorUnknown code '8452096' in the CodeSystem 'urn:iso:std:iso:11073:10101' version '2023-04-26'

Editor's Comment: This error is generated on an example of an observation using a private code. This should be fine. (from http://tx.fhir.org/r4)

Suppressed Messages (Warnings, hints, broken links)

Example observation in this IG are suppossed 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

These code systems are PHD specific

This error is generated on an example of an observation using a private code. This should be fine.

This is a recent code for a spirometer device type. Created a pull request on the codes in https://github.com/FHIR/packages/pulls

This warning is generated for a bundle of observations. Looks like a publisher bug.

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

When a vital signs observation has a derivedFrom reference to a timestamp observation this is also checked against vital signs, leading to these warnings.

partition is a known IEEE 11073-10101 concept - discussion on Zulip how to fix this: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Why.20is.20the.20ISO.2FIEEE.2011073.20Codesystem.20seen.20as.20draft.3F/near/456526001

Errors sorted by type


This_element_does_not_match_any_known_slice_

input/examples/compound-numeric-observation.jsonThis element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation|1.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)
input/examples/compound-numeric-observation.jsonThis element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation|1.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)
input/examples/compound-numeric-observation.jsonThis element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation|1.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)
input/examples/compound-numeric-observation.jsonThis element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation|1.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)