Introduction

A medication scheme is a kmehrmessage that consists of

• 1 transaction MS, 
• 0 or more transactions MSE and 
• 0 or more transactions TS

According to the Kmehr standard, these transactions need to be put in the folder of the kmehrmessage. The next paragrahs describe the kmehrmessage as used for Vitalink. Please refer to the Kmehr standard specification for the basic explanation, see External Links#kmehr_message-overview.

Kmehrmessage element <header>

Vitalink does not require more elements than the ones that are mandatory by the Kmehr standard.

When writing to Vitalink, all the elements are generated by the eHealth technical connector, based on the used properties.

Kmehrmessage element <folder>

Folder element <patient>

Vitalink does not require more elements than the ones that are mandatory by the Kmehr standard.

When writing to Vitalink, all the elements are generated by the eHealth technical connector, based on the patient information given by the application.

Folder element <transaction> "medicationscheme"

Folder element <transaction> "medicationschemeelement"

Kmehr standard

Vitalink transaction MSE specific <item>

Kmehr element <item>

Each Kmehr element <item> consists of the next elements:

Vitalink element <item> "medication"

The item medication has of the following additional elements:

Vitalink element <item> "healthcareelement"

To include certain Vitalink specific information within the medication scheme data element, use must be made of separate item with value 'healthcareelement'.

In order to further define these healthcareelements, the list CD-ITEM-MS was created for Vitalink, with as permitted values:

Healthcareelement "adaptationflag"

By using a value of the table CD-MS-ADAPTATION it can be indicated where in the kmehr message modifications have been made by the end user.

Permitted values for this list are:

• nochanges
• medication
• posology
• treatmentsuspension

If changes have taken place to several parts of the kmehr message, it is possible to enter multiple values. However if the value ‘nochanges’ is used, only this value is permitted.

<item>
	<id SV="1.0" S="ID-KMEHR">2</id>
	<cd SV="1.3" S="CD-ITEM">healthcareelement</cd>
	<content>
		<cd SV="1.0" S="CD-ITEM-MS">adaptationflag</cd>
		<cd SV="1.0" S="CD-MS-ADAPTATION">medication</cd>
		<cd SV="1.0" S="CD-MS-ADAPTATION">posology</cd>
	</content>
</item>

Healthcareelement "begincondition"

Healthcareelement  "endcondition"

Healthcareelement "medicationtype"

The type of the medication can be indicated via CD-MS-MEDICATIONTYPE.

Permitted values for this list are:

• onprescription
• otc
• other

Healthcareelement "medicationuse"

<item>
	<id SV="1.0" S="ID-KMEHR">2</id>
	<cd SV="1.3" S="CD-ITEM">healthcareelement</cd>
	<content>
		<cd SV="1.0" S="CD-ITEM-MS">medicationuse</cd>
	</content>
	<content>
		<text L="nl">For stomachache</text>
	</content>
</item>

Healthcareelement "origin"

With the help of the list CD-MS-ORIGIN it can be indicated via which path the medication is included in the medication scheme. Has this occurred by means of the ‘normal’ path by which the medicine is prescribed by the doctor and is delivered by the pharmacist (or in the case of OTC medication, is only delivered by the pharmacist)? This path will be indicated with the code ‘regularprocess’.

The other manner is that the patient or a care player indicates that he ingests certain medication. This medication can already be present at the patient's home; they have been obtained via friends or family or possibly purchased via the Internet or abroad. This medication can then still be included in the medication scheme and be indicated with the code ‘recorded’.

Permitted values for this list are:

• regularprocess
• recorded

Transaction TS