Validation Results for EHMIEDSIG

Generated Tue Sep 23 10:40:35 UTC 2025, FHIR version 4.0.1 for dk.ehmi.eds#1.0.1-draft (canonical = http://medcomehmi.dk/ig/eds (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.0.17
Publication Code:n/a . PackageId = dk.ehmi.eds, Canonical = http://medcomehmi.dk/ig/eds
Realm Check for n/a:
  • n/a
Language Info:This IG has no language information
Publication Request:
RelatedIgs(None Found)
  • Version 1.0.1-draft has already been published
  • This is not the first publication, so first must not be true
  • Publication Request is for version v1.0.1-draft which is already published
Supressed Messages:2 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. dk.ehmi.eds1.0.1-draftR4http://medcomehmi.dk/ig/eds
... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0
.... 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.dk.core3.4.0 MR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/3.4.0
.... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 6.5.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.phd1.1.0 MR4http://hl7.org/fhir/uv/phdhttp://hl7.org/fhir/uv/phd/STU1.1
..... hl7.terminology.r46.0.2 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.0.2Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
..... hl7.fhir.uv.pocd0.3.0 IR4http://hl7.org/fhir/uv/pocdhttp://hl7.org/fhir/uv/pocd/2021Sep
.... hl7.fhir.uv.ipa1.0.0 OR4http://hl7.org/fhir/uv/ipahttp://hl7.org/fhir/uv/ipa/STU1Latest Release is 1.1.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 6.5.0
..... 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
.... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 6.5.0
.... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
.... hl7.fhir.dk.core3.2.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/3.2.0Latest Release is 3.4.0
..... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0 (as above). Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
..... hl7.fhir.uv.phd1.0.0 OR4http://hl7.org/fhir/uv/phdhttp://hl7.org/fhir/uv/phd/STU1Latest Release is 1.1.0
...... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0Latest Release is 6.5.0
.... medcom.fhir.dk.terminology1.7.0 VR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.7.0
..... hl7.terminology.r45.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0 (as above). Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
... medcom.fhir.dk.messaging3.0.0 MR4http://medcomfhir.dk/ig/messaginghttp://medcomfhir.dk/ig/messaging/3.0.0
.... hl7.terminology.r46.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.3.0Latest Release is 6.5.0
..... 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.dk.core3.2.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/3.2.0 (as above). Latest Release is 3.4.0
.... medcom.fhir.dk.core2.4.0 IR4http://medcomfhir.dk/ig/corehttp://medcomfhir.dk/ig/core/2.4.0 (as above)
... medcom.fhir.dk.terminology1.8.1 MR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.8.1
.... hl7.terminology.r46.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.3.0 (as above). Latest Release is 6.5.0
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
... dk.ehmi.terminology1.0.0-draft OR4http://medcomehmi.dk/ig/terminologyhttp://medcomehmi.dk/ig/terminology/1.0.0-draftLatest Release is 1.0.1-draft
.... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0 (as above)
.... ihe.iti.balp1.1.3 MR4https://profiles.ihe.net/ITI/BALPhttps://profiles.ihe.net/ITI/BALP/1.1.3
..... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.2.0
.... ihe.iti.mcsd4.0.0 MR4https://profiles.ihe.net/ITI/mCSDhttps://profiles.ihe.net/ITI/mCSD/4.0.0
..... hl7.terminology.r46.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.3.0 (as above). Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
..... ihe.iti.balp1.1.3 MR4https://profiles.ihe.net/ITI/BALPhttps://profiles.ihe.net/ITI/BALP/1.1.3 (as above)
.... hl7.fhir.dk.core3.4.0 MR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/3.4.0 (as above)
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
... dk.ehmi.eer1.0.0-draft MR4http://medcomehmi.dk/ig/eerhttp://medcomehmi.dk/ig/eer/1.0.0-draft
.... hl7.terminology.r46.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0 (as above)
.... ihe.iti.mcsd3.9.0 OR4https://profiles.ihe.net/ITI/mCSDhttps://profiles.ihe.net/ITI/mCSD/3.9.0Latest Release is 4.0.0
..... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
..... ihe.iti.balp1.1.3 MR4https://profiles.ihe.net/ITI/BALPhttps://profiles.ihe.net/ITI/BALP/1.1.3 (as above)
.... hl7.fhir.dk.core3.3.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/3.3.0Latest Release is 3.4.0
..... hl7.terminology.r46.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.1.0 (as above). Latest Release is 6.5.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0 (as above). Latest Release is 5.2.0
..... hl7.fhir.uv.phd1.0.0 OR4http://hl7.org/fhir/uv/phdhttp://hl7.org/fhir/uv/phd/STU1 (as above). Latest Release is 1.1.0
.... medcom.fhir.dk.core2.4.0 IR4http://medcomfhir.dk/ig/corehttp://medcomfhir.dk/ig/core/2.4.0 (as above)
.... medcom.fhir.dk.messaging3.0.0 MR4http://medcomfhir.dk/ig/messaginghttp://medcomfhir.dk/ig/messaging/3.0.0 (as above)
.... medcom.fhir.dk.terminology1.8.1 MR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.8.1 (as above)
.... dk.ehmi.terminology1.0.0-draft OR4http://medcomehmi.dk/ig/terminologyhttp://medcomehmi.dk/ig/terminology/1.0.0-draft (as above). Latest Release is 1.0.1-draft
.... 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.8.0 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/0.8.0Internal Dependency
Templates: medcom.dk.ehmi.template#0.0.1 -> fhir.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:Non-HL7 Igs are exempt from terminology dependency analysis
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 = 0, warn = 2, info = 39, broken links = 0, pinned = 4 (when multiples).
FilenameErrorsWarningsHints
Build Errors000
/scratch/repo/fsh-generated/resources/ImplementationGuide-dk.ehmi.eds020

