...
| 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 |
| 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 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". |
...
This is almost exactly the same as updatea for updating a 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 "today" and "now", but is the same as the value originally read.
...