Page History

...

...

...

...

...

Medication element <temporality>

...

This element specifies the chronicity of the treatment. Please refer to M. Concept: Temporality "Ad hoc" for details of usage.

Medication element

...

<frequency>

This element specifies the frequency of the treatment. Please refer to M. Concept: Combined use of frequency and day and M. Concept: Hourly frequency and posology for details of usage.

Medication element <beginmoment>

This is the date from when the medication can at the earliest taken.

In the next example, the medication can is the date from when the medication can at the earliest taken.In the next example, the medication can be taken at the earliest starting from the 1th of september 2030: 

...

Medication element <route>

This element specifies the administration route.

Medication element <instructionforpatient>

This is the usage instruction for the patient.

Medication element <instructionforoverdose>

This is the medical justification when the product is overdosed. This element is not used by Vitalink.

Transaction element <item> Transaction 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'.

...

This healthcareelement is not be used by Vitalink. The orginal original intention was to indicate the changes compared to the previous version of the transaction.

...

Healthcareelement "begincondition"

This is an element containing a textual description with the condition when the treatment should be started.

Healthcareelement "endcondition"

This is an element containing a textual description with the condition when the treatment should be ended.

Healthcareelement "medicationtype"

...

The Vitalink transaction TS can be used to express a suspension of the ingestion of the medicationtreatment. A medication scheme can contain 0 or more suspensions.

...

...

This is the date from when the medication treatment should be suspended.

In the next example, the medication should not be taken anymore, until further notice, starting from the 1th of august 2030: 

...

This is the date until which the medication treatment should be suspended.

In the next example, the medication can be taken again earliest starting from the 1th of july 2030: 

...

Medication element <duration>

...

An implicit endmoment can be expressed by defining a duration. This duration defines the period, starting from the beginmoment, during which the medication can not be taken.

In the next example, the medication can be taken again earliest starting from the 1th of december 2030: 

...
<transaction>
	<id S="ID-KMEHR" SV="1.0">46</id>
	...
	<cd S="CD-TRANSACTION" SV="1.11">medicationschemeelement</cd>
	...
</transaction>
...
<transaction>
	<id S="ID-KMEHR" SV="1.0">49</id>
	...
	<cd S="CD-TRANSACTION" SV="1.11">treatmentsuspension</cd>
	...
	<item>
		...
		<beginmoment>
        	<date>2030-11-01</date>
        </beginmoment>
		<duration>
			<decimal>30</decimal>
			<unit>
				<cd S="CD-TIMEUNIT" SV="2.1">d</cd>
			</unit>
		</duration>
		...
		<lnk TYPE="isplannedfor" URL="//kmehr:transaction[id[@S='ID-KMEHR']='46']"/>
	</item>
	...
</transaction>
...

Medication element <lifecycle>

This element specifies if the suspension is temporary ("suspended") or definite ("stopped"). This lifecycle is only indicative, i.e. an application should not use this to interpret or express that a treatment should be stopped permanently. In the latter case, the application should remove the treatment.

Medication element <lnk>

This element contains a link to the transaction MSE that is suspended. The content is an XPath link identifying the corresponding MSE by its ID-KMEHR id.

...