Unable to compare with previous version: Unable to find version history at http://jpfhir.jp/fhir/core (Problem #1 with package-list.json at http://jpfhir.jp/fhir/core: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad, displayWarnings; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent
CodeSystem/jp-observation-bodymeasurement-category-cs: CodeSystem: Validated against
Path
Severity
Message
CodeSystem.valueSet (l1/c1055)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCategory_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
CodeSystem/jp-observation-bodymeasurement-code-cs: CodeSystem: Validated against
Path
Severity
Message
CodeSystem.valueSet (l1/c1042)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
DiagnosticReport/jp-diagnosticreport-labresult-example-1: DiagnosticReport: Validated against
DiagnosticReport/jp-diagnosticreport-labresult-example-1: DiagnosticReport.contained[0]/*Observation/inner-observation-labresult-1*/: Validated against
DiagnosticReport/jp-diagnosticreport-labresult-example-1: DiagnosticReport.contained[1]/*Observation/inner-observation-labresult-2*/: Validated against
DiagnosticReport/jp-diagnosticreport-labresult-example-1: DiagnosticReport.contained[2]/*Observation/inner-observation-labresult-3*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[0]/*Observation/gram-strain1*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[1]/*Observation/gram-strain2*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[2]/*Observation/gram-strain3*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[3]/*Observation/gram-strain4*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[4]/*Observation/organism-panels1*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[5]/*Observation/organism-panels2*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[6]/*Observation/organism-panels3*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[7]/*Observation/organism-panels4*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[8]/*Observation/organism-id1*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[9]/*Observation/organism-id2*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[10]/*Observation/organism-id3*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[11]/*Observation/organism-id4*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[12]/*Observation/susceptibility-panels1*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[13]/*Observation/susceptibility-panels2*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[14]/*Observation/susceptibility-measurements1-1*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[15]/*Observation/susceptibility-measurements1-2*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[16]/*Observation/susceptibility-measurements1-3*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[17]/*Observation/susceptibility-measurements1-4*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[18]/*Observation/susceptibility-measurements1-5*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[19]/*Observation/susceptibility-measurements1-6*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[20]/*Observation/susceptibility-measurements1-7*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[21]/*Observation/susceptibility-measurements2-1*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[22]/*Observation/susceptibility-measurements2-2*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[23]/*Observation/susceptibility-measurements2-3*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[24]/*Observation/susceptibility-measurements2-4*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[25]/*Observation/susceptibility-measurements2-5*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[26]/*Observation/susceptibility-measurements2-6*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[27]/*Observation/susceptibility-measurements2-7*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[28]/*Observation/susceptibility-measurements2-8*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[29]/*Observation/susceptibility-measurements2-9*/: Validated against
DiagnosticReport/jp-diagnosticreport-microbiology-example-1: DiagnosticReport.contained[30]/*ServiceRequest/jp-servicerequest-example-1*/: Validated against
MedicationAdministration.contained[0]: Validated against
MedicationAdministration.contained[1]: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-1: MedicationAdministration: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-1: MedicationAdministration.contained[0]/*Medication/jp-medicationadministration-injection-medication-example-1*/: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-1: MedicationAdministration.contained[1]/*BodyStructure/jp-medicationadministration-injection-bodystructure-example-1*/: Validated against
MedicationAdministration.contained[0]: Validated against
MedicationAdministration.contained[1]: Validated against
MedicationAdministration.contained[2]: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-2: MedicationAdministration: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-2: MedicationAdministration.contained[0]/*Medication/jp-medicationadministration-injection-medication-example-2*/: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-2: MedicationAdministration.contained[1]/*BodyStructure/jp-medicationadministration-injection-bodystructure-example-2*/: Validated against
MedicationAdministration/jp-medicationadministration-injection-example-2: MedicationAdministration.contained[2]/*Device/jp-medicationadministration-injection-device-example-2*/: Validated against
'generic composition' is the default display; the code system http://terminology.hl7.org/CodeSystem/v3-substanceAdminSubstitution has no Display Names found for the language ja
'regulatory requirement' is the default display; the code system http://terminology.hl7.org/CodeSystem/v3-ActReason has no Display Names found for the language ja
MedicationDispense.contained[0]: Validated against
MedicationDispense.contained[1]: Validated against
MedicationDispense/jp-medicationdispense-injection-example-1: MedicationDispense: Validated against
MedicationDispense/jp-medicationdispense-injection-example-1: MedicationDispense.contained[0]/*Medication/jp-medicationdispense-injection-medication-example-1*/: Validated against
MedicationDispense/jp-medicationdispense-injection-example-1: MedicationDispense.contained[1]/*BodyStructure/jp-medicationdispense-injection-bodystructure-example-1*/: Validated against
MedicationRequest/jp-medicationrequest-injection-example-1: MedicationRequest: Validated against
MedicationRequest/jp-medicationrequest-injection-example-1: MedicationRequest.contained[0]/*Medication/jp-medicationrequest-injection-medication-example-1*/: Validated against
MedicationRequest/jp-medicationrequest-injection-example-1: MedicationRequest.contained[1]/*BodyStructure/jp-medicationrequest-injection-bodystructure-example-1*/: Validated against
MedicationRequest/jp-medicationrequest-injection-example-2: MedicationRequest: Validated against
MedicationRequest/jp-medicationrequest-injection-example-2: MedicationRequest.contained[0]/*Medication/jp-medicationrequest-injection-medication-example-2*/: Validated against
MedicationRequest/jp-medicationrequest-injection-example-2: MedicationRequest.contained[1]/*BodyStructure/jp-medicationrequest-injection-bodystructure-example-2*/: Validated against
MedicationRequest/jp-medicationrequest-injection-example-2: MedicationRequest.contained[2]/*Device/jp-medicationrequest-injection-device-example-2*/: Validated against
MedicationStatement.contained[0]: Validated against
MedicationStatement.contained[1]: Validated against
MedicationStatement.contained[2]: Validated against
MedicationStatement/jp-medicationstatement-injection-example-1: MedicationStatement: Validated against
MedicationStatement/jp-medicationstatement-injection-example-1: MedicationStatement.contained[0]/*Medication/jp-medicationstatement-injection-medication-example-1*/: Validated against
MedicationStatement/jp-medicationstatement-injection-example-1: MedicationStatement.contained[1]/*BodyStructure/jp-medicationstatement-injection-bodystructure-example-1*/: Validated against
MedicationStatement/jp-medicationstatement-injection-example-1: MedicationStatement.contained[2]/*Device/jp-medicationstatement-injection-device-example-1*/: Validated against
'Shinto' is the default display; the code system http://terminology.hl7.org/CodeSystem/v3-ReligiousAffiliation has no Display Names found for the language ja
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeHL70241_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeJHSD0006_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeHL70241_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeJHSD0006_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse'. 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. Using version '3.1.0', found versions: 2014-03-26, 3.1.0TYPE_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. Using version '3.0.0', found versions: 2018-08-12, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPriority'. 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. Using version '3.0.0', found versions: 2018-08-12, 3.0.0TYPE_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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-FamilyMember'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/iso21090-EN-representation'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/iso21090-EN-representation'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCategory_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCategory_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0136'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0136'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-devTYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-religion'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-religion'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-Race'. 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. Using version '3.0.0', found versions: 2018-08-12, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-Race'. 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. Using version '3.0.0', found versions: 2018-08-12, 3.0.0TYPE_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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0487'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0916'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0371'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0493'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0487'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0916'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0371'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0493'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
ValueSet/jp-condition-disease-outcome-hl70241-jhsd0006-vs: ValueSet: Validated against
Path
Severity
Message
ValueSet.compose.include[0] (l1/c1924)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/CodeSystem/HL70241'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
ValueSet.compose.include[1] (l1/c1984)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/CodeSystem/JHSD0006'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
ValueSet/jp-condition-disease-outcome-hl70241-vs: ValueSet: Validated against
Path
Severity
Message
ValueSet.compose.include[0] (l1/c1499)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/CodeSystem/HL70241'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
ValueSet/jp-condition-disease-outcome-jhsd0006-vs: ValueSet: Validated against
Path
Severity
Message
ValueSet.compose.include[0] (l1/c1581)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/CodeSystem/JHSD0006'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
ValueSet/jp-observation-bodymeasurement-category-vs: ValueSet: Validated against
Path
Severity
Message
ValueSet.compose.include[0] (l1/c1612)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/CodeSystem/JP_ObservationBodyMeasurementCategory_CS'. 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. Using version '1.3.0-dev', found versions: 1.1.0a, 1.3.0-dev
ValueSet/jp-observation-bodymeasurement-code-vs: ValueSet: Validated against
Path
Severity
Message
ValueSet.compose.include[0] (l1/c1566)
warning
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/CodeSystem/JP_ObservationBodyMeasurementCode_CS'. 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. Using version '1.3.0-dev', found versions: 1.1.0a, 1.3.0-dev
The definition for the element 'Consent.provision.code' binds to the value set 'http://hl7.org/fhir/ValueSet/consent-content-code' which is experimental, but this structure is not labeled as experimental (0 uses)
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCategory_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeHL70241_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeJHSD0006_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeHL70241_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ConditionDiseaseOutcomeJHSD0006_VS'. 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. Using version '1.3.0-dev', found versions: 1.0.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse'. 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. Using version '3.1.0', found versions: 2014-03-26, 3.1.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. Using version '3.0.0', found versions: 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActEncounterCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPriority'. 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. Using version '3.0.0', found versions: 2018-08-12, 3.0.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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-FamilyMember'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/iso21090-EN-representation'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/iso21090-EN-representation'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
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. Using version '3.0.0', found versions: 2014-03-26, 3.0.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. Using version '5.2.0', found versions: 4.0.1, 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActPharmacySupplyType'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-ActSubstanceAdminSubstitutionCode'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.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. Using version '5.2.0', found versions: 4.0.1, 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-SubstanceAdminSubstitutionReason'. 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCategory_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCategory_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_ObservationBodyMeasurementCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0136'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0136'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://jpfhir.jp/fhir/core/ValueSet/JP_PhysicalExamCode_VS'. 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. Using version '1.3.0-dev', found versions: 1.1.0, 1.3.0-dev
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-religion'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-religion'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/patient-birthPlace'. 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. Using version '5.2.0', found versions: 4.0.1, 5.2.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-Race'. 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. Using version '3.0.0', found versions: 2018-08-12, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-Race'. 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. Using version '3.0.0', found versions: 2018-08-12, 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. Using version '3.0.0', found versions: 2014-03-26, 3.0.0
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0487'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0916'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0371'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0493'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0487'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0916'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0371'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0493'. 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. Using version '2.0.0', found versions: 2.0.0, 2.9