...
| Transaction | Element | Meaning | Store for later use? | Extra information |
|---|---|---|---|---|
| MS | 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 | S="ID-KMEHR" This is a unique Kmehr-identifier for the transaction within the transactionset. | NO | Although storage is not needed for the web service manipulation flow, it is off course needed to know the link between TS transactions and the MSE transactions they poin to. |
S="LOCAL" SL="vitalinkuri" This is the unique Vitalink-identifier for the MSE/TS transaction. | YES |
Update a medication scheme
...
| 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". |
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<transaction> <id S="ID-KMEHR" SV="1.0">6</id> <cd S="CD-TRANSACTION" SV="1.11">medicationschemeelement</cd> <date>2018-02-09</date> <time>10:21:13.603+01:00<13</time> <author> ... </author> <iscomplete>true</iscomplete> <isvalidated>true</isvalidated> ... </transaction> |
...
| 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" | Absence of this id means for Vitalink that this is a newly created transaction. | 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 | ||
| date | Date of creation | Typically, the creating application should choose " | 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 is 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". |
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<transaction> <id S="ID-KMEHR" SV="1.0">6</id> <id S="LOCAL" SL="vitalinkuri" SV="1.0">/subject/72071135503/medication-scheme/70277/2</id> <cd S="CD-TRANSACTION" SV="1.11">medicationschemeelement</cd> <date>2018-02-09<12</date> <time>10<time>14:21:13.603+01:00<57:45</time> <author> ... </author> <iscomplete>true</iscomplete> <isvalidated>true</isvalidated> ... </transaction> |
...
This is almost exactly the same as updatea MSE/TS transaction. The only difference is however that the date and time of the transaction that needs to be preserved, is not set to "rodaytoday" and "now", but is the same as the value originally read.
...