Validation Results for EHMIEDSIG

Generated Thu Apr 25 12:13:03 UTC 2024, FHIR version 4.0.1 for dk.ehmi.eds#0.9.0 (canonical = http://medcomehmi.dk/ig/dk-ehmi-eds (history)). See Errors Only

Quality Checks
Publisher Version:IG Publisher Version: v1.6.6
Publication Code:n/a . PackageId = dk.ehmi.eds, Canonical = http://medcomehmi.dk/ig/dk-ehmi-eds
Realm Check for n/a:
  • n/a
Publication Request:
  • Error fetching package-list from http://medcomehmi.dk/ig/dk-ehmi-eds: medcomehmi.dk
  • This IG has never been published, so the version should start with '0.' or include a patch version e.g. '-ballot'
  • No publication request found
Supressed Messages:No Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. dk.ehmi.eds0.9.0R4http://medcomehmi.dk/ig/dk-ehmi-eds
... hl7.terminology.r45.5.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0
... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0
... 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 5.5.0
.... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
... hl7.fhir.dk.core2.0.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.0.0Latest Release is 3.1.0
.... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0Latest Release is 5.5.0
... medcom.fhir.dk.core2.3.0 MR4http://medcomfhir.dk/ig/corehttp://medcomfhir.dk/ig/core/2.3.0
.... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
.... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... hl7.fhir.dk.core2.2.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.2.0Latest Release is 3.1.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 5.5.0
..... hl7.fhir.uv.phd1.0.0 UR4http://hl7.org/fhir/uv/phdhttp://hl7.org/fhir/uv/phd/STU1
...... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0see above. Latest Release is 5.5.0
.... medcom.fhir.dk.terminology1.5.0 OR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.5.0Latest Release is 1.6.0
..... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
..... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
... medcom.fhir.dk.messaging2.1.0 VR4http://medcomfhir.dk/ig/messaginghttp://medcomfhir.dk/ig/messaging/2.1.0
.... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
.... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... hl7.fhir.dk.core2.0.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.0.0see above. Latest Release is 3.1.0
.... medcom.fhir.dk.core2.3.0 MR4http://medcomfhir.dk/ig/corehttp://medcomfhir.dk/ig/core/2.3.0see above
... medcom.fhir.dk.terminology1.5.0 OR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.5.0see above. Latest Release is 1.6.0
... dk.ehmi.terminology0.8.0 UR4http://medcomehmi.dk/ig/dk-ehmi-terminologyhttps://build.fhir.org/ig/medcomdk/dk-ehmi-terminology/Matched to latest patch release (current->0.8.0)
.... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
.... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... ihe.iti.balp1.1.2 OR4https://profiles.ihe.net/ITI/BALPhttps://profiles.ihe.net/ITI/BALP/1.1.2Latest Release is 1.1.3
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0see above. Latest Release is 5.5.0
..... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... ihe.iti.mcsd3.8.0 MR4https://profiles.ihe.net/ITI/mCSDhttps://profiles.ihe.net/ITI/mCSD/3.8.0
..... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0see above. Latest Release is 5.5.0
..... ihe.iti.balp1.1.0 OR4https://profiles.ihe.net/ITI/BALPhttps://profiles.ihe.net/ITI/BALP/1.1.0Latest Release is 1.1.3
... dk.ehmi.eer0.3.0 UR4http://medcomehmi.dk/ig/dk-ehmi-eerhttps://build.fhir.org/ig/medcomdk/dk-ehmi-eer/Matched to latest patch release (current->0.3.0)
.... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
.... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... ihe.iti.mcsd3.8.0 MR4https://profiles.ihe.net/ITI/mCSDhttps://profiles.ihe.net/ITI/mCSD/3.8.0see above
.... hl7.fhir.dk.core2.0.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.0.0see above. Latest Release is 3.1.0
.... dk.ehmi.terminology0.8.0 UR4http://medcomehmi.dk/ig/dk-ehmi-terminologyhttps://build.fhir.org/ig/medcomdk/dk-ehmi-terminology/see above
.... medcom.fhir.dk.core2.3.0 MR4http://medcomfhir.dk/ig/corehttp://medcomfhir.dk/ig/core/2.3.0see above
.... medcom.fhir.dk.messaging2.0.0 MR4http://medcomfhir.dk/ig/messagingfile://C:\Users\TMS\TMS\GitHub\MedComPublication\dk-medcom-messaging-v.2.0.0-IG\output
..... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
..... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
..... hl7.fhir.dk.core2.0.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.0.0see above. Latest Release is 3.1.0
..... medcom.fhir.dk.core2.0.0 OR4http://medcomfhir.dk/ig/corefile://C:\Users\TMS\TMS\GitHub\MedComPublication\dk-medcom-core-v.2.0.0-IG\outputLatest Release is 2.3.0
...... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
...... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
...... hl7.fhir.dk.core2.0.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.0.0see above. Latest Release is 3.1.0
...... medcom.fhir.dk.terminology1.4.0 OR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.4.0Latest Release is 1.6.0
....... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0see above. Latest Release is 5.5.0
....... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... medcom.fhir.dk.terminology1.6.0 MR4http://medcomfhir.dk/ig/terminologyfile://C:\Users\TMS\TMS\GitHub\MedComPublication\dk-medcom-terminology\output
..... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
..... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
... medcom.fhir.dk.ihe.xds.metadata1.0.0 UR4https://medcomfhir.dk/ig/ihexdsmetadatahttps://build.fhir.org/ig/medcomdk/dk-medcom-ihe-xds-metadata/Matched to latest patch release (current->1.0.0)
.... hl7.terminology.r45.3.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0see above. Latest Release is 5.5.0
.... hl7.fhir.uv.extensions.r41.0.0 UR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0see above
.... medcom.fhir.dk.core2.1.0 OR4http://medcomfhir.dk/ig/corehttp://medcomfhir.dk/ig/core/2.1.0Latest Release is 2.3.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0see above. Latest Release is 5.5.0
..... hl7.fhir.dk.core2.0.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.0.0see above. Latest Release is 3.1.0
..... medcom.fhir.dk.terminology1.1.0 OR4http://medcomfhir.dk/ig/terminologyhttp://medcomfhir.dk/ig/terminology/1.1.0Latest Release is 1.6.0
...... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0see above. Latest Release is 5.5.0
.... hl7.fhir.dk.core2.2.0 OR4http://hl7.dk/fhir/corehttp://hl7.dk/fhir/core/2.2.0see above. Latest Release is 3.1.0
Templates: medcom.dk.ehmi.template#0.0.1 -> fhir.base.template#current. Tools: 0.1.0
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):http://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: Unable to compare with previous version: Unable to find version history at http://medcomehmi.dk/ig/dk-ehmi-eds (Problem #1 with package-list.json at http://medcomehmi.dk/ig/dk-ehmi-eds: medcomehmi.dk)
IPA Comparison: n/a
IPS Comparison: n/a
Summary: errors = 3, warn = 34, info = 24, broken links = 2
FilenameErrorsWarningsHints
Build Errors300
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-01.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-01.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-02.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-02.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-03.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-03.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-04.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-04.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-05.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-05.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-06.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-06.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-07.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-07.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-08.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-08.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-09.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-09.2011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-10.1011
/scratch/repo/fsh-generated/resources/AuditEvent-EDS-PDS-10.2011
/scratch/repo/fsh-generated/resources/AuditEvent-eds-basic-delivery-instance100
/scratch/repo/fsh-generated/resources/AuditEvent-msg-created-instance100
/scratch/repo/fsh-generated/resources/Device-s-01-EUA-Sender000
/scratch/repo/fsh-generated/resources/Device-s-02-MSH-Sender000
/scratch/repo/fsh-generated/resources/Device-s-03-AP-Sender000
/scratch/repo/fsh-generated/resources/Device-s-04-AP-Receiver000
/scratch/repo/fsh-generated/resources/Device-s-05-MSH-Receiver000
/scratch/repo/fsh-generated/resources/Device-s-06-EUA-Receiver000
/scratch/repo/fsh-generated/resources/ImplementationGuide-dk.ehmi.eds020
/scratch/repo/fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus061
/scratch/repo/fsh-generated/resources/StructureDefinition-EdsPatientDeliveryStatus063
/scratch/repo/fsh-generated/resources/StructureDefinition-eds-otherId000

