Unable to compare with previous version: Unable to find version history at https://fhir.amakomaya.com (Problem #1 with package-list.json at https://fhir.amakomaya.com: Error parsing JSON source: Unexpected content '<' in json format at Line 1 (path=[null]))
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Unable to find ImplementationGuide.definition.resource.description for the resource Communication/amk-communication-notification. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warning
Unable to find ImplementationGuide.definition.resource.description for the resource Consent/amk-consent-opt-in. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warning
Unable to find ImplementationGuide.definition.resource.description for the resource Person/AMKPersonMasterPersonIndex. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
1
warning
The HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide
4
warning
The HTML fragment 'globals-table.xhtml' is not included anywhere in the produced implementation guide
The resource CodeSystem/application-mode should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.experimental is mandatory, but it is not presentCODESYSTEM_SHAREABLE_MISSING
--
Resource
warning
The resource CodeSystem/identifier-type should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.experimental is mandatory, but it is not presentCODESYSTEM_SHAREABLE_MISSING
--
Resource
warning
The resource CodeSystem/locations should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.experimental is mandatory, but it is not presentCODESYSTEM_SHAREABLE_MISSING
--
Resource
warning
The resource CodeSystem/tele-call-consent-categories should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The Target Code System http://snomed.info/sct is not fully defined and populated, and no targetScope is specified, so the target code checking will not be performedCONCEPTMAP_GROUP_TARGET_UNKNOWN
--
ConceptMap (l1/c2266)
warning
Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.name should be present, but it is notCONCEPTMAP_SHAREABLE_EXTRA_MISSING
--
ConceptMap (l1/c2266)
warning
Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.experimental is mandatory, but it is not presentCONCEPTMAP_SHAREABLE_MISSING
--
Resource
information
The resource ConceptMap/AdministrativeGenderCM 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)
Constraint failed: cmd-12: 'If ConceptMap.group.element.noMap is present and has a value of 'true', there SHOULD be some comments, unless the status is 'draft' (comment.exists() or (%resource.status = 'draft') or (noMap != true))' (defined in http://hl7.org/fhir/StructureDefinition/ConceptMap) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ConceptMap#cmd-12
Constraint failed: cmd-12: 'If ConceptMap.group.element.noMap is present and has a value of 'true', there SHOULD be some comments, unless the status is 'draft' (comment.exists() or (%resource.status = 'draft') or (noMap != true))' (defined in http://hl7.org/fhir/StructureDefinition/ConceptMap) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ConceptMap#cmd-12
The Target Code System http://snomed.info/sct is not fully defined and populated, and no targetScope is specified, so the target code checking will not be performedCONCEPTMAP_GROUP_TARGET_UNKNOWN
The source display 'Yes / Affirmative' for the code 'http://terminology.hl7.org/CodeSystem/v2-0532|3.0.0#Y' is not valid. Possible displays: 'Yes', 'Ja'CONCEPTMAP_GROUP_SOURCE_DISPLAY_INVALID
The source display 'No / Negative' for the code 'http://terminology.hl7.org/CodeSystem/v2-0532|3.0.0#N' is not valid. Possible displays: 'No', 'Nein'CONCEPTMAP_GROUP_SOURCE_DISPLAY_INVALID
--
ConceptMap (l1/c2243)
warning
Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.name should be present, but it is notCONCEPTMAP_SHAREABLE_EXTRA_MISSING
--
ConceptMap (l1/c2243)
warning
Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.experimental is mandatory, but it is not presentCONCEPTMAP_SHAREABLE_MISSING
--
Resource
information
The resource ConceptMap/YesNoCM 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)
Coding has no system. A code with no system has no defined meaning, and it cannot be validated. A system should be providedCoding_has_no_system__cannot_validate
UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablet' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
Constraint failed: qty-4: 'Processing UCUM codes with annotations ({..}) can be misleading. (code.exists() implies code.matches('\\{.*?\\}').not())' (defined in http://hl7.org/fhir/StructureDefinition/Quantity) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/Quantity#qty-4
UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablet' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
Constraint failed: qty-4: 'Processing UCUM codes with annotations ({..}) can be misleading. (code.exists() implies code.matches('\\{.*?\\}').not())' (defined in http://hl7.org/fhir/StructureDefinition/Quantity) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/Quantity#qty-4
UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablet' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
Constraint failed: qty-4: 'Processing UCUM codes with annotations ({..}) can be misleading. (code.exists() implies code.matches('\\{.*?\\}').not())' (defined in http://hl7.org/fhir/StructureDefinition/Quantity) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/Quantity#qty-4
Constraint failed: obs-12: 'All observations SHOULD have a performer (performer.exists())' (defined in http://hl7.org/fhir/StructureDefinition/Observation)http://hl7.org/fhir/StructureDefinition/Observation#obs-12
Constraint failed: obs-12: 'All observations SHOULD have a performer (performer.exists())' (defined in http://hl7.org/fhir/StructureDefinition/Observation)http://hl7.org/fhir/StructureDefinition/Observation#obs-12
Constraint failed: obs-12: 'All observations SHOULD have a performer (performer.exists())' (defined in http://hl7.org/fhir/StructureDefinition/Observation)http://hl7.org/fhir/StructureDefinition/Observation#obs-12
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-appointment 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-binary 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-communication 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-consent 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-core-immunization 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-core-medication-dispense 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-core-patient 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-core-person 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-33: 'If there's more than one bindable type, it's usually an error for there to be a binding (type.where(code in 'code' | 'Coding' | 'CodeableConcept' | 'CodeableReference' | 'uri' | 'string' | 'Quantity').count() > 1 implies binding.empty())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-33
The resource StructureDefinition/amk-document-reference 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-encounter 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-healthcare-service 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-location 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-observation 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-organization 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/amk-relatedperson 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)
Constraint failed: eld-31: 'additionalBindings should have a key (key.exists())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-31
The resource StructureDefinition/reminder-task 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)
Coding has no system. A code with no system has no defined meaning, and it cannot be validated. A system should be providedCoding_has_no_system__cannot_validate
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/administrative-gender should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/amk-application-mode should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/condition-code should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/district should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/educational-level should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/localbody should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/medication should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/observation-vs should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/province should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/severities should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/tele-call-consent-valueset should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
Resource
warning
The resource ValueSet/vaccine should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/yes-no should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.experimental is mandatory, but it is not present
Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.experimental is mandatory, but it is not present
Published code systems SHOULD conform to the ShareableCodeSystem profile, which says that the element CodeSystem.experimental is mandatory, but it is not present
The source display 'Yes / Affirmative' for the code 'http://terminology.hl7.org/CodeSystem/v2-0532|3.0.0#Y' is not valid. Possible displays: 'Yes', 'Ja'
The Target Code System http://snomed.info/sct is not fully defined and populated, and no targetScope is specified, so the target code checking will not be performed
The Target Code System http://snomed.info/sct is not fully defined and populated, and no targetScope is specified, so the target code checking will not be performed
Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.experimental is mandatory, but it is not present
Published concept maps SHOULD conform to the ShareableConceptMap profile, which says that the element ConceptMap.experimental is mandatory, but it is not present
UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablet' SHOULD contain the annotation (it does not)
UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablet' SHOULD contain the annotation (it does not)
UCUM Codes that contain human readable annotations like {tbl} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'tablet' SHOULD contain the annotation (it does not)
None of the codings provided are in the value set 'Service type' (http://terminology.hl7.org/ValueSet/service-type|1.0.1), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/location-physical-type#bu)
amakomaya.fhir.core
hl7.terminology.r5
