The Vitalink medicationscheme business project uses 3 transactions of the Kmehr standard:
- medicationscheme
- medicationschemeelement
- treatmentsuspension
The first two were added to the Kmehr standard, the third transaction was already part of the Kmehr standard. For the new transactions and for the semantics of the re-used transaction, a maximal alignment with other business projects (e.g. Recip-e) was aimed at. This means that the corresponding Kmehr xml elements are very much alike, but not guaranteed to be 100% the same.
The specification of the usage of the Kmehr standard for the Vitalink medicationscheme consists of:
| M. Kmehrmessage Structure | This describes the structure of each transaction |
| M. Supported Kmehr tables, versions and codes | This is a reference with the Kmehr tables used in the transactions |
| M. Kmehrmessage Validation | This specifies extra business validation of the data in the transactions |
| M. Integration | This specifies how to do CRUD-operations on scheme-level. |
| Table of Contents |
|---|
General
A medication scheme consists of
- 1 transaction MS,
- 1 or more transactions MSE and
- 0 or more transactions TS.
Structure specification
Used Kmehr tables
Vitalink medication scheme specific Kmehr tables
CD-MS-ADAPTATION
| Warning | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This paragraph is under discussion and needs to be reviewed.
|
By means of the list CD-MS-ADAPTATION it can be indicated in a simple manner 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.
CD-MS-MEDICATIONTYPE
| Warning | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This paragraph is under discussion and needs to be reviewed.
|
The type of the medication can be indicated via CD-MS-MEDICATIONTYPE.
Permitted values for this list are:
- onprescription
- otc
- other
CD-MS-ORIGIN
| Warning | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This paragraph is under discussion and needs to be reviewed.
|
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
CD-ITEM-MS
To include certain project specific information within the medication scheme data element, use must be made of separate CD-ITEM with value 'healthcareelement'. In order to further define these items the list CD-ITEM-MS is available with as permitted values:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<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> |
...