This page is part of the FHIR eMedication exchange formats for the implementation effort of CARA within its EPR community (v1.0.0: STU1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Home
Official URL: http://fhir.ch/ig/ch-emed-epr/ImplementationGuide/ch.fhir.ig.ch-emed-epr
The CH EMED EPR implementation guide describes the FHIR representation of the defined documents for the exchange of medication information in the context of CARA’s eMedication service.
This implementation guide is dependent on CH EMED, CH Core and CH EPR Term, which describe the Swiss specific context, especially related to the Swiss EPR.
Initially this implementation guide was based on the CDA-CH-EMED eMedication ART-DECOR® specification which has been published by eHealth Suisse.
CDA-CH-EMED defined the eMedication documents for the information exchange in the context of the EPR in Switzerland.
The documents were based on the IHE Pharmacy Technical Framework modelled and specialized in the Building Block Repository CH-PHARM.
Base for this modelling was the report from IPAG eMedikation, 7.6.2017 and the work of IPAG/eHealth Suisse.
MTP (Medication Treatment Plan): introducing a treatment in the plan.
PADV (Pharmaceutical advice): modifying the state of the treatment.
PML (Medication list): listing multiple entries in a single document.
PMLC (Medication card): listing the on-going treatments in an aggregated form.
Guidance pages are available to detail some parts of the profile, they are listed in the top menu.
How to understand this IG
Tabs
Resources usually show these three different tabs in the main table. You should only review the Snapshot one.
Differential: it shows differences with the parent artifact. It is only useful to authors of this IG.
Key: it only contains elements that are included in summaries (a feature not used by this IG) or as must support.
Snapshot: the tab that contains all the elements, it is the most useful one.
Flags
must support: the mustSupport flag follows the IHE use of R2 as defined in Appendix Z. It demands that the content creator must support these elements if they are known. If the sending application has data for the element, it is required to populate the element with a non-empty value. If the value is not known, the element may be omitted. A receiving application may ignore the information conveyed by the element. A receiving application shall not raise an error solely due to the presence or absence of the element.
draft/✕: the draft flag or ‘✕’ symbol are used to indicate that an element has no clear use case or description and is useless in this profile. Implementers SHOULD avoid setting or reading it, as elements’ meaning is undefined.
trial use: the element description is being defined and implementers MAY support it.
Binding strengths
required binding: the use of a code present in the given value set is required.
extensible binding: the use of a code present in the given value set is recommended; another code can be used if it is missing.
example binding: the value set is given as example.
This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)
Package ihe.formatcode.fhir#1.1.0
Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)
Package ch.fhir.ig.ch-epr-term#2.0.10
Implementation guide for the meta data specified in the framework of Annex 3 and 9 of the FDHA Ordinance on the electronic patient record in Switzerland (built Tue, Dec 19, 2023 12:36+0100+01:00)
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/getsnomed-ct or info@snomed.org.
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
CH EMED EPR
