Validation Results for TransversalClinicalCore

Generated Thu Aug 20 13:12:34 CEST 2026, FHIR version 4.0.1 for hl7.fhir.be.core-clinical#1.3.0 (canonical = https://www.ehealth.fgov.be/standards/fhir/core-clinical (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.3.2
Publication Code:n/a . PackageId = hl7.fhir.be.core-clinical, Canonical = https://www.ehealth.fgov.be/standards/fhir/core-clinical
Realm Check for n/a:
  • n/a
Language Info:Stated Languages: n/a. IG Resource Lang: en. 1 of 33 (3%) of resources have a language. Population Policy: NONE
Publication Request:
package-idhl7.fhir.be.core-clinical
version1.3.0
pathhttps://www.ehealth.fgov.be/standards/fhir/core-clinical/1.3.0
Pub-Modemilestone
statusrelease
Release-LabelSTU1
Sequence (Group)Trial Use (current: 'Trial Use', others = n/a)
desceHealth FHIR core-clinical Profiles for Belgium
RelatedIgs(None Found)
No Messages found - all good
Supressed Messages:3 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.be.core-clinical1.3.0R4https://www.ehealth.fgov.be/standards/fhir/core-clinical
... hl7.terminology.r47.3.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.3.0
.... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0
..... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0Latest Release is 7.3.0
...... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.3.0
... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0 (as above)
... hl7.fhir.be.core2.2.0 MR4https://www.ehealth.fgov.be/standards/fhir/corehttps://www.ehealth.fgov.be/standards/fhir/core/2.2.0
.... hl7.terminology.r47.3.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.3.0 (as above)
.... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0 (as above)
.... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0 (as above). Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2Internal Dependency
Templates: hl7.be.fhir.template#current -> fhir2.base.template#current
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):https://dte-tx.ehealth.fgov.be/r4 (details)
HTA Analysis:1 issue
R5 Dependencies:
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 1.2.0
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 0, warn = 23, info = 17, broken links = 0, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors000
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\CodeSystem-be-cs-bodysite010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\CodeSystem-be-cs-problem-category010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\CodeSystem-be-cs-problem-origin-type010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\CodeSystem-be-cs-score010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\CodeSystem-be-cs-score-category010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\StructureDefinition-be-problem021
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-ProblemCategoryVS020
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-ProblemCodeVS020
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-ProblemDiseaseCourseVS020
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-body-topography010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-bodysite010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-laterality010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-problem-category010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-problem-code010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-problem-origin-type010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-reaction-manifestation-code010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-score011
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-scorecategory010
C:\temp\Publications\core-clinical\temp\ig-builds\hl7.fhir.be.core-clinical#1.3.0-milestone\fsh-generated\resources\ValueSet-be-vs-severity010

n/a Show Validation Information


fsh-generated\resources\CodeSystem-be-cs-bodysite.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource CodeSystem/be-cs-bodysite 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) --

fsh-generated\resources\CodeSystem-be-cs-problem-category.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource CodeSystem/be-cs-problem-category 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) --

fsh-generated\resources\CodeSystem-be-cs-problem-origin-type.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource CodeSystem/be-cs-problem-origin-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) --

fsh-generated\resources\CodeSystem-be-cs-score.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource CodeSystem/be-cs-score 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) --

fsh-generated\resources\CodeSystem-be-cs-score-category.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource CodeSystem/be-cs-score-category 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) --

fsh-generated\resources\StructureDefinition-be-problem.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[9]​.type[0]​.profile[0] (l1​/c74162)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-dueTo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (from hl7.fhir.uv.extensions.r4#5.3.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-dueTo' to 'http://hl7.org/fhir/StructureDefinition/condition-dueTo|5.3.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.differential​.element[3]​.type[0]​.profile[0] (l1​/c121494)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-dueTo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (from hl7.fhir.uv.extensions.r4#5.3.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-dueTo' to 'http://hl7.org/fhir/StructureDefinition/condition-dueTo|5.3.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
ResourceinformationThe resource StructureDefinition/be-problem 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) --

