Validation Results for TransversalClinicalCore

Generated Wed Apr 08 07:33:46 UTC 2026, FHIR version 4.0.1 for hl7.fhir.be.core-clinical#1.1.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.2.5
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:	This IG has no language information
Publication Request:	RelatedIgs (None Found) Version 1.1.0 has already been published Publication Request is for version v1.1.0 which is already published
Supressed Messages:	6 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.be.core-clinical 1.1.0 R4 https://www.ehealth.fgov.be/standards/fhir/core-clinical hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.be.core 2.1.2 M R4 https://www.ehealth.fgov.be/standards/fhir/core https://www.ehealth.fgov.be/standards/fhir/core/2.1.2 hl7.terminology.r4 6.0.2 O R4 http://terminology.hl7.org http://terminology.hl7.org/6.0.2 Latest Release is 7.1.0 hl7.fhir.uv.extensions.r4 5.1.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0 Latest Release is 5.2.0 hl7.fhir.uv.tools.r4 1.1.2 M R4 http://hl7.org/fhir/tools http://hl7.org/fhir/tools/1.1.2 Internal Dependency Templates: hl7.be.fhir.template#current -> fhir.base.template#1.0.0
Related IGs:	n/a
Dependent IGs:	no references
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4, https://apps.health.belgium.be/ontoserver/fhir, https://tx.fhir.org/r4 (details)
HTA Analysis:	7 issues
R5 Dependencies:	http://hl7.org/fhir/5.0/StructureDefinition/extension-Procedure.recorded
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), Condition (10 uses), Procedure (8 uses), MedicationAdministration (6 uses), Immunization (5 uses), MedicationStatement (5 uses), ConditionClinicalStatusCodes (3 uses), ConditionVerificationStatus (3 uses), Condition/DiagnosisSeverity (2 uses), Practitioner (4 uses), PractitionerRole (4 uses), Organization (5 uses), CommonLanguages (5 uses), CarePlan (4 uses), DeviceRequest (3 uses), ImmunizationRecommendation (3 uses), MedicationRequest (3 uses), NutritionOrder (3 uses), ServiceRequest (4 uses), MedicationDispense (3 uses), ImagingStudy (6 uses), ObservationCategoryCodes (2 uses), LOINCCodes (5 uses), Group (6 uses), Device (9 uses), Location (5 uses), Encounter (5 uses), CareTeam (4 uses), RelatedPerson (6 uses), SNOMEDCTBodyStructures (4 uses), ObservationMethods (3 uses), Specimen (3 uses), DeviceMetric (3 uses), ObservationReferenceRangeMeaningCodes (3 uses), ObservationReferenceRangeAppliesToCodes (3 uses), QuestionnaireResponse (6 uses), MolecularSequence (6 uses), DocumentReference (5 uses), Media (3 uses), ConditionStage (1 uses), ClinicalImpression (1 uses), DiagnosticReport (3 uses), ConditionStageType (1 uses), ManifestationAndSymptomCodes (1 uses), PlanDefinition (1 uses), ActivityDefinition (1 uses), Measure (1 uses), Questionnaire (1 uses), EventStatus (1 uses), ProcedureCategoryCodes(SNOMEDCT) (1 uses), ProcedureCodes(SNOMEDCT) (1 uses), ProcedurePerformerRoleCodes (1 uses), ProcedureReasonCodes (1 uses), ProcedureOutcomeCodes(SNOMEDCT) (1 uses), Composition (1 uses), Condition/Problem/DiagnosisCodes (1 uses), ProcedureFollowUpCodes(SNOMEDCT) (1 uses), ProcedureDeviceActionCodes (1 uses), Medication (1 uses), Substance (1 uses), FHIRDeviceTypes (1 uses) hl7.fhir.uv.extensions.r4#5.2.0: SDTypeCharacteristics (1 uses)
Modifier Extensions:	(none)
Previous Version Comparison:
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary:	errors = 3, warn = 14, info = 5, broken links = 0, pinned = n/a. Show Message Ids

n/a Show Validation Information

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

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

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

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

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

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

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

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

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

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

Suppressed Messages (Warnings, hints, broken links)

This is inherited from the base resource

• WARNING: StructureDefinition/myObservation: StructureDefinition.snapshot.element[15].mapping[3].map: value should not start or finish with whitespace (0 uses)

We're expecting these to not match the slice - we're showing how you can use slicing to define the one repetition you want even when many repetitions might be present

• INFORMATION: Patient/example: Patient.name[0]: This element does not match any known slice defined in the profile http://somewhere.org/fhir/uv/myig/StructureDefinition/mypatient (0 uses)
• INFORMATION: Patient/example: Patient.name[1]: This element does not match any known slice defined in the profile http://somewhere.org/fhir/uv/myig/StructureDefinition/mypatient (0 uses)

no examples provided yet for some profiles

• %The Implementation Guide contains no examples for this profile% (4 uses)
• The Implementation Guide contains no examples for this data type profile (1 uses)
• The Implementation Guide contains no examples for this extension (4 uses)

Errors sorted by type

MSG_DEPENDS_ON_DEPRECATED

TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS

VALUESET_BAD_FILTER_VALUE_VALID_CODE

VALUESET_INC_NO_BATCH_ON_SERVER