...
| Element | Meaning | Extra information | |||||
|---|---|---|---|---|---|---|---|
| id S="ID-KMEHR" | A unique Kmehr-identifier that distinguishes this transaction from all others. | This does not need to be the same value from the orginally read one. However make sure the relations between TS and MSE transactions are not broken. | |||||
| id S="LOCAL" SL="vitalinkuri" | This should not be present! | Absence of this id means for Vitalink that this is a newly created transaction.
| |||||
| date | Date of creation | Typically, the creating application should choose "today". | |||||
| time | Time of creation | Typically, the creating application should choose "now". | |||||
| 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 generate this information based on the used session certificates. | |||||
iscomplete | This is not used in the Vitalink business flow. | It is good practice to hard code this to "true". | |||||
isvalidated | This is not used in the Vitalink business flow. | It is good practice to hard code this to "true". |
...
| Element | Meaning | Extra information | |||||
|---|---|---|---|---|---|---|---|
| id S="ID-KMEHR" | A unique Kmehr-identifier that distinguishes this transaction from all others. | This does not need to be the same value from the orginally read one. However make sure the relations between TS and MSE transactions are not broken. | |||||
| id S="LOCAL" SL="vitalinkuri" | The unique identifier provided by Vitalink that distinguishes the MSE transaction from all other MSE transactions and the TS . | . This need to be the same value from the orginally read one, in other words Vitalink needs to know which transaction needs to be updated.
| |||||
| date | Date of creation | Typically, the creating application should choose "today". | |||||
| time | Time of creation | Typically, the creating application should choose "now". The fact that the date and time are more recent than the original ones means for Vitalink that this is an updated transaction. | |||||
| 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 generate this information based on the used session certificates. | |||||
iscomplete | This is not used in the Vitalink business flow. | It is good practice to hard code this to "true". | |||||
isvalidated | This is not used in the Vitalink business flow. | It is good practice to hard code this to "true". |
...
| Warning | ||
|---|---|---|
| ||
In the RSW and RSB implementations, only the ID of the medication scheme as a whole will be returned. |
Update transaction MS
A transaction MS must be composed.
...
Kmehr Element
...
Input value
...
2 id elements should be provided:
...
S="LOCAL", SL="vitalinkuri"
| Warning | ||
|---|---|---|
| ||
In the RSW, this local_id is named “RSWID” and in RSB “RSBID”. |
...
true VIM-147 - Vragenlijst Kmehr OPEN
...
true VIM-147 - Vragenlijst Kmehr OPEN
...
Vitalink Element
...
Input value
...
Update transaction MSE
A transaction MS must be composed.
...
Kmehr Element
...
Input value
...
2 id elements should be provided:
...
S="LOCAL", SL="vitalinkuri"
...
| title | RSW/RSB annotation |
|---|
...
. |
...
true VIM-147 - Vragenlijst Kmehr OPEN
...
true VIM-147 - Vragenlijst Kmehr OPEN
Create transaction MSE
Create transaction TS
Delete transaction MS
A transaction MS must be composed.
...
Kmehr Element
...
Input value
...
2 id elements should be provided:
...
S="LOCAL", SL="vitalinkuri"
| Warning | ||
|---|---|---|
| ||
In the RSW, this local_id is named “RSWID” and in RSB “RSBID”. |
...
true VIM-147 - Vragenlijst Kmehr OPEN
...
true VIM-147 - Vragenlijst Kmehr OPEN
...