Scope

This page contains the Kmehrmessages for testing the integration of the 4 mainly used Kmehr tables.

Downloading

CD-ADMINISTRATIONUNIT

This EVS export contains for each code of CD-ADMINISTRATIONUNIT a unique medication.

Each medication has in the text of the "medicationuse" healthcareelement the value <dutch translation>.

...
<transaction>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">2</id>
		<cd S="CD-ITEM" SV="1.11">medication</cd>
		...
		<regimen>
			...
			<quantity>
				<decimal>1</decimal>
				<unit>
					<cd S="CD-ADMINISTRATIONUNIT" SV="1.2">tsp</cd>
				</unit>
			</quantity>
			...
		</regimen>
		...
	</item>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">3</id>
		<cd S="CD-ITEM" SV="1.11">healthcareelement</cd>
		<content>
			<cd S="CD-ITEM-MS" SV="1.0">medicationuse</cd>
		</content>
		<content>
			<text L="nl">Koffielepel</text>
		</content>
	</item>
	...
</transaction>
...

This allows to verify quickly, in the reading application, if the free text value matches the parsed values.

E.g. for the EVS:

After reading a medication scheme with only these lines, you should end up with:

• a medication scheme with 43 medications,
• each administrationunit shown in the caretaker UI (or print) should have the same meaning of the <dutch translation> (e.g. synonyms and abbreviations are allowed,
• each administrationunitshown in the patient UI (or print) should be exactly the same as the <dutch translation> (e.g. synonyms or abbreviations are not allowed).

CD-DAYPERIOD

This EVS export contains for each code of CD-PERIODICITY a unique medication.

Each medication has in the text of the "medicationuse" healthcareelement the value <dutch translation>.

...
<transaction>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">2</id>
		<cd S="CD-ITEM" SV="1.11">medication</cd>
		...
		<regimen>
			...
			<daytime>
				<dayperiod>
					<cd S="CD-DAYPERIOD" SV="1.0">beforelunch</cd>
				</dayperiod>
			</daytime>
			...
		</regimen>
		...
	</item>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">3</id>
		<cd S="CD-ITEM" SV="1.11">healthcareelement</cd>
		<content>
			<cd S="CD-ITEM-MS" SV="1.0">medicationuse</cd>
		</content>
		<content>
			<text L="nl">Voor het middageten</text>
		</content>
	</item>
	...
</transaction>
...

This allows to verify quickly, in the reading application, if the free text value matches the parsed values.

E.g. for the EVS:

After reading a medication scheme with only these lines, you should end up with:

• a medication scheme with 14 medications,
• each dayperiod shown in the caretaker UI (or print) should have the same meaning of the <dutch translation> (e.g. synonyms and abbreviations are allowed,
• each dayperiod shown in the patient UI (or print) should be exactly the same as the <dutch translation> (e.g. synonyms or abbreviations are not allowed) and
• the organisations of the columns should be according to "5.1 Guidelines for displaying the Vitalink Medication scheme as an overview scheme " in http://www.vitalink.be/sites/default/files/atoms/files/Safe_Cookbook_Medicatieschema_v5.5_EN.pdf.

CD-DRUGROUTE

This EVS export contains for each code of CD-DRUGROUTE a unique medication.

Each medication has in the text of the "medicationuse" healthcareelement the next values: <order>/<dutch translation>.

...
<transaction>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">2</id>
		<cd S="CD-ITEM" SV="1.11">medication</cd>
		...
		<route>
        	<cd S="CD-DRUG-ROUTE" SV="2.0">00001</cd>
        </route>
		...
	</item>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">3</id>
		<cd S="CD-ITEM" SV="1.11">healthcareelement</cd>
		<content>
			<cd S="CD-ITEM-MS" SV="1.0">medicationuse</cd>
		</content>
		<content>
			<text L="nl">In het oor</text>
		</content>
	</item>
	...
</transaction>
...

This allows to verify quickly, in the reading application, if the free text value matches the parsed values.

E.g. for the EVS:

After reading a medication scheme with only these lines, you should end up with:

• a medication scheme with 30 medications,
• each drugroute shown in the caretaker UI (or print) should have the same meaning of the <dutch translation> (e.g. synonyms and abbreviations are allowed,
• each drugroute in the patient UI (or print) should be exactly the same as the <dutch translation> (e.g. synonyms or abbreviations are not allowed).

CD-PERIODICITY

This EVS export contains for each code of CD-PERIODICITY a unique medication.

Each medication has in the text of the "medicationuse" healthcareelement the next values: <order>/<dutch translation>.

...
<transaction>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">2</id>
		<cd S="CD-ITEM" SV="1.11">medication</cd>
		...
		<frequency>
			<periodicity>
				<cd S="CD-PERIODICITY" SV="1.1">D</cd>
			</periodicity>
		</frequency>
		...
	</item>
	...
	<item>
		<id S="ID-KMEHR" SV="1.0">3</id>
		<cd S="CD-ITEM" SV="1.11">healthcareelement</cd>
		<content>
			<cd S="CD-ITEM-MS" SV="1.0">medicationuse</cd>
		</content>
		<content>
			<text L="nl">1/Dagelijks</text>
		</content>
	</item>
	...
</transaction>
...

This allows to verify quickly, in the reading application, if the free text value matches the parsed values.

E.g. for the EVS:

After reading a medication scheme with only these lines, you should end up with:

• a medication scheme with 52 medications,
• sorted by the order indicated by the <order> in the "medicationuse" healthcareelement,
• each periodicity shown in the caretaker UI (or print) should have the same meaning of the <dutch translation> (e.g. synonyms and abbreviations are allowed) and
• each periodicity shown in the patient UI (or print) should be exactly the same as the <dutch translation> (e.g. synonyms or abbreviations are not allowed).

Uploading

For the applications who can write to Vitalink, the next 2 tests can be performed:

• do a minimal change (e.g. add an underscore to each medicationuse text) to each line after reading, and do an upload, and check with EVS if the content is properly updated.
• start from an empty vault, construct from scratch the corresponding scheme, do an upload, and check with EVS if the content is properly updated.