n/a Show Validation Information

fsh-generated/resources/ImplementationGuide-dk.ehmi.eds.json Show Validation Information (1)

PathSeverityMessage
ImplementationGuide​.definition​.resource[35]​.description (l1​/c43716)warningvalue should not start or finish with whitespace '\nEdsBasicDeliveryStatus is used to define the basic delivery status reporting for EDS from an EDS Client to the EDS Server.\n\nA basic EdsBasicDeliveryStatus is based on the AuditEvent profile for and is submitted when a EHMI Core Messaging transaction \nfrom one station in the messageflow to another station happens successfully.\n\nEdsBasicDeliveryStatus is only used when a Patient entity is not required, for instance for delivery status reporting of Acknowledgements. \nThe EdsBasicDeliveryStatus does not have a Patient subject or is otherwise associated with a Patient. \nWhen the message transaction is Patient specific then EdsPatientDeliveryStatus is used.\n\nWhen successfully submitted from an EDS Client to the EDS Server then the recorded EdsBasicDeliveryStatus has conformed to the profile otherwise it would \nnot have a successful outcome and the EDS Client will receive an OperationOutcome indicating the failure.' Type_Specific_Checks_DT_String_WS
ImplementationGuide​.definition​.resource[36]​.description (l1​/c44938)warningvalue should not start or finish with whitespace '\nEdsPatientDeliveryStatus is used to define the basic delivery status reporting for EDS from an EDS Client to the EDS Server.\n\nThe EdsPatientDeliveryStatus is an enhancement of the basic EdsBasicDeliveryStatus and is submitted when a EHMI Core Messaging transaction \nfrom one station in the messageflow to another station happens successfully.\n\nEdsPatientDeliveryStatus is used when a Patient entity is required, for instance for status reporting of MedCom FHIR Messages.\nThe EdsPatientDeliveryStatus has a Patient subject entity and is thereby associated with a Patient. \nWhen the message transaction is not Patient specific then EdsBasicDeliveryStatus is used.\n\nWhen successfully submitted from an EDS Client to the EDS Server then the recorded EdsPatientDeliveryStatus has conformed to the profile otherwise it would \nnot have a successful outcome and the EDS Client will receive an OperationOutcome indicating the failure.' Type_Specific_Checks_DT_String_WS

Suppressed Messages (Warnings, hints, broken links)

