201805 MedicationPlan-Track

Return to May 2018 Proposals

German Medication Plan

This track allows creator and consumer of the german Medikationsplan PLUS to test their application against the official HL7 Germany Test Server.
Pre-connectathon testing is encouraged, but not required, where the participants can utilize the German FHIR Testserver: http://fhir.hl7.de

Submitting WG/Project/Implementer Group

HL7 Germany Affiliate

Justification

Since October 1, 2016, patients have been entitled to a so-called nationwide medication plan if they take or use at least three systemically acting drugs prescribed at the expense of the statutory health insurance funds at the same time. Until now the medication plan is paper based, containing an 2D-Code encoded representation of the paper plan in the FHIR Ultra Short Format UKF. This track sees Medication Plans as a set of profiles (see specification below).

Proposed Track Lead

Simone Heckmann

Co-Leads:
Stefan Lang
Kai Heitmann
Patrick Werner

Version of FHIR

The scenarios described below will be based on the DSTU3 FHIR version utilizing the “Medikationsplan PLUS” profiles: https://simplifier.net/medikationsplanplus

Roles

Medication Plan Consumer

Consumes the medication plan bundle from the FHIR Testserver. If changes to a existing plan are necessary the consumer also plays the creator role after consuming the document bundle.

Medication Plan Creator

Plays the role of a creator of a german medication plan document bundle - uploading the medication plan to the FHIR Test Server.

Creation of a medication plan can have two contexts:

• Initial creation of medication plan for a patient, with all his drugs he shall take, along with the medication information,dosage, possible instructions for the patient.
• Modification of an existing medication plan of a patient (this includes also the Medication Plan Consumer Role)

Scenarios

1. Querying the server for a medication plan for a given patient
   Action: Medication Plan Consumer queries the FHIR Server for the document bundle representing the current medication plan of a patient.
   Precondition: Document Bundle exists on FHIR server prior to action, the identifier of the patient is known to the Medication Plan Consumer.
   Success Criteria: Consumer can display the document and render the content.
2. Modification of a medication plan for a given patient on the server.

   a) Modification of a single medication dosage.

   Action: Medication Plan Creator queries the FHIR Server for the document bundle representing the current medication plan of a patient and updates the dosage of one medication of the plan.
   Precondition: Document Bundle exists on FHIR server prior to action, the identifier of the patient is known to the Medication Plan Consumer.
   Success Criteria: The dosage of the manipulated medication is updated in the patient’s medication plan document bundle.

   b) Addition a new medication to the medication plan.

   Action: Medication Plan Creator queries the FHIR Server for the document bundle representing the current medication plan of a patient and adds a new medication to the plan.
   Precondition: Document Bundle exists on FHIR server prior to action, the identifier of the patient is known to the Medication Plan Consumer.
   Success Criteria: The new medication is added in the patients medication plan document bundle on the server.

   c) Removal of a medication of the medication plan.

   Action: Medication Plan Creator queries the FHIR Server for the document bundle representing the current medication plan of a patient and removes a medication from the medication plan bundle.
   Precondition: Document Bundle exists on FHIR server prior to action, the identifier of the patient is known to the Medication Plan Consumer.
   Success Criteria: The obsolete medication is removed from the patient’s medication plan document bundle on the server.

3. Creation of a patient and a medication plan consisting of three medications.
   Action: Medication Plan Creator creates a document bundle representing the current medication of a patient consisting of three different medications.
   Precondition: -
   Success Criteria: The new medication persisted on the Test Server and can be consumed by a medication plan consumer (scenario 1)

Links

Here are some links to assist implementers:

• REST API in the Specification.
• Medication Plan Conformance Resources at Simplifier.de.
• Medication Plan Implementation Guide.