Validation Results for MDI

Generated Thu Dec 12 17:24:19 UTC 2024, FHIR version 4.0.1 for hl7.fhir.us.mdi#2.0.0-ballot2 (canonical = http://hl7.org/fhir/us/mdi (history)). See Full QA Report

Quality Checks
Publisher Version:IG Publisher Version: v1.8.1
Publication Code:mdi . PackageId = hl7.fhir.us.mdi, Canonical = http://hl7.org/fhir/us/mdi
Realm Check for US:

Snomed: The IG specifies the US edition of SNOMED CT

6 Profiles not based on US Core

Publication Request:
package-idhl7.fhir.us.mdi
version2.0.0-ballot2
pathhttp://hl7.org/fhir/us/mdi/2025Jan
Pub-Modeworking release
statusballot
Release-LabelSTU2 ballot
Sequence (Group)STU 2 (current: 'STU 1', others = 'STU 1','STU 2','STU1')
desc2nd Ballot version for STU2
  • Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
  • This release is labelled as a working release in the sequence 'STU 2'. This is an unexpected workflow - check that the sequence really is correct.
Supressed Messages:217 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.mdi2.0.0-ballot2R4http://hl7.org/fhir/us/mdi
... hl7.terminology.r46.1.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0
... hl7.fhir.uv.extensions.r45.1.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0
... hl7.fhir.us.core5.0.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU5.0.1Latest Release is 7.0.0
.... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0Latest Release is 6.1.0
.... hl7.fhir.uv.bulkdata2.0.0 MR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2
.... 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.7.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.21.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
... hl7.fhir.us.vr-common-library2.0.0 MR4http://hl7.org/fhir/us/vr-common-libraryhttp://hl7.org/fhir/us/vr-common-library/STU2
.... 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.0see above
.... hl7.fhir.us.core5.0.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU5.0.1see above. Latest Release is 7.0.0
.... us.nlm.vsac0.19.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.21.0
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvadssee above
... hl7.fhir.us.vrdr3.0.0 MR4http://hl7.org/fhir/us/vrdrhttp://hl7.org/fhir/us/vrdr/STU3
.... hl7.terminology.r46.0.2 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.0.2see above. Latest Release is 6.1.0
.... hl7.fhir.uv.extensions.r45.1.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0see above
.... hl7.fhir.us.core5.0.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU5.0.1see above. Latest Release is 7.0.0
.... hl7.fhir.us.vr-common-library2.0.0 MR4http://hl7.org/fhir/us/vr-common-libraryhttp://hl7.org/fhir/us/vr-common-library/STU2see above
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvadssee above
.... hl7.fhir.us.odh1.3.0 MR4http://hl7.org/fhir/us/odhhttp://hl7.org/fhir/us/odh/STU1.3
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 6.1.0
..... hl7.fhir.us.core5.0.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU5.0.1see above. Latest Release is 7.0.0
..... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvadssee above
... hl7.fhir.us.odh1.3.0 MR4http://hl7.org/fhir/us/odhhttp://hl7.org/fhir/us/odh/STU1.3see above
Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: 0.3.0
Dependent IGs:no references
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: Comparison with version 1.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 = 0, info = 0, broken links = 0
FilenameErrorsWarningsHints
Build Errors000

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

01 - APPROVALS by HL7 Cross Group Projects WG: 2022-02-10, see https://confluence.hl7.org/pages/viewpage.action?pageId=90341999; 2022-03-10, see https://confluence.hl7.org/pages/viewpage.action?pageId=90358833; 2024-11-14, see https://confluence.hl7.org/display/CGP/2024-11-14+Cross-Group+Project+Workgroup+Call. All non-US Core profiles must be reviewed when this IG becomes dependent on US Core 6 or later.

02 - Variance Requested from TSMG 03/20/24 and approved 2024-11-14, see: https://confluence.hl7.org/display/TSMG/2024-11-14+TSMG+Agenda+and+Minutes

03 - For VRDR Observation profile examples included in this MDI IG: Vital Records Death Reporting (VRDR) FHIR IG states the following related to VRDR Observations: For vital records reporting the performer and effective time are either/or/both not known, or not important. These are not really clinical observations, but abstracted facts represented using Observation resources.

04 - For VRDR Observation profile examples included in the example bundle-doc-mdi-dcr-ex1: Vital Records Death Reporting (VRDR) FHIR IG states the following related to VRDR Observations: For vital records reporting the performer and effective time are either/or/both not known, or not important. These are not really clinical observations, but abstracted facts represented using Observation resources.

05 - For VRDR Observation profile examples included in the example bundle-msg-mdi-dcr-ex1: Vital Records Death Reporting (VRDR) FHIR IG states the following related to VRDR Observations: For vital records reporting the performer and effective time are either/or/both not known, or not important. These are not really clinical observations, but abstracted facts represented using Observation resources.

06 - Slicing information for bundle example: bundle-doc-mdi-dcr-ex1. Bundle examples have optional slices (after the required entry[0]) that are not defined in the profile; not matching is expected behavior. All slices have been reviewed and verified.

07 - Slicing information for bundle example: bundle-mdi-and-edrs-a-freeman. Bundle examples have optional slices (after the required entry[0]) that are not defined in the profile; not matching is expected behavior. All slices have been reviewed and verified.

08 - Slicing information for bundle example: bundle-mdi-tox-report-message-a-freeman. Bundle examples have optional slices (after the required entry[0]) that are not defined in the profile; not matching is expected behavior. All slices have been reviewed and verified.

09 - Slicing information for bundle example: bundle-msg-mdi-dcr-ex1. Bundle examples have optional slices (after the required entry[0]) that are not defined in the profile; not matching is expected behavior. All slices have been reviewed and verified.

10 - Other slicing issues in examples, some related to US Core 5.0.1, which defines slices for several profiles that this IG references, based on the value of pattern:$this. The discriminator type 'pattern' has been deprecated, which affects profiles in this IG. See: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/deprecated.20pattern.20slicing

11 - dom-6: 'A resource should have narrative for robust management'. Narrative is not expected in content coming from EDRS.

Errors sorted by type