See https://github.com/FHIR/sample-ig/blob/master/input/ignoreWarnings.txt for examples

Errors sorted by type

MSG_DEPENDS_ON_DEPRECATED

fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus.jsonThe extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated

MSG_DRAFT

fsh-generated/resources/AuditEvent-EDS-BDS-07.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-08.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-08.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-09.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-09.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-10.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-11.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-11.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-12.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-12.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-13.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-13.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-14.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-14.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-15.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-15.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-16.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-17.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-18.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-18.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-19.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-19.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-BDS-20.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-01.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-01.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-02.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-02.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-03.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-03.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-04.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-04.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-05.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-05.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-06.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

PIN_VERSION

fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus.jsonPinned the version of http://terminology.hl7.org/ValueSet/v3-PurposeOfUse to 3.1.0 from choices of 2.0.0 (hl7.terminology.r4#5.3.0), 3.0.0 (hl7.terminology.r4#5.5.0), 3.1.0 (hl7.terminology.r4#6.1.0)
fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus.jsonPinned the version of http://terminology.hl7.org/ValueSet/v3-PurposeOfUse to 3.1.0 from choices of 2.0.0 (hl7.terminology.r4#5.3.0), 3.0.0 (hl7.terminology.r4#5.5.0), 3.1.0 (hl7.terminology.r4#6.1.0)
fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus.jsonPinned the version of http://terminology.hl7.org/ValueSet/v3-PurposeOfUse to 3.1.0 from choices of 2.0.0 (hl7.terminology.r4#5.3.0), 3.0.0 (hl7.terminology.r4#5.5.0), 3.1.0 (hl7.terminology.r4#6.1.0)
fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus.jsonPinned the version of http://terminology.hl7.org/ValueSet/v3-PurposeOfUse to 3.1.0 from choices of 2.0.0 (hl7.terminology.r4#5.3.0), 3.0.0 (hl7.terminology.r4#5.5.0), 3.1.0 (hl7.terminology.r4#6.1.0)

Type_Specific_Checks_DT_String_WS

fsh-generated/resources/ImplementationGuide-dk.ehmi.eds.jsonvalue should not start or finish with whitespace '\nEdsBasicDeliveryStatus is used to define the basic delivery status reporting for EDS from an EDS Client to the EDS Server.\n\nA basic EdsBasicDeliveryStatus is based on the AuditEvent profile for and is submitted when a EHMI Core Messaging transaction \nfrom one station in the messageflow to another station happens successfully.\n\nEdsBasicDeliveryStatus is only used when a Patient entity is not required, for instance for delivery status reporting of Acknowledgements. \nThe EdsBasicDeliveryStatus does not have a Patient subject or is otherwise associated with a Patient. \nWhen the message transaction is Patient specific then EdsPatientDeliveryStatus is used.\n\nWhen successfully submitted from an EDS Client to the EDS Server then the recorded EdsBasicDeliveryStatus has conformed to the profile otherwise it would \nnot have a successful outcome and the EDS Client will receive an OperationOutcome indicating the failure.'
fsh-generated/resources/ImplementationGuide-dk.ehmi.eds.jsonvalue should not start or finish with whitespace '\nEdsPatientDeliveryStatus is used to define the basic delivery status reporting for EDS from an EDS Client to the EDS Server.\n\nThe EdsPatientDeliveryStatus is an enhancement of the basic EdsBasicDeliveryStatus and is submitted when a EHMI Core Messaging transaction \nfrom one station in the messageflow to another station happens successfully.\n\nEdsPatientDeliveryStatus is used when a Patient entity is required, for instance for status reporting of MedCom FHIR Messages.\nThe EdsPatientDeliveryStatus has a Patient subject entity and is thereby associated with a Patient. \nWhen the message transaction is not Patient specific then EdsBasicDeliveryStatus is used.\n\nWhen successfully submitted from an EDS Client to the EDS Server then the recorded EdsPatientDeliveryStatus has conformed to the profile otherwise it would \nnot have a successful outcome and the EDS Client will receive an OperationOutcome indicating the failure.'