Unable to compare with previous version: Unable to find version history at https://fhir.hl7.at/prenudge/appdata/r4 (Problem #1 with package-list.json at https://fhir.hl7.at/prenudge/appdata/r4: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
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
3
warning
An HTML fragment from the set [dependency-table.xhtml, dependency-table-short.xhtml, dependency-table-nontech.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/at-prenudge-physical-activity-classification-method-cs 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)
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/at-prenudge-pss-codes-codesystem 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)
This property has only a code ('score') and not a URI, so it has no clearly defined meaning in the terminology ecosystemCODESYSTEM_PROPERTY_UNKNOWN_CODE
--
CodeSystem.concept[0] (l1/c3212)
warning
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/at-prenudge-pss-frequency-codesystem 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)
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/athis-answers 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)
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/prenudge-isced-2011-education-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)
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/prenudge-wai-answer 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)
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/prenudge-workability 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)
CodeSystems SHOULD have a stated value for the hierarchyMeaning element so that users know the status and meaning of the code system clearlyCODESYSTEM_CS_NONHL7_MISSING_ELEMENT
--
CodeSystem.property[0] (l1/c10417)
information
This property has only a code ('scale') and not a URI, so it has no clearly defined meaning in the terminology ecosystemCODESYSTEM_PROPERTY_UNKNOWN_CODE
--
CodeSystem.property[1] (l1/c10417)
information
This property has only a code ('score') and not a URI, so it has no clearly defined meaning in the terminology ecosystemCODESYSTEM_PROPERTY_UNKNOWN_CODE
--
CodeSystem.concept[0].concept[0] (l1/c10417)
warning
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
--
Resource
warning
The resource CodeSystem/whoqol-bref-scale 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)
Source Code System http://snomed.info/sct is only supported on the terminology server, so the source codes are not validated for performance reasonsCONCEPTMAP_GROUP_SOURCE_SERVER_SIDE
--
ConceptMap.group[0].target (l1/c3340)
warning
Target Code System http://unitsofmeasure.org doesn't have all content (content = not-present), so the target codes cannot be checkedCONCEPTMAP_GROUP_TARGET_INCOMPLETE
--
ConceptMap.group[1].source (l1/c3848)
information
Source Code System http://loinc.org is only supported on the terminology server, so the source codes are not validated for performance reasonsCONCEPTMAP_GROUP_SOURCE_SERVER_SIDE
--
ConceptMap.group[1].target (l1/c3848)
warning
Target Code System http://unitsofmeasure.org doesn't have all content (content = not-present), so the target codes cannot be checkedCONCEPTMAP_GROUP_TARGET_INCOMPLETE
--
ConceptMap (l1/c3850)
warning
Concept maps published by HL7 SHALL conform to the ShareableConceptMap profile, which says that the element ConceptMap.name should be present, but it is notCONCEPTMAP_SHAREABLE_EXTRA_MISSING_HL7
--
Resource
information
The resource ConceptMap/AtPrenudgeCodeUnitMap 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)
A definition could not be found for Canonical URL 'https://build.fhir.org/ig/HL7Austria/ELGA-AustrianPatientSummary-R4/StructureDefinition-at-aps-device.html'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE
Profile reference 'https://build.fhir.org/ig/HL7Austria/ELGA-AustrianPatientSummary-R4/StructureDefinition-at-aps-device.html' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
ImplementationGuide/hl7.at.fhir.prenudge.appdata.r4: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
ImplementationGuide.dependsOn[3] (l1/c2543)
warning
The ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent appropriate version is 4.0.0. This reference is getting old and the more recent version should be consideredIG_DEPENDENCY_VERSION_WARNING_OLD
--
Resource
information
The resource ImplementationGuide/hl7.at.fhir.prenudge.appdata.r4 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)
UCUM Codes that contain human readable annotations like {drinks} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {drinks} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {drinks} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {sessions} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {sessions} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {sessions} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)TYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS_NOT_IN_UNIT
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {steps} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {steps} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {steps} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {score} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
This element does not match any known slice defined in the profile https://fhir.hl7.at/elga/aps/r4/StructureDefinition/at-aps-patient|1.0.0 (this may not be a problem, but you should check that it's not intended to match a slice)Show Reasoning
This element does not match any known slice Defined in the profile https://fhir.hl7.at/elga/aps/r4/StructureDefinition/at-aps-patient|1.0.0 (this may not be a problem, but you should check that it's not intended to match a slice)
Patient.identifier[0]: discriminator = true and ('SS' in type.coding.code)
,
Patient.identifier[0]: discriminator = true and ('NI' in type.coding.code)
,
Patient.identifier[0]: discriminator = true and ('PI' in type.coding.code)
There are no valid display names found for the code http://loinc.org#106875-8 for language(s) 'de'. The display is 'Perceived stress scale-10 [PSS-10]' which is a valid display for the default language (from https://tx.fhir.org/r4, see log, or see the servers logic) NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_OK
0ms tx-op
1ms http://loinc.org/vs|2.82: Validate "[http://loinc.org#106875-8 ("Perceived stress scale-10 [PSS-10]")]"
2ms http://loinc.org/vs|2.82: Check "http://loinc.org#106875-8"
2ms http://loinc.org/vs|2.82: CodeSystem found: http://loinc.org|2.82 for http://loinc.org|2.82
2ms http://loinc.org/vs|2.82: check code in (http://loinc.org) at Coding
2ms http://loinc.org/vs|2.82: Code "106875-8" found in http://loinc.org|2.82
There are no valid display names found for the code http://loinc.org#106875-8 for language(s) 'de'. The display is 'Perceived stress scale-10 [PSS-10]' which is a valid display for the default language (for 'http://loinc.org#106875-8') (from server, see log, or see the servers logic) Terminology_PassThrough_TX_Message
0ms tx-op
1ms http://loinc.org/vs|2.82: Validate "[http://loinc.org#106875-8 ("Perceived stress scale-10 [PSS-10]")]"
2ms http://loinc.org/vs|2.82: Check "http://loinc.org#106875-8"
2ms http://loinc.org/vs|2.82: CodeSystem found: http://loinc.org|2.82 for http://loinc.org|2.82
2ms http://loinc.org/vs|2.82: check code in (http://loinc.org) at Coding
2ms http://loinc.org/vs|2.82: Code "106875-8" found in http://loinc.org|2.82
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. There are no valid display names found for language(s) 'de-AT'. Default display is 'Yes'
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_ERR
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373066001 ("Ja")]"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373066001"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373066001" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. There are no valid display names found for language(s) 'de-AT'. Default display is 'No'
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_ERR
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373067005 ("Nein")]"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373067005"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373067005" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. There are no valid display names found for language(s) 'de-AT'. Default display is 'Yes'
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_ERR
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373066001 ("Ja")]"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373066001"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373066001" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. There are no valid display names found for language(s) 'de-AT'. Default display is 'No'
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) NO_VALID_DISPLAY_FOUND_NONE_FOR_LANG_ERR
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373067005 ("Nein")]"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373067005"
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
1ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373067005" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
UCUM Codes that contain human readable annotations like {sessions} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {steps} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
UCUM Codes that contain human readable annotations like {steps} 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 checkedTYPE_SPECIFIC_CHECKS_DT_QTY_UCUM_ANNOTATIONS
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US')
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) Display_Name_for__should_be_one_of__instead_of
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373066001 ("Ja")]"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373066001"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373066001" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. Valid display is one of 2 choices: 'No (qualifier value)' (en) or 'No' (en) (for the language(s) 'en-US')
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) Display_Name_for__should_be_one_of__instead_of
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373067005 ("Nein")]"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373067005"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373067005" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US')
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) Display_Name_for__should_be_one_of__instead_of
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373066001 ("Ja")]"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373066001"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373066001" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US')
Editor's Comment: Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein'). (from https://tx.fhir.org/r4, see log, or see the servers logic) Display_Name_for__should_be_one_of__instead_of
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#373066001 ("Ja")]"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#373066001"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "373066001" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
A definition could not be found for Canonical URL 'https://fhir.hl7.at/prenudge/appdata/r4/Questionnaire/QolQuestionnaire'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE
The questionnaire 'https://fhir.hl7.at/prenudge/appdata/r4/Questionnaire/QolQuestionnaire' could not be resolved, so no validation can be performed against the base questionnaireQuestionnaire_QR_Q_NotFound
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'MSG_DEPENDS_ON_DEPRECATED_NOTE
The resource StructureDefinition/at-prenudge-alcoholuse-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)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
--
Resource
information
The resource StructureDefinition/at-prenudge-bloodglucose-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)
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users)SD_VALUE_TYPE_REPEAT_HINT
--
Resource
information
The resource StructureDefinition/at-prenudge-bmi-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)
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users)SD_VALUE_TYPE_REPEAT_HINT
--
Resource
information
The resource StructureDefinition/at-prenudge-bodyheight-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)
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users)SD_VALUE_TYPE_REPEAT_HINT
--
Resource
information
The resource StructureDefinition/at-prenudge-bodyweight-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)
The resource StructureDefinition/at-prenudge-education-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)
The resource StructureDefinition/at-prenudge-muscle-strengthening-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)
The resource StructureDefinition/at-prenudge-nutrition-fruitportions-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)
The resource StructureDefinition/at-prenudge-nutrition-sugarsalty-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)
The resource StructureDefinition/at-prenudge-nutrition-vegetableportions-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)
The resource StructureDefinition/at-prenudge-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)
The resource StructureDefinition/at-prenudge-observation-other-not-quantities 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)
The resource StructureDefinition/at-prenudge-observation-other-quantities 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)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
--
Resource
information
The resource StructureDefinition/at-prenudge-physical-activity-minutes-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)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
--
Resource
information
The resource StructureDefinition/at-prenudge-pss10-score-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)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
--
Resource
information
The resource StructureDefinition/at-prenudge-pss4-score-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)
Questionnaire is labeled as an abstract type, but no concrete descendants were found (check definitions - this is usually an error unless concrete definitions are in some other package)SD_DERIVATION_NO_CONCRETE
--
Resource
information
The resource StructureDefinition/at-prenudge-questionnaire 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)
The resource StructureDefinition/at-prenudge-questionnaireresponse 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)
The resource StructureDefinition/at-prenudge-sitting-hours-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)
The resource StructureDefinition/at-prenudge-sleep-duration-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)
The resource StructureDefinition/at-prenudge-sleep-quality-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)
A definition could not be found for Canonical URL 'https://termgit.elga.gv.at/ValueSet/elga-currentsmokingstatus'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE
The resource StructureDefinition/at-prenudge-smokingstatus-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)
The resource StructureDefinition/at-prenudge-stepcount-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)
The resource StructureDefinition/at-prenudge-whooley-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)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
--
Resource
information
The resource StructureDefinition/at-prenudge-whoqol-bref-score-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)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
--
Resource
information
The resource StructureDefinition/at-prenudge-work-soc-score-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)
The resource ValueSet/at-prenudge-pss-frequency-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)
The resource ValueSet/at-prenudge-whooley-screen-result 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/prenudge-alcoholuse-frequency 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/prenudge-bloodglucose-mealcontext 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/prenudge-isced-2011-education-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)
The resource ValueSet/prenudge-nutrition-consumption-frequency-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)
The resource ValueSet/prenudge-nutrition-sugarsalty-frequency-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)
The resource ValueSet/prenudge-observation-method 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)
Wrong Display Name 'Activity intensity' for http://loinc.org#66270-0. Valid display is one of 3 choices: 'Activity intensity [PhenX]' (en-US), 'Activity intensity [PhenX]' (en-US) or 'Activity intensity PhenX' (en-US) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
0ms tx-op
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Validate "[http://snomed.info/sct#82832008 ("General body state finding (finding)")]"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Check "http://snomed.info/sct#82832008"
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: CodeSystem found: http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201 for http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: check code in (http://snomed.info/sct) at Coding
0ms http://snomed.info/sct/vs|http://snomed.info/sct/900000000000207008/version/20250201: Code "82832008" found in http://snomed.info/sct|http://snomed.info/sct/900000000000207008/version/20250201
--
Resource
warning
The resource ValueSet/prenudge-other-observations-codes 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)
Wrong Display Name 'finding' for http://unitsofmeasure.org#{finding}. Valid display is one of 2 choices: '{finding}' (en) or '1' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
Wrong Display Name 'intensity' for http://unitsofmeasure.org#{intensity}. Valid display is one of 2 choices: '{intensity}' (en) or '1' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
--
Resource
warning
The resource ValueSet/prenudge-other-observations-units 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/prenudge-physical-activity-classification-method-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)
The resource ValueSet/prenudge-wai-physical-demands-answer 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/prenudge-whoqol-bref-score-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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/AlcoholQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
--
Resource
information
The resource StructureMap/BloodGlucoseQuestionnaireResponseToObservation 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)
The target path val.value refers to the path QuestionnaireResponse.item.answer.value[x].value which could be a reference to multiple elements (boolean.value, decimal.value, integer.value, date.value, dateTime.value, time.value, string.value, uri.value, Quantity.value). No further checking can be performedSM_TARGET_PATH_MULTIPLE_MATCHES
The target path val.value refers to the path QuestionnaireResponse.item.answer.value[x].value which could be a reference to multiple elements (boolean.value, decimal.value, integer.value, date.value, dateTime.value, time.value, string.value, uri.value, Quantity.value). No further checking can be performedSM_TARGET_PATH_MULTIPLE_MATCHES
The target path val.value refers to the path QuestionnaireResponse.item.answer.value[x].value which could be a reference to multiple elements (boolean.value, decimal.value, integer.value, date.value, dateTime.value, time.value, string.value, uri.value, Quantity.value). No further checking can be performedSM_TARGET_PATH_MULTIPLE_MATCHES
--
Resource
information
The resource StructureMap/BmiQuestionnaireResponseToObservations 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)
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
--
Resource
information
The resource StructureMap/EducationQuestionnaireResponseToObservation 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/MuscleStrengtheningEhisPaqQuestionnaireResponseToObservation 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/MuscleStrengtheningQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/NutritionFruitPortionsQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/NutritionSugarSaltyFrequencyQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/NutritionVegetablePortionsQuestionnaireResponseToObservation 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: smp-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation (name.matches('[A-Z]([A-Za-z0-9_]){0,254}'))'http://hl7.org/fhir/StructureDefinition/StructureMap#smp-0
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path ans.valueInteger refers to the path QuestionnaireResponse.item.answer.valueInteger which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/PhysicalActivityMinutesQtoO 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/Pss10QuestionnaireResponseToObservation 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/Pss4QuestionnaireResponseToObservation 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)
The source statement doesn't assign a variable to the source - check that this is what is intendedSM_RULE_SOURCE_UNASSIGNED
--
Resource
information
The resource StructureMap/QuestionnaireResponseToObservationBase 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/WHOQOLBrefQuestionnaireResponseToObservation 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path ans.valueDecimal refers to the path QuestionnaireResponse.item.answer.valueDecimal which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/SittingHoursQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
--
Resource
information
The resource StructureMap/SleepDurationQuestionnaireResponseToObservation 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)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
--
Resource
information
The resource StructureMap/SleepQualityBase 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)
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/SmokingStatusQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The source statement doesn't assign a variable to the source - check that this is what is intendedSM_RULE_SOURCE_UNASSIGNED
--
Resource
information
The resource StructureMap/StepCountQuestionnaireResponseToObservation 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)
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_TARGET_PATH_INVALID
--
Resource
information
The resource StructureMap/WhooleyQuestionnaireResponseToObservation 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)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown
Editor's Comment: StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.SM_SOURCE_PATH_INVALID
--
Resource
information
The resource StructureMap/WorkSocQuestionnaireResponseToObservation 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)
Some citizen-facing answerOptions/answers deliberately use a German (de-AT) display text for codes from terminologies that have no official German designation (e.g. SNOMED CT), so the UI can render a plain-language answer without a separate translation lookup at runtime. The IG Publisher's display-name check flags this as a mismatch whenever a SNOMED-/LOINC-aware terminology service is available, since only the English canonical display is registered. This suppresses the IG Publisher build-time warning only - it does not affect runtime validation on a FHIR server that itself checks display names against a terminology service. Current example: Whooley questionnaire, SNOMED CT 373066001/373067005 ('Yes'/'No' shown as 'Ja'/'Nein').
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. There are no valid display names found for language(s) 'de-AT'. Default display is 'Yes' (2 uses)
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US') (3 uses)
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. There are no valid display names found for language(s) 'de-AT'. Default display is 'No' (2 uses)
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. Valid display is one of 2 choices: 'No (qualifier value)' (en) or 'No' (en) (for the language(s) 'en-US') (1 uses)
StructureMap BackboneElement path validation: the IG Publisher validates FML source/target paths (src.answer, answer.valueCoding, ans.valueInteger, ans.valueDecimal, tgt.effectiveDateTime, tgt.valueCodeableConcept, etc.) against the StructureMap group's declared input type (e.g. QuestionnaireResponse, Observation) instead of the actual type of the element passed into that group (e.g. QuestionnaireResponse.item.answer, QuestionnaireResponse.item.answer.valueCoding). This is a known FML R4 limitation - all of these paths are valid for the element actually bound in the group at runtime.
Der Quellpfad ans.valueDecimal bezieht sich auf den Pfad QuestionnaireResponse.item.answer.valueDecimal, der unbekannt ist (0 uses)
Der Quellpfad ans.valueInteger bezieht sich auf den Pfad QuestionnaireResponse.item.answer.valueInteger, der unbekannt ist (0 uses)
Der Quellpfad answer.valueCoding bezieht sich auf den Pfad QuestionnaireResponse.item.answer.valueCoding, der unbekannt ist (0 uses)
Der Quellpfad src.answer bezieht sich auf den Pfad QuestionnaireResponse.answer, der unbekannt ist (0 uses)
Der Zielpfad tgt.effectiveDateTime bezieht sich auf den Pfad Observation.effectiveDateTime, der unbekannt ist (0 uses)
Der Zielpfad tgt.valueCodeableConcept bezieht sich auf den Pfad Observation.valueCodeableConcept, der unbekannt ist (0 uses)
The source path ans.valueDecimal refers to the path QuestionnaireResponse.item.answer.valueDecimal which is unknown (1 uses)
The source path ans.valueInteger refers to the path QuestionnaireResponse.item.answer.valueInteger which is unknown (1 uses)
The source path answer.valueCoding refers to the path QuestionnaireResponse.item.answer.valueCoding which is unknown (7 uses)
The source path src.answer refers to the path QuestionnaireResponse.answer which is unknown (33 uses)
The target path tgt.effectiveDateTime refers to the path Observation.effectiveDateTime which is unknown (12 uses)
The target path tgt.valueCodeableConcept refers to the path Observation.valueCodeableConcept which is unknown (19 uses)
Concept maps published by HL7 SHALL conform to the ShareableConceptMap profile, which says that the element ConceptMap.name should be present, but it is not
This element does not match any known slice defined in the profile https://fhir.hl7.at/elga/aps/r4/StructureDefinition/at-aps-patient|1.0.0 (this may not be a problem, but you should check that it's not intended to match a slice)
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US')
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. Valid display is one of 2 choices: 'No (qualifier value)' (en) or 'No' (en) (for the language(s) 'en-US')
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US')
Wrong Display Name 'Ja' for http://snomed.info/sct#373066001. Valid display is one of 2 choices: 'Yes (qualifier value)' (en) or 'Yes' (en) (for the language(s) 'en-US')
The ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent appropriate version is 4.0.0. This reference is getting old and the more recent version should be considered
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. There are no valid display names found for language(s) 'de-AT'. Default display is 'No'
Wrong Display Name 'Nein' for http://snomed.info/sct#373067005. There are no valid display names found for language(s) 'de-AT'. Default display is 'No'
There are no valid display names found for the code http://loinc.org#106875-8 for language(s) 'de'. The display is 'Perceived stress scale-10 [PSS-10]' which is a valid display for the default language
The questionnaire 'https://fhir.hl7.at/prenudge/appdata/r4/Questionnaire/QolQuestionnaire' could not be resolved, so no validation can be performed against the base questionnaire
Questionnaire is labeled as an abstract type, but no concrete descendants were found (check definitions - this is usually an error unless concrete definitions are in some other package)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The target path val.value refers to the path QuestionnaireResponse.item.answer.value[x].value which could be a reference to multiple elements (boolean.value, decimal.value, integer.value, date.value, dateTime.value, time.value, string.value, uri.value, Quantity.value). No further checking can be performed
The target path val.value refers to the path QuestionnaireResponse.item.answer.value[x].value which could be a reference to multiple elements (boolean.value, decimal.value, integer.value, date.value, dateTime.value, time.value, string.value, uri.value, Quantity.value). No further checking can be performed
The target path val.value refers to the path QuestionnaireResponse.item.answer.value[x].value which could be a reference to multiple elements (boolean.value, decimal.value, integer.value, date.value, dateTime.value, time.value, string.value, uri.value, Quantity.value). No further checking can be performed
A definition could not be found for Canonical URL 'https://build.fhir.org/ig/HL7Austria/ELGA-AustrianPatientSummary-R4/StructureDefinition-at-aps-device.html'
UCUM Codes that contain human readable annotations like {drinks} 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
UCUM Codes that contain human readable annotations like {drinks} 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
UCUM Codes that contain human readable annotations like {drinks} 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
UCUM Codes that contain human readable annotations like {sessions} 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
UCUM Codes that contain human readable annotations like {sessions} 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
UCUM Codes that contain human readable annotations like {sessions} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {steps} 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
UCUM Codes that contain human readable annotations like {steps} 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
UCUM Codes that contain human readable annotations like {steps} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {score} 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
UCUM Codes that contain human readable annotations like {sessions} 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
UCUM Codes that contain human readable annotations like {steps} 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
UCUM Codes that contain human readable annotations like {steps} 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
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)
UCUM Codes that contain human readable annotations like {serving} 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 'Portionen' SHOULD contain the annotation (it does not)
There are no valid display names found for the code http://loinc.org#106875-8 for language(s) 'de'. The display is 'Perceived stress scale-10 [PSS-10]' which is a valid display for the default language (for 'http://loinc.org#106875-8')
Profile reference 'https://build.fhir.org/ig/HL7Austria/ELGA-AustrianPatientSummary-R4/StructureDefinition-at-aps-device.html' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Wrong Display Name 'Activity intensity' for http://loinc.org#66270-0. Valid display is one of 3 choices: 'Activity intensity [PhenX]' (en-US), 'Activity intensity [PhenX]' (en-US) or 'Activity intensity PhenX' (en-US) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'finding' for http://unitsofmeasure.org#{finding}. Valid display is one of 2 choices: '{finding}' (en) or '1' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'intensity' for http://unitsofmeasure.org#{intensity}. Valid display is one of 2 choices: '{intensity}' (en) or '1' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
hl7.at.fhir.prenudge.appdata.r4
hl7.terminology.r4
