Table of Contents |
---|
General
This paragraph explains the general principles concerning the storage and consultation of a medication scheme.
...
These transactions are named "a transaction set". This is reflected in the presence of the eHealth Interhub Webservices getTransactionSet and putTransactionSet.
Medication scheme
Read a medication scheme
The web service getTransactionList needs to be called in order to retrieve the id for the transaction MS.
...
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
Updating a medication scheme means doing putTransactionSet for a specific patient and with the id of the needed transaction MS.
...
Warning | ||
---|---|---|
| ||
In the RSW and RSB implementations, only the ID of the medication scheme as a whole will be returned. |
Delete a medication scheme
There is no explicit function to delete a medication scheme. A medication scheme is however implictly deleted by deleting all its MS/TSE transactions.
Create a medication scheme
There is no explicit function to create a medication scheme. A medication scheme is however implictly created by creating 1 or more MS/TSE transaction(s).
MSE/TS transaction
Read a MSE/TS transaction
Reading the MSE/TS transactions means parsing the correspondent transaction elements in the getTransactionSetResponse.
Create a MSE/TS transaction
An MSE/TS transaction needs to be composed, compliant to the structure described in M. Kmehr Kmehrmessage Structure, where the following elements have a specific meaning:
...
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</time> <author> ... </author> <iscomplete>true</iscomplete> <isvalidated>true</isvalidated> ... </transaction> |
Update a MSE/TS transaction
An earlier MSE/TS transaction needs to be adapted, compliant to the structure described in M. Kmehr Kmehrmessage Structure, where the following elements have a specific meaning:
...
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-12</date> <time>14:57:45</time> <author> ... </author> <iscomplete>true</iscomplete> <isvalidated>true</isvalidated> ... </transaction> |
Delete a MSE/TS transaction
This can be achieved by not adding the transaction (that needs to be deleted)in the <kmehrmessage> of the putTransactionSetRequest.
Preserve a MSE/TS transaction
This is almost exactly the same as 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.