eMediplan CHMED20AF Implementation Guide: Home

This page is part of the eMediplan CHMED20AF FHIR IG (R4) (v2.0.0: STU 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions


Medication plans are a central pillar of any eHealth solution. To enable interoperability between eHealth systems in Switzerland, the organization “Verein 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.

Example Mediplan


CHMED16A describes the proposed specification and reference implementation of the object model for a medication plan, the so called CHMED16A.

The reference consists of two major parts:

  • The content and layout specification for the electronic document, a string/textfile containing a header such as “CHMED16A1” and the (compressed, encoded) medication plan as a JSON object in UTF-8
  • The content and layout specification for a paper-based layout used in Print/PDF scenarios

This allows IT systems to store and transmit electronic medication plans as simple strings or text files in UTF-8. It also makes it possible to transmit the mediplan print-based through the use of QR barcodes. Therefore, the mediplan is readable by users and systems alike. This is necessary to guarantee a simple handling.

A typical CHMED16A object (QR barcode) would look like this:



In addition, the layout specification for the print-based layouts makes recognition of and work with medication plans easier for medical professionals and patients, as the documents will come in a universal layout, independent of the individual IT systems. Details


Disclaimer July 2020: HCI Solutions AG has built a converter for all software houses that have integrated the CHMED16A. The converter will be published here as soon as it is available. If you have any questions, please contact hotline@hcisolutions.ch directly.

FHIR is a standard in development from HL7. FHIR consists of a RESTFul API and a set of interoperability Ressources.

Extending the CHMED16A format to a FHIR based definition (CHMED20AF) has the following advantages:

  • CHMED20AF formats can be validated for correctness, data types are well defined
  • Base interoperabilty for other projects based on medications, e.g. mappings will be provided for the exchange formats for medication with the EPR in Switzerland.

The CHEMD20AF format can bei either in XML or JSON format.

In the section Introduction the structures for the different formats/values are explained.

Download: You can download this implementation guide in npm format from here.