General
This paragraph explains the general principles concerning the storage and consultation of a medication scheme.
When reading or updating the medication scheme, all this information should be displayed, validated and checked by the user in its entirety.
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 TS
Read | Create | Update | Delete | |
---|---|---|---|---|
medication scheme | GetTransactionSet | See "Update". | PutTransactionSet | not possible |
transaction MS | As transaction MS in the GetTransactionSetResponse. | See "Update". | not possible | not possible |
transaction MSE | As transaction MSE in the GetTransactionSetResponse. | The new transaction MSE is present in the PutTransactionSetRequest. | The updated transaction MSE is present in the PutTransactionSetRequest. | The transaction MSE is absent in the PutTransactionSetRequest. |
transaction TS | As transaction TS in the GetTransactionSetResponse. | The new transaction TS is present in the PutTransactionSetRequest. | The updated transaction TS is present in the PutTransactionSetRequest. | The transaction TS is absent in the PutTransactionSetRequest. |
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
Read the transaction MS
Read the transaction MSE
Read the transaction TS
Create the medication scheme
Creating the medication scheme means that no transactions MSE or TS are present in Vitalink. A read action at this moment will not return any of the transaction types MSE or TS.
Create transaction MS
A transaction MS must be composed.
Kmehr Element | Input value |
---|---|
id | 2 id elements should be provided:
|
cd | S="CD-TRANSACTION" with value "medicationscheme" |
date | ? |
time | ? |
author | ? |
iscomplete | true VIM-147 - Getting issue details... STATUS |
isvalidated | true VIM-147 - Getting issue details... STATUS |
Vitalink Element | Input value |
---|---|
version | ? |
Create transaction MSE
A transaction MSE must be composed.
Kmehr Element | Input value |
---|---|
id | 2 id elements should be provided:
|
cd | S="CD-TRANSACTION" with value "medicationschemeelement" |
date | ? |
time | ? |
author | ? |
iscomplete | true VIM-147 - Getting issue details... STATUS |
isvalidated | true VIM-147 - Getting issue details... STATUS |
Create transaction TS
A transaction TS must be composed.
Kmehr Element | Input value |
---|---|
id | 2 id elements should be provided:
|
cd | S="CD-TRANSACTION" with value "treatmentsuspension" |
date | ? |
time | ? |
author | ? |
iscomplete | true VIM-147 - Getting issue details... STATUS |
isvalidated | true VIM-147 - Getting issue details... STATUS |
Vitalink Element | Input value |
---|---|
lnk | The link to the corresponding transaction MSE, identified by its cd 'ID-KMEHR'. |
medication | The elements defining the medication information (Medicationscheme Kmehr Structure) should exactly match the medication information elements in the corresponding transaction MSE. |