Fixed uuid invariants, removed Patient.deceased MustSupport, added Dependencies tab, and updated profiles with new cardinalities, MustSupport, and narrative obligations.
descmd
Invariants medcom-uuidv4 and medcom-uuidv5 is corrected as it did not work as intended.
MustSupport for the element deceased in MedComCorePatient is removed, as it is not relevant for all MedCom standards using the profile.
Dependencies tab in the menu bar is added.
The following cardinalities, MustSupport, and Obligation (SHALL:in-narrative) have been added:
The HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide
2
warning
An HTML fragment from the set [cross-version-analysis.xhtml, cross-version-analysis-inline.xhtml] is not included anywhere in the produced implementation guide
ActorDefinition/ProducerActor: ActorDefinition: Validated against fhir.ActorDefinition
Path
Severity
Message
ActorDefinition.jurisdiction[0] (l1/c946)
information
Reference to deprecated ValueSet http://hl7.org/fhir/5.0/ValueSet/jurisdiction|5.0.0 (from https://tx.fhir.org/r4) MSG_DEPRECATED
ActorDefinition (l1/c964)
warning
Constraint failed: cnl-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation' (defined in http://hl7.org/fhir/StructureDefinition/ActorDefinition)http://hl7.org/fhir/StructureDefinition/ActorDefinition#cnl-0
Resource
information
The resource ActorDefinition/ProducerActor could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Review the extension type for medcom-core-contact-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for medcom-core-datetime-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
The definition for the element 'DiagnosticReport.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-corediagnosticreport-status' which is experimental, but this structure is not labeled as experimentalSD_ED_EXPERIMENTAL_BINDING
The definition for the element 'DiagnosticReport.code' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/MedComDiagnosticReportCodesValueset' which is experimental, but this structure is not labeled as experimentalSD_ED_EXPERIMENTAL_BINDING
The definition for the element 'DiagnosticReport.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-corediagnosticreport-status' which is experimental, but this structure is not labeled as experimentalSD_ED_EXPERIMENTAL_BINDING
The definition for the element 'DiagnosticReport.code' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/MedComDiagnosticReportCodesValueset' which is experimental, but this structure is not labeled as experimentalSD_ED_EXPERIMENTAL_BINDING
Pinned the version of http://terminology.hl7.org/ValueSet/v3-ActEncounterCode to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#5.0.0), 3.0.0 (hl7.terminology.r4#6.0.2)PIN_VERSION
Pinned the version of http://terminology.hl7.org/ValueSet/v3-ActPriority to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#5.0.0), 3.0.0 (hl7.terminology.r4#6.0.2)PIN_VERSION
Review the extension type for medcom-core-identifier-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
The definition for the element 'Observation.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-core-observation-status' which is experimental, but this structure is not labeled as experimentalSD_ED_EXPERIMENTAL_BINDING
The definition for the element 'Observation.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-core-observation-status' which is experimental, but this structure is not labeled as experimentalSD_ED_EXPERIMENTAL_BINDING
Pinned the version of http://hl7.org/fhir/StructureDefinition/address-official to 5.2.0 from choices of 5.1.0 (hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0)PIN_VERSION
Review the extension type for medcom-core-sender-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Unable to check if http://medcomfhir.dk/fhir/core/1.0/ValueSet/medcom-core-attachmentMimeTypes is a proper subset of http://hl7.org/fhir/ValueSet/mimetypes|4.0.1 - base value set is too large to check (0 uses)
Is just noise
%This element does not match any known slice defined in the profile% (30 uses)
Not sure what the context should be currently
%Review the extension type for medcom-core-practitioner-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhere% (1 uses)
This is an example and is expected
%Reference is external which isn't supported by the specified aggregation mode(s) for the reference (bundled)% (2 uses)
We don't need examples for extensions
%The Implementation Guide contains no examples for this extension% (5 uses)
Pinned the version of http://terminology.hl7.org/ValueSet/v3-ActEncounterCode to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#5.0.0), 3.0.0 (hl7.terminology.r4#6.0.2)
Pinned the version of http://terminology.hl7.org/ValueSet/v3-ActPriority to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#5.0.0), 3.0.0 (hl7.terminology.r4#6.0.2)
Pinned the version of http://hl7.org/fhir/StructureDefinition/address-official to 5.2.0 from choices of 5.1.0 (hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0)
Review the extension type for medcom-core-contact-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for medcom-core-datetime-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for medcom-core-identifier-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for medcom-core-sender-extension: extensions should not have a context of Element unless it's really intended that they can be used anywhere
The definition for the element 'DiagnosticReport.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-corediagnosticreport-status' which is experimental, but this structure is not labeled as experimental
The definition for the element 'DiagnosticReport.code' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/MedComDiagnosticReportCodesValueset' which is experimental, but this structure is not labeled as experimental
The definition for the element 'DiagnosticReport.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-corediagnosticreport-status' which is experimental, but this structure is not labeled as experimental
The definition for the element 'DiagnosticReport.code' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/MedComDiagnosticReportCodesValueset' which is experimental, but this structure is not labeled as experimental
The definition for the element 'Observation.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-core-observation-status' which is experimental, but this structure is not labeled as experimental
The definition for the element 'Observation.status' binds to the value set 'http://medcomfhir.dk/ig/terminology/ValueSet/medcom-core-observation-status' which is experimental, but this structure is not labeled as experimental
medcom.fhir.dk.core
hl7.fhir.uv.tools.r4