Validation Results for CH_EMED

Generated Thu Mar 28 09:18:31 UTC 2024, FHIR version 4.0.1 for ch.fhir.ig.ch-emed#5.0.0-ci-build (canonical = http://fhir.ch/ig/ch-emed (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.6.3
Publication Code:	n/a . PackageId = ch.fhir.ig.ch-emed, Canonical = http://fhir.ch/ig/ch-emed
Realm Check for n/a:	n/a
Publication Request:	Publication Request is for v'4.0.1' but package version is v5.0.0-ci-build Publication Request is for version v4.0.1 which is already published
Supressed Messages:	14 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment ch.fhir.ig.ch-emed 5.0.0-ci-build R4 http://fhir.ch/ig/ch-emed hl7.fhir.uv.extensions.r4 1.0.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 ch.fhir.ig.ch-core 5.0.0-ci-build V R4 http://fhir.ch/ig/ch-core https://build.fhir.org/ig/ralych/ch-core/ Matched to latest patch release (current->5.0.0-ci-build) hl7.fhir.uv.extensions.r4 1.0.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 see above ch.fhir.ig.ch-term current U R4 http://fhir.ch/ig/ch-term https://build.fhir.org/ig/hl7ch/ch-epr-term/ Cannot be published with a dependency on a current build version hl7.fhir.uv.extensions.r4 1.0.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 see above ihe.formatcode.fhir 1.1.0 O R4 https://profiles.ihe.net/fhir/ihe.formatcode.fhir https://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0 Latest Release is 1.2.0 hl7.terminology 5.4.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.4.0 Latest Release is 5.5.0 hl7.fhir.uv.extensions.r4 1.0.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 see above hl7.terminology 5.4.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.4.0 see above. Latest Release is 5.5.0 hl7.terminology 5.4.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.4.0 see above. Latest Release is 5.5.0 Templates: ch.fhir.ig.template#current -> fhir.base.template#current. Tools: 0.1.0
Dependent IGs:	no references
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4 (details)
HTA Analysis:	Non-HL7 Igs are exempt from terminology dependency analysis
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), Narrative Link (8 uses), bestpractice (24 uses), bestpractice-explanation (24 uses), fhir-type (629 uses), maxValueSet (31 uses), bindingName (611 uses), CommonLanguages (31 uses), Organization (45 uses), CompositionStatus (6 uses), translatable (110 uses), Device (53 uses), RelatedPerson (70 uses), regex (6 uses), CompositionAttestationMode (12 uses), DocumentRelationshipType (6 uses), Composition (72 uses), DocumentSectionCodes (24 uses), ListMode (24 uses), ListOrderCodes (24 uses), ListEmptyReasons (24 uses), SNOMEDCTAdditionalDosageInstructions (3 uses), TimingAbbreviation (3 uses), SNOMEDCTMedicationAsNeededReasonCodes (3 uses), SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (5 uses), DoseAndRateType (3 uses), SNOMEDCTMedicationCodes (12 uses), Medication Status Codes (2 uses), Substance (2 uses), MedicationAdministration (9 uses), Procedure (9 uses), MedicationAdministration Status Codes (2 uses), SNOMEDCTReasonMedicationNotGivenCodes (2 uses), MedicationAdministration Category Codes (2 uses), Encounter (13 uses), EpisodeOfCare (8 uses), MedicationAdministration Performer Function Codes (2 uses), ReasonMedicationGivenCodes (2 uses), Condition (9 uses), DiagnosticReport (6 uses), MedicationRequest (16 uses), Provenance (7 uses), MedicationDispense (7 uses), MedicationDispense Status Codes (2 uses), DetectedIssue (7 uses), MedicationDispense Status Reason Codes (2 uses), MedicationDispense Category Codes (2 uses), MedicationDispense Performer Function Codes (2 uses), Location (4 uses), Practitioner (13 uses), PractitionerRole (11 uses), medicationrequest Status (3 uses), medicationRequest Status Reason Codes (3 uses), medicationRequest Intent (3 uses), medicationRequest Category Codes (3 uses), RequestPriority (3 uses), CareTeam (3 uses), ProcedurePerformerRoleCodes (3 uses), Condition/Problem/DiagnosisCodes (7 uses), CarePlan (9 uses), ServiceRequest (9 uses), ImmunizationRecommendation (5 uses), medicationRequest Course of Therapy Codes (3 uses), Coverage (3 uses), ClaimResponse (3 uses), MedicationStatement (5 uses), Medication Status Codes (4 uses), SNOMEDCTDrugTherapyStatusCodes (4 uses), Medication usage category codes (4 uses), DeviceRequest (2 uses), NutritionOrder (2 uses), Immunization (2 uses), ImagingStudy (4 uses), display-hint (2 uses), ObservationCategoryCodes (2 uses), SNOMEDCTBodyStructures (2 uses), ObservationMethods (2 uses), Specimen (2 uses), DeviceMetric (2 uses), ObservationReferenceRangeMeaningCodes (2 uses), ObservationReferenceRangeAppliesToCodes (2 uses), QuestionnaireResponse (4 uses), MolecularSequence (4 uses), DocumentReference (2 uses), Media (2 uses), LOINCCodes (2 uses), hierarchy (1 uses), ContactEntityType (1 uses), Endpoint (2 uses), HealthcareService (1 uses) hl7.fhir.uv.tools#0.1.0: ResourceSortExt (102 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Comparison with version 4.0.1
IPA Comparison:	n/a
IPS Comparison:	n/a
Summary:	errors = 0, warn = 0, info = 2, broken links = 0

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

