Unable to compare with previous version: Unable to find version history at http://johnmoehrke.github.io/phr (Problem #1 with package-list.json at http://johnmoehrke.github.io/phr: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation'. 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.1.0, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation' to 'http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
Canonical URL 'http://fhir.org/packages/hl7.fhir.us.core/ImplementationGuide/hl7.fhir.us.core' does not resolveTYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE
ImplementationGuide.dependsOn[2] (l1/c2324)
warning
The ImplementationGuide uses package hl7.fhir.us.core#5.0.x released on 2022-06-22, but the most recent appropriate version is 7.0.0. This reference is getting old and the more recent version should be consideredIG_DEPENDENCY_VERSION_WARNING_OLD
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType' to 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType|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/condition-assertedDate'. 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, 5.2.0. Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|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/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|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/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, 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 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 regexMSG_DEPENDS_ON_DEPRECATED_NOTE
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, 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://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType' to 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType' to 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|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/event-location'. 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, 5.2.0. Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/event-location' to 'http://hl7.org/fhir/StructureDefinition/event-location|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/event-location'. 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, 5.2.0. Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/event-location' to 'http://hl7.org/fhir/StructureDefinition/event-location|5.2.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/condition-clinical'. 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: 0.5.0, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/condition-clinical' to 'http://terminology.hl7.org/CodeSystem/condition-clinical|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/condition-ver-status'. 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 '2.0.1', found versions: 0.5.0, 2.0.1. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/condition-ver-status' to 'http://terminology.hl7.org/CodeSystem/condition-ver-status|2.0.1'
Unknown code '78990' in the CodeSystem 'http://www.ama-assn.org/go/cpt' version '2023' (0 uses)
AVS Location is rather generic
Reference_REF_MultipleMatches (0 uses)
ChemHem has extra category codes
This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
ChemHem seems to use this version of snomed
A definition for CodeSystem 'http://snomed.info' version '20170901' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://snomed.info' version '20180301' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://snomed.info' version '20180901' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://snomed.info' version '20200731' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://snomed.info' version '20200901' could not be found, so the code cannot be validated% (0 uses)
DiagnosticReport profile is for API use. No data will be marked with this profile
WARNING: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.diagnosticReport'): The Implementation Guide contains no examples for this profile (1 uses)
DocumentReference profile is for API use. No data will be marked with this profile
WARNING: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.documentReference'): The Implementation Guide contains no examples for this profile (1 uses)
I am not using #pattern slicing, but the us-core that I am depending on does
INFORMATION: StructureDefinition/JFM.PHR.MBlabReport: StructureDefinition.snapshot.element[36].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.SPlabReport: StructureDefinition.snapshot.element[36].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.avs: StructureDefinition.snapshot.element[60].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.chOrder: StructureDefinition.snapshot.element[17].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.chReport: StructureDefinition.snapshot.element[31].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.chTest: StructureDefinition.snapshot.element[13].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.condition: StructureDefinition.snapshot.element[22].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.diagnosticReport: StructureDefinition.snapshot.element[12].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.documentReference: StructureDefinition.snapshot.element[26].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.ecg: StructureDefinition.snapshot.element[35].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.imaging: StructureDefinition.snapshot.element[39].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.irOrder: StructureDefinition.snapshot.element[17].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.labTest: StructureDefinition.snapshot.element[22].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.note: StructureDefinition.snapshot.element[35].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.organization: StructureDefinition.snapshot.element[9].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.studyReport: StructureDefinition.snapshot.element[30].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.vitalsBP: StructureDefinition.snapshot.element[78].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.vitalsOx: StructureDefinition.snapshot.element[38].slicing.discriminator[0]: 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) (1 uses)
INFORMATION: StructureDefinition/JFM.PHR.vitalsOx: StructureDefinition.snapshot.element[80].slicing.discriminator[0]: 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) (1 uses)
Observation interpretation code translation has no source
WARNING: ConceptMap/VF-ChemistryResult-valueInterpretation: ConceptMap.group[0]: No Source Code System, so the source codes cannot be checked (1 uses)
Organization has an odd info coming from us-core
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (6 uses)
Organization, Practitioner, and Location are now contained, so there is no examples formally recognized by validator
The Implementation Guide contains no explicitly linked examples for this profile (0 uses)
Pathology codes don't have a system
WARNING: ConceptMap/SPTypeCM: ConceptMap.group[0]: No Source Code System, so the source codes cannot be checked (1 uses)
Patient-0 is fully populated, therefore uses extensions beyond us-core
INFORMATION: Patient/ex-VIA-patient-0: Patient.extension[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient|5.0.1 (0 uses)
INFORMATION: Patient/ex-VIA-patient-0: Patient.extension[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient|5.0.1 (0 uses)
Search disabling starts with FHIR core, which has the problem
Constraint failed: spd-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation' (95 uses)
The CH tests, panel, and specimen are contained
INFORMATION: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chOrder'): The Implementation Guide contains no explicitly linked examples for this profile (0 uses)
INFORMATION: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chSpecimen'): The Implementation Guide contains no explicitly linked examples for this profile (0 uses)
INFORMATION: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chTest'): The Implementation Guide contains no explicitly linked examples for this profile (0 uses)
The Lab test and specimen are contained
INFORMATION: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.LabSpecimen'): The Implementation Guide contains no explicitly linked examples for this profile (0 uses)
INFORMATION: StructureDefinition.where(url = 'http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.labTest'): The Implementation Guide contains no explicitly linked examples for this profile (0 uses)
There is no source for these codes from Vista for status
WARNING: ConceptMap/VF-ChemistryResult-ObservationStatus: ConceptMap.group[0]: No Source Code System, so the source codes cannot be checked (1 uses)
US-Core Practitioner requires an identifier, and allows anything. But that doesn't match the NPI slice
INFORMATION: DiagnosticReport/ex-MHV-imaging-0: DiagnosticReport.contained[1]/*Practitioner/ex-MHV-practitioner-image0*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/ex-MHV-labReport-1: DiagnosticReport.contained[3]/*Practitioner/ex-MHV-practitioner-mangas*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/ex-MHV-labReport-2: DiagnosticReport.contained[5]/*Practitioner/ex-MHV-practitioner-mangas*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/ex-MHV-labReport-3: DiagnosticReport.contained[5]/*Practitioner/ex-MHV-practitioner-mangas*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/ex-MHV-labReport-4: DiagnosticReport.contained[2]/*Practitioner/ex-MHV-practitioner-seetha*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/ex-MHV-labReport-6: DiagnosticReport.contained[2]/*Practitioner/ex-MHV-practitioner-seetha*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/ex-MHV-labReport-8: DiagnosticReport.contained[2]/*Practitioner/ex-MHV-practitioner-seetha*/.identifier[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|5.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
VA codeSystem
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/60' could not be found, so the code cannot be validated (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/61' version '5.2' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/64' could not be found, so the code cannot be validated (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.14' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.52' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.61' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.63' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.64' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.65' could not be found, so the code cannot be validated% (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' version '2.68' could not be found, so the code cannot be validated% (0 uses)
Vital-Sign concepts are mapped from VUID
A definition for CodeSystem 'urn:oid:2.16.840.1.113883.6.233' could not be found, so the code cannot be validated (0 uses)
The Source Code System urn:oid:2.16.840.1.113883.6.233 is not fully defined and populated, and no sourceScope is specified, so the source code checking will not be performed (8 uses)
example Chem-Hem has extra codes outside the slices defined by us-core
INFORMATION: DiagnosticReport/9952: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9953: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9954: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9955: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9956: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9957: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9958: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9959: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9960: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9961: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9962: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9963: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9964: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9965: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9966: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9966: DiagnosticReport.category[3]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9967: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9968: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9969: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9969: DiagnosticReport.category[3]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9970: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9971: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9972: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9973: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9974: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9975: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9976: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9977: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9978: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9979: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9980: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9981: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9982: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9983: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9984: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9985: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9986: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9987: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
INFORMATION: DiagnosticReport/9988: DiagnosticReport.category[2]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.chReport|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
explicitly no examples
The Implementation Guide contains no examples for this extension (3 uses)
The Implementation Guide contains no examples for this profile (25 uses)
imaging report has some okay info
This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.organization|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
info messages when using draft resources, like valueSets from THO
MSG_DRAFT (0 uses)
not all ends of the concept maps are available
CONCEPTMAP_GROUP_TARGET_INCOMPLETE (2 uses)
observation-deviceCode has been retired, but we still use it - http://jira.hl7.org/browse/FHIR-46838
INFORMATION: Observation/ex-MHV-oximetry-1: Observation.extension[0]: The extension http://hl7.org/fhir/StructureDefinition/observation-deviceCode|5.1.0 is retired (0 uses)
stand in system for assigning authority short
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/61' could not be found, so the code cannot be validated (0 uses)
A definition for CodeSystem 'http://va.gov/terminology/vistaDefinedTerms/95.3' could not be found, so the code cannot be validated (0 uses)
the pain example also includes the original code (VUID)
INFORMATION: Observation/ex-MHV-pain-1: Observation.code.coding[1]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.vitalsPain|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
unclear why not but I don't care
Target Code System http://loinc.org is only supported on the terminology server, so the target codes are not validated for performance reasons (2 uses)
Target Code System http://snomed.info/sct is only supported on the terminology server, so the target codes are not validated for performance reasons (5 uses)
validator presumes latest icd-9, we don't have a version, so it looks like we are using a non-found code when it is just one that has been removed
WARNING: Condition/0635f0d9-81ab-4a0b-af8d-f899d8e5220d: Condition.code.coding[0].code: Unknown Code '414.00' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/2b2d8b23-439d-4d5c-967e-b080b2710dd9: Condition.code.coding[0].code: Unknown Code '799.9' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/36a44c53-cb2a-45a3-a932-a295ac7d52c7: Condition.code.coding[0].code: Unknown Code '401.9' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/397ef2d8-7516-4fdb-aef4-ae74b53dd202: Condition.code.coding[0].code: Unknown Code '300.00' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/6ba7a74c-b635-4593-bcb7-735f009aaf88: Condition.code.coding[0].code: Unknown Code '424.90' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/74976867-7782-4e26-90af-2e576be9bb44: Condition.code.coding[0].code: Unknown Code '365.9' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/7e55cbc8-4864-462d-a730-98ca4cccd4a2: Condition.code.coding[0].code: Unknown Code '724.2' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/7f88a60c-ffe5-4001-8286-c5eeccc069dd: Condition.code.coding[0].code: Unknown Code '333.99' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/a7471138-f4ac-4226-9555-4999196c6136: Condition.code.coding[0].code: Unknown Code '600.00' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/c02cc828-7fd0-40a7-a2fb-5b4609f825a7: Condition.code.coding[0].code: Unknown Code 'V79.8' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/ca55b358-f98a-4ba0-a3dc-0346cbeaf44d: Condition.code.coding[0].code: Unknown Code 'V79.1' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
WARNING: Condition/ex-MHV-condition-deleted-487: Condition.code.coding[0].code: Unknown Code '401.9' in the CodeSystem 'http://hl7.org/fhir/sid/icd-9-cm' version '2015' - note that the code system is labeled as a fragment, so the code may be valid in some other fragment (0 uses)
vitals can have .component that carry vista qualifiers. The following are confirmed to be legitimate
INFORMATION: Observation/ex-MHV-oximetry-1: Observation.component[0]: This element does not match any known slice defined in the profile http://johnmoehrke.github.io/phr/StructureDefinition/JFM.PHR.vitalsOx|0.5.2 (this may not be a problem, but you should check that it's not intended to match a slice) (0 uses)
The ImplementationGuide uses package hl7.fhir.us.core#5.0.x released on 2022-06-22, but the most recent appropriate version is 7.0.0. This reference is getting old and the more recent version should be considered
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
There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation'. 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.1.0, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation' to 'http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType' to 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType|3.0.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'. 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, 5.2.0. Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|5.2.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.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, 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, 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://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType' to 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType' to 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActCode'. 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, 3.0.0. Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-ActCode' to 'http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/event-location'. 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, 5.2.0. Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/event-location' to 'http://hl7.org/fhir/StructureDefinition/event-location|5.2.0'
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/event-location'. 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, 5.2.0. Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/event-location' to 'http://hl7.org/fhir/StructureDefinition/event-location|5.2.0'
johnmoehrke.phr
hl7.fhir.r4.examples