Validation Results for CH_EMED

Generated Tue Dec 19 15:49:06 CET 2023, FHIR version 4.0.1 for ch.fhir.ig.ch-emed#4.0.0 (canonical = http://fhir.ch/ig/ch-emed (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.5.8
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:	package-id ch.fhir.ig.ch-emed version 4.0.0 path http://fhir.ch/ig/ch-emed/4.0.0 Pub-Mode milestone status trial-use sequence STU 4 desc HL7 Switzerland STU 4 changes changelog.html No Messages found - all good
Supressed Messages:	14 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment ch.fhir.ig.ch-emed 4.0.0 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 4.0.0 M R4 http://fhir.ch/ig/ch-core file:///home/michaela/github/ch-core/output 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-epr-term 2.0.10 M R4 http://fhir.ch/ig/ch-epr-term http://fhir.ch/ig/ch-epr-term/2.0.10 Matched to latest patch release (2.0.x->2.0.10) 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 M R4 https://profiles.ihe.net/fhir/ihe.formatcode.fhir https://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0 hl7.terminology 5.4.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/5.4.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 M R4 http://terminology.hl7.org http://terminology.hl7.org/5.4.0 see above ch.fhir.ig.ch-epr-term 2.0.10 M R4 http://fhir.ch/ig/ch-epr-term http://fhir.ch/ig/ch-epr-term/2.0.10 see above hl7.terminology 5.4.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/5.4.0 see above Templates: ch.fhir.ig.template#current -> fhir.base.template#current. Tools: current
Dependent IGs:	no references
Global Profiles:	(none declared)
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 (93 uses), bestpractice-explanation (93 uses), fhir-type (626 uses), maxValueSet (31 uses), bindingName (618 uses), CommonLanguages (31 uses), Organization (51 uses), CompositionStatus (6 uses), translatable (103 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), MedicationDispense (10 uses), SNOMEDCTAdditionalDosageInstructions (3 uses), Dosage (29 uses), TimingAbbreviation (3 uses), SNOMEDCTMedicationAsNeededReasonCodes (3 uses), SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (5 uses), SNOMEDCTAdministrationMethodCodes (5 uses), DoseAndRateType (3 uses), SNOMEDCTRouteCodes (1 uses), SNOMEDCTMedicationCodes (12 uses), Medication Status Codes (2 uses), Substance (2 uses), Medication (13 uses), MedicationAdministration (10 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 (17 uses), Provenance (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 (6 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), Shareable ValueSet (5 uses), effectivePeriod (5 uses), concept-comments (514 uses) hl7.fhir.uv.tools#1.0.0-candidate: ResourceSortExt (116 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Comparison with version 4.0.0-ballot
IPA Comparison:	n/a
IPS Comparison:	n/a
Summary:	errors = 0, warn = 4, info = 575, broken links = 0

n/a Show Validation Information

fsh-generated/resources/Medication-TriatecWithCodeNotFromVS.json Show Validation Information (1)

fsh-generated/resources/MedicationStatement-NotRecommendedTimingCodes.json Show Validation Information (6)

fsh-generated/resources/StructureDefinition-ch-emed-medicationadministration-list.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

All important examples are contained in the IG

• The Implementation Guide contains no examples for this extension (4 uses)
• WARNING: StructureDefinition.where(url = 'http://fhir.ch/ig/ch-emed/StructureDefinition/ch-emed-medicationrequest-list'): The Implementation Guide contains no examples for this profile (1 uses)
• WARNING: StructureDefinition.where(url = 'http://fhir.ch/ig/ch-emed/StructureDefinition/ch-emed-observation-list'): The Implementation Guide contains no examples for this profile (1 uses)
• WARNING: StructureDefinition​.where(url = 'http:​/​/fhir​.ch​/ig​/ch-emed​/StructureDefinition​/ch-emed-medicationadministration-list'): The Implementation Guide contains no examples for this profile (0 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)

Fixed with next release: https://github.com/hl7ch/ch-emed/issues/252

• UCUM Codes that contain human readable annotations like {Piece} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit 'Stk' SHOULD contain the annotation (it does not) (1 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-epr-term/ValueSet/DocumentEntry.typeCode|2.0.10), 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-epr-term/ValueSet/DocumentEntry.typeCode|2.0.10), 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-epr-term/ValueSet/DocumentEntry.typeCode|2.0.10), 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)

The following code systems/value sets are external and not supported by terminology server (or an example)

• Code System URI 'http://example.com/localcode' is unknown so the code cannot be validated (0 uses)
• Code System URI 'urn:oid:2.51.1.1' is unknown so the code cannot be validated (0 uses)
• The value provided ('rm-CH') is not in the value set 'Common Languages' (http://hl7.org/fhir/ValueSet/languages|4.0.1), and a code is recommended to come from this value set) (error message = The provided code 'urn:ietf:bcp:47#rm-CH' is not in the value set 'http://hl7.org/fhir/ValueSet/languages|4.0.1' (from Tx-Server)) (0 uses)

Errors sorted by type

Terminology_TX_NoValid_13

Terminology_TX_NoValid_18

Terminology_TX_System_NotKnown