eMediplan CHMED Implementation Guide
3.0.0 - CI Build
eMediplan CHMED Implementation Guide, published by IG eMediplan. This is not an authorized publication; it is the continuous build for version 3.0.0). This version is based on the current content of https://github.com/ahdis/chmed/ and changes regularly. See the Directory of published versions
Official URL: http://chmed.emediplan.ch/fhir/ImplementationGuide/ch.chmed.emediplan | Version: 3.0.0 | |||
Active as of 2022-02-18 | Computable Name: CHMED | |||
Copyright/Legal: CC-BY-SA-4.0 |
Medication plans are a central pillar of any eHealth solution. To enable interoperability between eHealth systems in Switzerland, the organization ‘IG eMediplan’ was founded in 2016. Its aim is to support and provide public, open source, medication plan formats supported by a broad group of stakeholders from the public and private sectors.
Fig.: Example of a Mediplan
The purpose of this implementation guide is to specify the medication plan exchange formats based on the FHIR® standard from HL7®.
Extending the CHMED21A format to a FHIR based definition (CHMED) has the following advantages:
The CHEMD format can be either in XML or JSON format. However, both are too big in size to be exchanged in a QR code.
HCI Solutions AG has built a converter for all software houses that have integrated the CHMED16A/CHMED21A. If you have questions or want more information please contact hotline@hcisolutions.ch directly.
The meaning of the flag mustSupport for this implementation guide follows the definition of CH EMED, the Swiss eMedication IG from which CHMED is derived.
You can download this implementation guide in NPM format from here.
Significant changes to this specification since its initial version.
The ‘eMedication Plan CHMED21A’ paper describes the specification and reference implementation of the object model for a medication plan, the so-called CHMED21A.
The reference consists of:
The content and layout specification for a paper-based layout used in Print/PDF scenarios is described in the document ‘eMediplan_Paper-based_Layout’.
This allows IT systems to store and transmit electronic medication plans as JSON file in UTF-8. It also makes it possible to transmit the mediplan print-based using QR barcodes. Therefore, the mediplan is readable by users and systems alike. This is necessary to guarantee a simple handling.
A typical compressed CHMED21A object would look like this:
{
"MedF": "ChMed21A",
"IsCompressed": true,
"Med":
"H4sIAAAAAAAACq2OOw4CMQxE7zIt2ZUTAmzcLZsGiU+KUCEKYKlokIACRbk7jkLBAWisZz/NyAmb6/g
AHxJWI7hsGgqhnsIOnBDBRmF4+9cebCuBtUL0Xy38g73MnIu+DxX/1nRUkCRiv1zLl9tzOF1uIloqxj9FGT
KmId1oHcnxtGM7a+28c9YtJqSZCPkD+iD8fPQAAAA="
}
It is recommended to use the compressed CHMED21A object to minimize data size.
This implementation guide includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO) and distributed by agreement between IHTSDO and HL7. Implementers of these specification must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/snomed-ct/getsnomed or info@snomed.org.
This implementation guide contains content from LOINC® (http://loinc.org). The LOINC table, LOINC codes, and LOINC panels and forms file are copyright © 1995-2014, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and available at no cost under the license at http://loinc.org/terms-of-use .