fsh-generated\resources\ValueSet-ProblemCategoryVS.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet (l1/c1059)warningPublished value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present --
ResourcewarningThe resource ValueSet/ProblemCategoryVS 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) --

fsh-generated\resources\ValueSet-ProblemCodeVS.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet (l1/c1027)warningPublished value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present --
ResourcewarningThe resource ValueSet/ProblemCodeVS 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) --

fsh-generated\resources\ValueSet-ProblemDiseaseCourseVS.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet (l1/c1446)warningPublished value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present --
ResourcewarningThe resource ValueSet/ProblemDiseaseCourseVS 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) --

fsh-generated\resources\ValueSet-be-vs-body-topography.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-body-topography 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) --

fsh-generated\resources\ValueSet-be-vs-bodysite.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-bodysite 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) --

fsh-generated\resources\ValueSet-be-vs-laterality.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-laterality 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) --

fsh-generated\resources\ValueSet-be-vs-problem-category.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-problem-category 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) --

fsh-generated\resources\ValueSet-be-vs-problem-code.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-problem-code should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

fsh-generated\resources\ValueSet-be-vs-problem-origin-type.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-problem-origin-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) --

fsh-generated\resources\ValueSet-be-vs-reaction-manifestation-code.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-reaction-manifestation-code should have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) --

fsh-generated\resources\ValueSet-be-vs-score.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[0] (l1/c8335)informationThis SNOMED-CT based include has some concepts with semantic tags (FSN terms) and some without (preferred terms) - check that this is what is intended (examples for FSN: [Visual analog scale score (observable entity), Mini-mental state examination score (observable entity), Malnutrition universal screening tool score (observable entity), Norton Scale score (observable entity), Thirty second chair stand test score (observable entity)] and examples for no FSN: [FINDRISC (Finnish Diabetes Risk Score) score, Index of Independence in Activities of Daily Living, Pain Assessment in Advanced Dementia Scale, Subjective Global Assessment, Waterlow pressure sore risk score]) VALUESET_CONCEPT_DISPLAY_SCT_TAG_MIXED--
ResourcewarningThe resource ValueSet/be-vs-score 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) --

fsh-generated\resources\ValueSet-be-vs-scorecategory.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-scorecategory 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) --

fsh-generated\resources\ValueSet-be-vs-severity.json Show Validation Information (1)

PathSeverityMessageValidating
ResourcewarningThe resource ValueSet/be-vs-severity 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) --

Suppressed Messages (Warnings, hints, broken links)

no examples provided yet for some profiles

Errors sorted by type


MSG_DEPENDS_ON_DEPRECATED_NOTE

fsh-generated\resources\StructureDefinition-be-clinical-observation.jsonThe extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'StructureDefinition

TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS

fsh-generated\resources\StructureDefinition-be-problem.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-dueTo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (from hl7.fhir.uv.extensions.r4#5.3.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-dueTo' to 'http://hl7.org/fhir/StructureDefinition/condition-dueTo|5.3.0'StructureDefinition
fsh-generated\resources\StructureDefinition-be-problem.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-dueTo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.3.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (from hl7.fhir.uv.extensions.r4#5.3.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-dueTo' to 'http://hl7.org/fhir/StructureDefinition/condition-dueTo|5.3.0'StructureDefinition

VALUESET_CONCEPT_DISPLAY_SCT_TAG_MIXED

fsh-generated\resources\ValueSet-be-vs-score.jsonThis SNOMED-CT based include has some concepts with semantic tags (FSN terms) and some without (preferred terms) - check that this is what is intended (examples for FSN: [Visual analog scale score (observable entity), Mini-mental state examination score (observable entity), Malnutrition universal screening tool score (observable entity), Norton Scale score (observable entity), Thirty second chair stand test score (observable entity)] and examples for no FSN: [FINDRISC (Finnish Diabetes Risk Score) score, Index of Independence in Activities of Daily Living, Pain Assessment in Advanced Dementia Scale, Subjective Global Assessment, Waterlow pressure sore risk score])--