Unable to compare with previous version: Unable to find version history at https://rarelink.bih-charite.de/fhir (Problem #1 with package-list.json at https://rarelink.bih-charite.de/fhir: rarelink.bih-charite.de)
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
ImplementationGuide/rarelink-ig: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
ImplementationGuide.dependsOn[2] (l1/c2565)
warning
The ImplementationGuide uses package hl7.fhir.uv.ips#2.0.0-ballot released on 2024-08-12, but the most recent appropriate version is 2.0.0. This reference is getting old and the more recent version should be consideredIG_DEPENDENCY_VERSION_WARNING_OLD
Review the extension type for age-at-diagnosis: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for age-at-onset: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for birth-place: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for cause-of-death: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for cause-of-death-code: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for cause-of-death-definition: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for causing-agent: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for clinical-modifier-1: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for clinical-modifier-2: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for clinical-modifier-3: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for consanguinity: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for date-of-admission: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for erdri-agreement-to-be-contacted: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for erdri-consent-to-reuse-data: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for phenotype-severity: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for phenotype-status: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for propositus: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Constraint failed: ext-ab-1: 'Additional Bindings SHOULD have a key to allow a binding to be constrained. (extension.where(url='key').exists())'http://hl7.org/fhir/tools/StructureDefinition/additional-binding#ext-ab-1
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex'MSG_DEPENDS_ON_DEPRECATED_NOTE
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding' to 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/bodySite'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/bodySite' to 'http://hl7.org/fhir/StructureDefinition/bodySite|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact' to 'http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. 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 '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#6.0.2), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0092' to 'http://terminology.hl7.org/ValueSet/v2-0092|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding' to 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/bodySite'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/bodySite' to 'http://hl7.org/fhir/StructureDefinition/bodySite|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
Constraint failed: ext-ab-1: 'Additional Bindings SHOULD have a key to allow a binding to be constrained. (extension.where(url='key').exists())'http://hl7.org/fhir/tools/StructureDefinition/additional-binding#ext-ab-1
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
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
--
StructureDefinition.snapshot (l1/c259539)
warning
The slice 'observationText' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c259539)
warning
The slice 'observationCode' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c259539)
warning
The slice 'numericQuantityMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c259539)
warning
The slice 'numericRangeMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c259539)
warning
The slice 'numericRatioMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c259539)
warning
The slice 'numericSampledDataMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
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
--
StructureDefinition.snapshot (l1/c285152)
warning
The slice 'observationText' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c285152)
warning
The slice 'observationCode' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c285152)
warning
The slice 'numericQuantityMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c285152)
warning
The slice 'numericRangeMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c285152)
warning
The slice 'numericRatioMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c285152)
warning
The slice 'numericSampledDataMeasurement' on path 'Observation.component' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
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
A definition could not be found for Canonical URL 'https://hl7.org/fhir/R4/codesystem-observation-category.html' but a definition can be found for 'http://hl7.org/fhir/R4/codesystem-observation-category.html' - change from https: to http:TYPE_SPECIFIC_CHECKS_DT_URL_WRONG_HTTPS
A definition could not be found for Canonical URL 'https://hl7.org/fhir/R4/codesystem-observation-category.html' but a definition can be found for 'http://hl7.org/fhir/R4/codesystem-observation-category.html' - change from https: to http:TYPE_SPECIFIC_CHECKS_DT_URL_WRONG_HTTPS
Review the extension type for recorded-sex-at-birth: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for resolution-date: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for temporal-pattern: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for vital-status: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Wrong Display Name 'Prenatal' for http://snomed.info/sct#118189007. Valid display is one of 2 choices: 'Prenatal finding' (en) or 'Prenatal finding (finding)' (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
--
ValueSet (l1/c1830)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Wrong Display Name 'Prenatal' for http://snomed.info/sct#118189007. Valid display is one of 2 choices: 'Prenatal finding' (en) or 'Prenatal finding (finding)' (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
--
ValueSet (l1/c1798)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
The concepts in the value set include have not been validated because the code system 'http://purl.obolibrary.org/obo/hp.owl' is not known, and no terminology service supports itVALUESET_INC_CS_NO_SUPPORT
--
ValueSet (l1/c2552)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
The concepts in the value set include have not been validated because the code system 'http://hl7.org/fhir/R4' is not known, and no terminology service supports itVALUESET_INC_CS_NO_SUPPORT
A definition for CodeSystem 'http://github.com/BIH-CEI/RareLink' could not be found, so the code cannot be validatedA definition for CodeSystem 'http://github.com/BIH-CEI/RareLink' could not be found, so the code cannot be validated
--
ValueSet (l1/c2889)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
ValueSet.where(id = 'encounter-class-vs')
warning
Error from https://tx.fhir.org/r4: Error: A definition for CodeSystem 'http://hl7.org/fhir/R4' could not be found, so the value set cannot be expanded (from server, see log)
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Wrong Display Name 'XX' for http://snomed.info/sct#734875008. Valid display is one of 2 choices: 'Karyotype 46, XX (cell structure)' (en) or 'Karyotype 46, XX' (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 'XY' for http://snomed.info/sct#734876009. Valid display is one of 2 choices: 'Karyotype 46, XY (cell structure)' (en) or 'Karyotype 46, XY' (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 'X0' for http://snomed.info/sct#80427008. Valid display is one of 2 choices: 'X0 sex chromosome alteration' (en) or 'X0 sex chromosome alteration (morphologic abnormality)' (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 'XXY' for http://snomed.info/sct#65162001. Valid display is one of 2 choices: 'XXY sex chromosome alteration' (en) or 'XXY sex chromosome alteration (morphologic abnormality)' (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 'XXX' for http://snomed.info/sct#35111009. Valid display is one of 5 choices: 'Trisomy X syndrome' (en), 'XXX syndrome' (en), 'Trisomy X syndrome (disorder)' (en), 'Triple X female' (en) or 'Karyotype 47, XXX' (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 'XXYY' for http://snomed.info/sct#403760006. Valid display is one of 2 choices: 'XXYY syndrome (disorder)' (en) or 'XXYY syndrome' (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 'XXXY' for http://snomed.info/sct#78317008. Valid display is one of 2 choices: 'XXXY syndrome' (en) or 'XXXY syndrome (disorder)' (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 'XXXX' for http://snomed.info/sct#10567003. Valid display is one of 4 choices: 'Four X syndrome' (en), 'XXXX syndrome' (en), 'Tetrasomy X' (en) or 'Four X syndrome (disorder)' (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 'XYY' for http://snomed.info/sct#48930007. Valid display is one of 2 choices: 'XYY sex chromosome alteration' (en) or 'XYY sex chromosome alteration (morphologic abnormality)' (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
--
ValueSet (l1/c2656)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
The concepts in the value set include have not been validated because the code system 'http://purl.obolibrary.org/obo/hp.owl' is not known, and no terminology service supports itVALUESET_INC_CS_NO_SUPPORT
--
ValueSet (l1/c1756)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Wrong Display Name 'NCBI Build 34 (hg16)' for http://loinc.org#LA14032-9. Valid display is 'NCBI Build 34' (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
Wrong Display Name 'GRCh37 (hg19)' for http://loinc.org#LA14029-5. Valid display is 'GRCh37' (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
Wrong Display Name 'NCBI Build 36.1 (hg18)' for http://loinc.org#LA14030-3. Valid display is 'NCBI Build 36.1' (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
Wrong Display Name 'NCBI Build 35 (hg17)' for http://loinc.org#LA14031-1. Valid display is 'NCBI Build 35' (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
Wrong Display Name 'GRCh38 (hg38)' for http://loinc.org#LA26806-2. Valid display is 'GRCh38' (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
--
ValueSet (l1/c2062)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
'Moderate' is no longer considered a correct display for code '6736007' (status = inactive). The correct display is one of Midgrade,Moderate (severity modifier) (qualifier value),Moderate (severity modifier),Moderate severity (from https://tx.fhir.org/r4, see log) INACTIVE_DISPLAY_FOUND
--
ValueSet (l1/c1646)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
The concepts in the value set include have not been validated because the code system 'http://purl.obolibrary.org/obo/hp.owl' is not known, and no terminology service supports itVALUESET_INC_CS_NO_SUPPORT
--
ValueSet (l1/c2039)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
A definition for CodeSystem 'http://www.orpha.net/ORDO' could not be found, so the code cannot be validatedA definition for CodeSystem 'http://www.orpha.net/ORDO' could not be found, so the code cannot be validated
Wrong Display Name 'A Rare Disease was diagnosed' 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, 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
--
ValueSet (l1/c2189)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
--
ValueSet.where(id = 'undiagnosed-rd-case-vs')
warning
Error from https://tx.fhir.org/r4: Error: A definition for CodeSystem 'http://www.orpha.net/ORDO' could not be found, so the value set cannot be expanded (from server, see log)
Wrong Display Name 'Unknown - Lost in follow-up' for http://snomed.info/sct#399307001. Valid display is one of 2 choices: 'Lost to follow-up (finding)' (en) or 'Lost to follow-up' (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 'Unknown - Opted-out' for http://snomed.info/sct#185924006. Valid display is one of 2 choices: 'Patient withdrawn from trial' (en) or 'Patient withdrawn from trial (finding)' (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 'Unknown - Other Reason' for http://snomed.info/sct#261665006. Valid display is one of 2 choices: 'Unknown' (en) or 'Unknown (qualifier value)' (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
--
ValueSet (l1/c2048)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Wrong Display Name '(simple) Heterozygous' for http://loinc.org#LA6706-1. Valid display is 'Heterozygous' (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
--
ValueSet (l1/c2254)
warning
Published value sets SHOULD conform to the ShareableValueSet profile, which says that the element ValueSet.experimental is mandatory, but it is not present
Have verified that these examples are being checked against the expected profiles/resources.
INFORMATION: Binary/example: Binary: Validate resource against profile http://hl7.org/fhir/StructureDefinition/Binary (0 uses)
INFORMATION: Bundle/h1: Bundle.entry[0].resource.ofType(Provenance): Validate resource against profile http://hl7.org/fhir/StructureDefinition/Provenance (0 uses)
INFORMATION: Bundle/h1: Bundle: Validate resource against profile http://hl7.org/fhir/StructureDefinition/Bundle (0 uses)
INFORMATION: Patient/example: Patient: Validate resource against profile http://somewhere.org/fhir/uv/myig/StructureDefinition/mypatient (0 uses)
If this was a real IG, there should be examples for these profiles too. But it's not, and I'm lazy...
WARNING: StructureDefinition.where(url = 'http://somewhere.org/fhir/uv/myig/StructureDefinition/myObservation'): The Implementation Guide contains no examples for this profile (0 uses)
WARNING: StructureDefinition.where(url = 'http://somewhere.org/fhir/uv/myig/StructureDefinition/mypractitioner'): The Implementation Guide contains no examples for this profile (0 uses)
The objective is to show a reference to an unknown code system, so these warnings are expected
WARNING: ValueSet.where(id = 'valueset-no-codesystem'): Error from server: Unable to provide support for code system http://not-a-known-code-system (0 uses)
WARNING: ValueSet/valueset-no-codesystem: ValueSet.compose[0].include[0]: Unknown System/Version specified, so Concepts and Filters can''t be checked (0 uses)
These errors are intentional to demonstrate that specifying the canonical URL for value sets in the CQL is expected
ERROR: Library/example: Library.dataRequirement[4].codeFilter[0].valueSet: Canonical URLs must be absolute URLs if they are not fragment references (TBD) (0 uses)
ERROR: Library/example: Library.relatedArtifact[7].resource: Canonical URLs must be absolute URLs if they are not fragment references (TBD) (0 uses)
These examples are fake code systems - they're not expected to be checked
Code System URI 'http://example.org/some-id-type-system' is unknown so the code cannot be validated (0 uses)
Code System URI 'http://example.org/some-system' is unknown so the code cannot be validated (0 uses)
This error is intentional to demonstrate that CQL files not included in a Library resource in the IG are an error:
ERROR: sample-ig\input\cql\notincluded.cql: CQL source was not associated with a library resource in the IG. (0 uses)
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 don't want a code for the change reason (and this binding shouldn't be extensible anyhow)
WARNING: Bundle/h1: Bundle.entry[0].resource.ofType(Provenance).reason[0]: No code provided, and a code should be provided from the value set 'PurposeOfUse' (http://terminology.hl7.org/ValueSet/v3-PurposeOfUse) (0 uses)
WARNING: Bundle/h1: Bundle.entry[0].resource.ofType(Provenance).reason[0]: No code provided, and a code should be provided from the value set 'PurposeOfUse' (http://terminology.hl7.org/ValueSet/v3-PurposeOfUse) (0 uses)
We expect that all of the 'structural' resources will only be validated against their respective 'core' resource definitions
Validate resource against profile http://hl7.org/fhir/StructureDefinition/ImplementationGuide (0 uses)
Validate resource against profile http://hl7.org/fhir/StructureDefinition/Library (0 uses)
Validate resource against profile http://hl7.org/fhir/StructureDefinition/StructureDefinition (0 uses)
Validate resource against profile http://hl7.org/fhir/StructureDefinition/ValueSet (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)
The ImplementationGuide uses package hl7.fhir.uv.ips#2.0.0-ballot released on 2024-08-12, but the most recent appropriate version is 2.0.0. This reference is getting old and the more recent version should be considered
'Moderate' is no longer considered a correct display for code '6736007' (status = inactive). The correct display is one of Midgrade,Moderate (severity modifier) (qualifier value),Moderate (severity modifier),Moderate severity
The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex'
Review the extension type for age-at-diagnosis: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for cause-of-death: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for cause-of-death-code: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for cause-of-death-definition: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for causing-agent: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for clinical-modifier-1: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for clinical-modifier-2: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for clinical-modifier-3: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for consanguinity: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for date-of-admission: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for erdri-agreement-to-be-contacted: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for erdri-consent-to-reuse-data: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for phenotype-severity: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for phenotype-status: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for recorded-sex-at-birth: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for resolution-date: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for temporal-pattern: extensions should not have a context of Element unless it's really intended that they can be used anywhere
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)
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding' to 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/bodySite'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/bodySite' to 'http://hl7.org/fhir/StructureDefinition/bodySite|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact' to 'http://hl7.org/fhir/StructureDefinition/workflow-relatedArtifact|5.2.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. 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 '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#6.0.2), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0092' to 'http://terminology.hl7.org/ValueSet/v2-0092|3.0.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding' to 'http://hl7.org/fhir/StructureDefinition/observation-secondaryFinding|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/bodySite'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/bodySite' to 'http://hl7.org/fhir/StructureDefinition/bodySite|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/data-absent-reason'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/data-absent-reason' to 'http://hl7.org/fhir/StructureDefinition/data-absent-reason|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/translation'. 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.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/translation' to 'http://hl7.org/fhir/StructureDefinition/translation|5.2.0'
A definition could not be found for Canonical URL 'https://hl7.org/fhir/R4/codesystem-observation-category.html' but a definition can be found for 'http://hl7.org/fhir/R4/codesystem-observation-category.html' - change from https: to http:
A definition could not be found for Canonical URL 'https://hl7.org/fhir/R4/codesystem-observation-category.html' but a definition can be found for 'http://hl7.org/fhir/R4/codesystem-observation-category.html' - change from https: to http:
Wrong Display Name 'Prenatal' for http://snomed.info/sct#118189007. Valid display is one of 2 choices: 'Prenatal finding' (en) or 'Prenatal finding (finding)' (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 'Prenatal' for http://snomed.info/sct#118189007. Valid display is one of 2 choices: 'Prenatal finding' (en) or 'Prenatal finding (finding)' (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 'XX' for http://snomed.info/sct#734875008. Valid display is one of 2 choices: 'Karyotype 46, XX (cell structure)' (en) or 'Karyotype 46, XX' (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 'XY' for http://snomed.info/sct#734876009. Valid display is one of 2 choices: 'Karyotype 46, XY (cell structure)' (en) or 'Karyotype 46, XY' (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 'X0' for http://snomed.info/sct#80427008. Valid display is one of 2 choices: 'X0 sex chromosome alteration' (en) or 'X0 sex chromosome alteration (morphologic abnormality)' (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 'XXY' for http://snomed.info/sct#65162001. Valid display is one of 2 choices: 'XXY sex chromosome alteration' (en) or 'XXY sex chromosome alteration (morphologic abnormality)' (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 'XXX' for http://snomed.info/sct#35111009. Valid display is one of 5 choices: 'Trisomy X syndrome' (en), 'XXX syndrome' (en), 'Trisomy X syndrome (disorder)' (en), 'Triple X female' (en) or 'Karyotype 47, XXX' (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 'XXYY' for http://snomed.info/sct#403760006. Valid display is one of 2 choices: 'XXYY syndrome (disorder)' (en) or 'XXYY syndrome' (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 'XXXY' for http://snomed.info/sct#78317008. Valid display is one of 2 choices: 'XXXY syndrome' (en) or 'XXXY syndrome (disorder)' (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 'XXXX' for http://snomed.info/sct#10567003. Valid display is one of 4 choices: 'Four X syndrome' (en), 'XXXX syndrome' (en), 'Tetrasomy X' (en) or 'Four X syndrome (disorder)' (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 'XYY' for http://snomed.info/sct#48930007. Valid display is one of 2 choices: 'XYY sex chromosome alteration' (en) or 'XYY sex chromosome alteration (morphologic abnormality)' (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 'NCBI Build 34 (hg16)' for http://loinc.org#LA14032-9. Valid display is 'NCBI Build 34' (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 'GRCh37 (hg19)' for http://loinc.org#LA14029-5. Valid display is 'GRCh37' (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 'NCBI Build 36.1 (hg18)' for http://loinc.org#LA14030-3. Valid display is 'NCBI Build 36.1' (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 'NCBI Build 35 (hg17)' for http://loinc.org#LA14031-1. Valid display is 'NCBI Build 35' (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 'GRCh38 (hg38)' for http://loinc.org#LA26806-2. Valid display is 'GRCh38' (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 'A Rare Disease was diagnosed' 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, 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 'Unknown - Lost in follow-up' for http://snomed.info/sct#399307001. Valid display is one of 2 choices: 'Lost to follow-up (finding)' (en) or 'Lost to follow-up' (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 'Unknown - Opted-out' for http://snomed.info/sct#185924006. Valid display is one of 2 choices: 'Patient withdrawn from trial' (en) or 'Patient withdrawn from trial (finding)' (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 'Unknown - Other Reason' for http://snomed.info/sct#261665006. Valid display is one of 2 choices: 'Unknown' (en) or 'Unknown (qualifier value)' (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 '(simple) Heterozygous' for http://loinc.org#LA6706-1. Valid display is 'Heterozygous' (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
The concepts in the value set include have not been validated because the code system 'http://purl.obolibrary.org/obo/hp.owl' is not known, and no terminology service supports it
The concepts in the value set include have not been validated because the code system 'http://hl7.org/fhir/R4' is not known, and no terminology service supports it
The concepts in the value set include have not been validated because the code system 'http://purl.obolibrary.org/obo/hp.owl' is not known, and no terminology service supports it
The concepts in the value set include have not been validated because the code system 'http://purl.obolibrary.org/obo/hp.owl' is not known, and no terminology service supports it
rarelink-ig
hl7.fhir.uv.tools.r4