...
Transaction | Element | Meaning | Store for later use? | Extra information |
---|---|---|---|---|
MS | <id>id | S="ID-Kmehr" This is a unique Kmehr-identifier for the transaction within the transactionset. | NO | |
S="LOCAL" SL="vitalinkuri" This is the unique Vitalink-identifier for the MS transaction. | YES | This is the same value as the Vitalink-identier retrieved with getTransactionList. | ||
MSE/TS | <id>id | S="ID-Kmehr" This is a unique Kmehr-identifier for the transaction within the transactionset. | YES | |
S="LOCAL" SL="vitalinkuri" This is the unique Vitalink-identifier for the MSE transaction. | YES |
...
Element | Meaning | Extra information | ||||
---|---|---|---|---|---|---|
<author>author | The author of the manipulation of the transaction set. | It is good practice to provide the author information of the user of the application. However, the Vitalink gateway will reproduce this infirmation based on the used session certificates. | ||||
<iscomplete>iscomplete | This is not used in the Vitalink business flow. | It is good practice to hard code this to "true". | ||||
<isvalidated>isvalidated | This is not used in the Vitalink business flow. | It is good practice to hard code this to "true". | ||||
<version>version | The version of the medication scheme on which this manipulation is based. | An application must pass here the value that was earlier read in the reading sequence. The are several ways to retrieve the correct input value:
|
Here an example of an updated MS transaction:
...
Create a MSE/TS transaction
The CRUD operations (Create, Read, Update, Delete) for the medication scheme can be looked at from 2 points of view:
- the medication scheme as a whole, i.e. the kmehrmessage
- the transactions MS, MSE and TSe
...
----------------------
...
In the next paragraphs, a "Kmehr element" next table shows which values should be put in the Kmehr parent elements (create/update) or how they should be interpreted and used (read).
The "Vitalink element" table shows the input/output values for the Vitalink child elements, but only for those elements that influence the basic CRUD behaviour. The usage of the other elements should be clear when reading Medicationscheme Kmehr Structure.
Read the medication scheme kmehrmessage
Read the transaction MS
Read the transaction MSE
Read the transaction TS
Create the medication scheme kmehrmessage
Creating the medication scheme means that no transactions MSE or TS are present in Vitalink.
Create transaction MS
A transaction MS must be composed.
Kmehr Element | Input value | ||||||||
---|---|---|---|---|---|---|---|---|---|
id | 1 id element should be provided:
For Vitalink, the id with S="vitalinkuri" is optional. However, if given, the SSIN part should match the id with S="ID-PATIENT" of the patient element in the kmehr folder. | ||||||||
cd | S="CD-TRANSACTION" with value "medicationscheme" | ||||||||
date | ? | ||||||||
time | ? | ||||||||
author | ? | ||||||||
iscomplete | true
| ||||||||
isvalidated | true
| ||||||||
Vitalink Element | Input value | ||||||||
version | The are several ways to retrieve the correct input value: The value of the element <version> in the element <latestupdate> for the transaction "medicationscheme" in the GetLatestUpdateResponse Note | For Vitalink: GetLatestUpdateResponse returns error 489+406 if no Vitalink transactions at all were ever created.GetLatestUpdateResponse returns error 489+400 if only the medication scheme has never been created yet. The value of the element <version> in the transaction MS in the latest GetTransactionSetResponse
|
Create transaction MSE
...
Kmehr Element | Input value | ||||||||
---|---|---|---|---|---|---|---|---|---|
id | 1 id element should be provided:
An id with S="LOCAL" should not be provided. Absence of this id means for Vitalink that this is a new transaction. | ||||||||
cd | S="CD-TRANSACTION" with value "medicationschemeelement" | ||||||||
date | ? | ||||||||
time | ? | ||||||||
author | ? | ||||||||
iscomplete | true
| ||||||||
isvalidated | true
|
...