Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Structure specification

Used Kmehr tables

All Kmehr tables can be found at the site of the Kmehr standard, see External Links#kmehr_tables.

Vitalink medication scheme specific Kmehr tables

The Vitalink medication scheme business project needed the addition of some specific tables to the Kmehr standard. This paragraph lists these specific Kmehr tables.

CD-MS-ADAPTATION

Warning
titleUnder discussion

This paragraph is under discussion and needs to be reviewed.

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyVIM-147

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
titleUnder discussion

This paragraph is under discussion and needs to be reviewed.

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyVIM-147

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
titleUnder discussion

This paragraph is under discussion and needs to be reviewed.

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyVIM-147

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:

...

Example with usage of Kmehr tables:

Code Block
languagexml
linenumberstrue
<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>

Example with usage of text field:

Code Block
languagexml
linenumberstrue
<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>

Generic Kmehr tables

The Vitalink medication scheme business project re-uses tables from the Kmehr standard. This paragraph lists these Kmehr tables and their version. For Vitalink, not all codes are always allowed. For each table, a whitelist or blacklist defines this, based on the used version.

Codes added in later versions than the used version are not allowed!

...

CD-ADDRESS

...