n/a Show Validation Information

package.tgzerrorError converting pacakge to R4B: Error processing example/AuditEvent-eds-basic-delivery-instance.json: Unknown AuditEventOutcome code 'success'
output​/xhtml-fragments​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/div​/p​/a at Line 175, column 136errorThe link 'package.r4.tgz' for "R4 (dk.ehmi.eds.r4)" cannot be resolved
output​/xhtml-fragments​.html​#​/html​/body​/div​/div​/div​/div​/div​/div​/div​/p​/a at Line 175, column 189errorThe link 'package.r4b.tgz' for "R4B (dk.ehmi.eds.r4b)" cannot be resolved

fsh-generated/resources/AuditEvent-EDS-PDS-01.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l191/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-01.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l193/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-02.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l213/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-02.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l215/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-03.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l213/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-03.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l213/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-04.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l195/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-04.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l195/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-05.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l195/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-05.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l195/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-06.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l191/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-06.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l191/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-07.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l227/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-07.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l227/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-08.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l226/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-08.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l226/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-09.1.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l225/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-09.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l225/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-10.1.json Show Validation Information (1)

PathSeverityMessage
AuditEvent.type (l9/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l218/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-EDS-PDS-10.2.json Show Validation Information (2)

PathSeverityMessage
AuditEvent.type (l36/c4)warningA code with no system has no defined meaning, and it cannot be validated. A system should be provided
AuditEvent.outcome (l245/c17)informationReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1

fsh-generated/resources/AuditEvent-eds-basic-delivery-instance.json Show Validation Information (1)

PathSeverityMessage
AuditEvent.outcome (l180/c23)errorThe value provided ('success') was not found in the value set 'EHMI Delivery Status (EDS) Outcome Valueset' (http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0), and a code is required from this value set (error message = The System URI could not be determined for the code 'success' in the ValueSet 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0'; The provided code '#success' was not found in the value set 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0')

fsh-generated/resources/AuditEvent-msg-created-instance.json Show Validation Information (1)

PathSeverityMessage
AuditEvent.outcome (l180/c23)errorThe value provided ('success') was not found in the value set 'EHMI Delivery Status (EDS) Outcome Valueset' (http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0), and a code is required from this value set (error message = The System URI could not be determined for the code 'success' in the ValueSet 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0'; The provided code '#success' was not found in the value set 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0')

fsh-generated/resources/Device-s-01-EUA-Sender.json Show Validation Information (1)


fsh-generated/resources/Device-s-02-MSH-Sender.json Show Validation Information (1)


fsh-generated/resources/Device-s-03-AP-Sender.json Show Validation Information (1)


fsh-generated/resources/Device-s-04-AP-Receiver.json Show Validation Information (1)


fsh-generated/resources/Device-s-05-MSH-Receiver.json Show Validation Information (1)


fsh-generated/resources/Device-s-06-EUA-Receiver.json Show Validation Information (1)


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

PathSeverityMessage
ImplementationGuide​.definition​.resource[21]​.description (l1​/c31077)warningvalue should not start or finish with whitespace '\nEdsBasicDeliveryStatus is used to define the basic status reporting for EDS from the EDS Client to the EDS Server.\nEdsBasicDeliveryStatus is used when a Patient entity is not required, for instance for status reporting of Acknowledgments.\nA basic EdsBasicDeliveryStatus based on the AuditEvent profile for when a EHMI Basic Delivery Status Messaging action happens successfully.\nIt is used when \n- the resource does not have a Patient subject or is otherwise associated with a Patient\n - when the resource is Patient specific then EdsPatientDeliveryStatus is used\n- And the request is authorized\n- When successful\n - Note a failure EdsBasicDeliveryStatus may follow this pattern, but would not be a successful outcome and should have an OperationOutcome\n - Then the EdsBasicDeliveryStatus recorded will conform'
ImplementationGuide​.definition​.resource[23]​.description (l1​/c32601)warningvalue should not start or finish with whitespace '\nEHMI profile based on the EHMI profile EdsBasicDeliveryStatus.\nEdsPatientDeliveryStatus is used to define the status reporting for EDS from a EDS Client to the EDS Server.\nEdsPatientDeliveryStatus is used when a Patient entity is required, for instance for status reporting of MedCom FHIR Messages.\nA EdsPatientDeliveryStatus based on the AuditEvent profile for when a EHMI Patient Delivery Status Messaging action happens successfully.\nIt is used when \n- the resource has a Patient subject or is otherwise associated with a Patient\n - when the resource is not Patient related then EdsBasicDeliveryStatus is used\n- And the request is authorized\n- When successful\n - Note a failure EdsPatientDeliveryStatus may follow this pattern, but would not be a successful outcome and should have an OperationOutcome\n - Then the EdsPatientDeliveryStatus recorded will conform'

fsh-generated/resources/StructureDefinition-EdsBasicDeliveryStatus.json Show Validation Information (1)

PathSeverityMessage
StructureDefinition​.snapshot​.element[17]informationThe slice definition for AuditEvent.subtype has a maximum of 1 but the slices add up to a maximum of 6. Check that this is what is intended
StructureDefinition​.snapshot​.element[18]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[26]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[34]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[42]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[50]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[58]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance

fsh-generated/resources/StructureDefinition-EdsPatientDeliveryStatus.json Show Validation Information (1)

PathSeverityMessage
StructureDefinition​.snapshot​.element[17]informationThe slice definition for AuditEvent.subtype has a maximum of 1 but the slices add up to a maximum of 6. Check that this is what is intended
StructureDefinition​.snapshot​.element[470]​.pattern​.ofType(Coding) (l1​/c644914)informationReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/object-role|1.0.0
StructureDefinition​.differential​.element[8]​.pattern​.ofType(Coding) (l1​/c661553)informationReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/object-role|1.0.0
StructureDefinition​.snapshot​.element[18]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[26]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[34]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[42]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[50]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance
StructureDefinition​.snapshot​.element[58]​.fixed​.ofType(Coding)warningFor the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance

fsh-generated/resources/StructureDefinition-eds-otherId.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

No suppressed messsages

Errors sorted by type


MSG_DRAFT

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
fsh-generated/resources/AuditEvent-EDS-PDS-06.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-07.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-07.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-08.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-08.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-09.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-09.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-10.1.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/AuditEvent-EDS-PDS-10.2.jsonReference to draft CodeSystem http://hl7.org/fhir/audit-event-outcome|4.0.1
fsh-generated/resources/StructureDefinition-EdsPatientDeliveryStatus.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/object-role|1.0.0
fsh-generated/resources/StructureDefinition-EdsPatientDeliveryStatus.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/object-role|1.0.0

TERMINOLOGY_TX_SYSTEM_NO_CODE

fsh-generated/resources/AuditEvent-EDS-PDS-01.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-01.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-02.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-02.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-03.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-03.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-04.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-04.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-05.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-05.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-06.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-06.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-07.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-07.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-08.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-08.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-09.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-09.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-10.1.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided
fsh-generated/resources/AuditEvent-EDS-PDS-10.2.jsonA code with no system has no defined meaning, and it cannot be validated. A system should be provided

Terminology_TX_NoValid_16

fsh-generated/resources/AuditEvent-eds-basic-delivery-instance.jsonThe value provided ('success') was not found in the value set 'EHMI Delivery Status (EDS) Outcome Valueset' (http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0), and a code is required from this value set (error message = The System URI could not be determined for the code 'success' in the ValueSet 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0'; The provided code '#success' was not found in the value set 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0')
fsh-generated/resources/AuditEvent-msg-created-instance.jsonThe value provided ('success') was not found in the value set 'EHMI Delivery Status (EDS) Outcome Valueset' (http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0), and a code is required from this value set (error message = The System URI could not be determined for the code 'success' in the ValueSet 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.0'; The provided code '#success' was not found in the value set 'http://medcomehmi.dk/ig/dk-ehmi-terminology/ValueSet/ehmi-delivery-status-outcome-valueset|0.8.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 status reporting for EDS from the EDS Client to the EDS Server.\nEdsBasicDeliveryStatus is used when a Patient entity is not required, for instance for status reporting of Acknowledgments.\nA basic EdsBasicDeliveryStatus based on the AuditEvent profile for when a EHMI Basic Delivery Status Messaging action happens successfully.\nIt is used when \n- the resource does not have a Patient subject or is otherwise associated with a Patient\n - when the resource is Patient specific then EdsPatientDeliveryStatus is used\n- And the request is authorized\n- When successful\n - Note a failure EdsBasicDeliveryStatus may follow this pattern, but would not be a successful outcome and should have an OperationOutcome\n - Then the EdsBasicDeliveryStatus recorded will conform'
fsh-generated/resources/ImplementationGuide-dk.ehmi.eds.jsonvalue should not start or finish with whitespace '\nEHMI profile based on the EHMI profile EdsBasicDeliveryStatus.\nEdsPatientDeliveryStatus is used to define the status reporting for EDS from a EDS Client to the EDS Server.\nEdsPatientDeliveryStatus is used when a Patient entity is required, for instance for status reporting of MedCom FHIR Messages.\nA EdsPatientDeliveryStatus based on the AuditEvent profile for when a EHMI Patient Delivery Status Messaging action happens successfully.\nIt is used when \n- the resource has a Patient subject or is otherwise associated with a Patient\n - when the resource is not Patient related then EdsBasicDeliveryStatus is used\n- And the request is authorized\n- When successful\n - Note a failure EdsPatientDeliveryStatus may follow this pattern, but would not be a successful outcome and should have an OperationOutcome\n - Then the EdsPatientDeliveryStatus recorded will conform'