All important examples are contained in the IG

• The Implementation Guide contains no examples for this extension (2 uses)
• The Implementation Guide contains no examples for this profile (3 uses)

Build errors

• The image source '2-7-pdf' cannot be resolved (1 uses)
• The link 'Binary/2-6-pdf' for "Representation of the original view" cannot be resolved (1 uses)

External code system

• A definition for CodeSystem 'http://example.com/localcode' could not be found, so the code cannot be validated (1 uses)
• A definition for CodeSystem 'urn:oid:0.4.0.127.0.16.1.1.2.1' could not be found, so the code cannot be validated (93 uses)
• A definition for CodeSystem 'urn:oid:2.51.1.1' could not be found, so the code cannot be validated (37 uses)

Not yet a stable version, which can be published (see https://github.com/hl7ch/ch-epr-term/issues/17)

• None of the codings provided are in the value set 'DocumentEntry.typeCode' (http://fhir.ch/ig/ch-term/ValueSet/DocumentEntry.typeCode|3.0.0-ci-build), and a coding should come from this value set unless it has no suitable code (note that the validator cannot judge what is suitable) (codes = http://loinc.org#56445-0, http://snomed.info/sct#736378000) (3 uses)
• None of the codings provided are in the value set 'DocumentEntry.typeCode' (http://fhir.ch/ig/ch-term/ValueSet/DocumentEntry.typeCode|3.0.0-ci-build), and a coding should come from this value set unless it has no suitable code (note that the validator cannot judge what is suitable) (codes = http://loinc.org#77603-9, http://snomed.info/sct#761931002) (6 uses)
• None of the codings provided are in the value set 'DocumentEntry.typeCode' (http://fhir.ch/ig/ch-term/ValueSet/DocumentEntry.typeCode|3.0.0-ci-build), and a coding should come from this value set unless it has no suitable code (note that the validator cannot judge what is suitable) (codes = http://snomed.info/sct#82291000195104, http://loinc.org#60593-1) (8 uses)

Problem in the base profile

• The string value contains text that looks like embedded HTML tags. If this content is rendered to HTML without appropriate post-processing, it may be a security risk (2 uses)

Swiss specific value

• Der Displayname f\u00fcr http://loinc.org#57828-6 sollte einer von ''Prescription list'' anstelle von 'PRESCRIPTIONS' sein. (1 uses)

Test case for extensible value set binding (parameter = allow-extensible-warnings)

• The code provided (http://snomed.info/sct#408050008) is not in the value set in the value set 'ActivePharmaceuticalIngredient' (http://fhir.ch/ig/ch-term/ValueSet/ActivePharmaceuticalIngredient|3.0.0-ci-build), and a code should come from this value set unless it has no suitable code (the validator cannot judge what is suitable) (1 uses)

Test case for using not recommended timing codes (1-1-1-1)

• Constraint failed: ch-emed-event-timing: 'For the representation of the time of administration according to the 1-1-1-1 scheme, the values MORN-NOON-EVE-NIGHT are highly recommended.' (defined in http://fhir.ch/ig/ch-emed/StructureDefinition/ch-emed-dosage) (2 uses)

Errors sorted by type