...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/>
<soap:Body>
<ns3:GetTransactionListResponse xmlns="http://www.ehealth.fgov.be/hubservices/core/v3" xmlns:ns10="urn:be:fgov:ehealth:metahub:protocol:v2" xmlns:ns2="http://www.ehealth.fgov.be/standards/kmehr/schema/v1" xmlns:ns3="http://www.ehealth.fgov.be/hubservices/protocol/v3" xmlns:ns4="urn:be:fgov:ehealth:metahub:core:v2" xmlns:ns5="http://www.w3.org/2001/04/xmlenc#" xmlns:ns6="http://www.w3.org/2000/09/xmldsig#" xmlns:ns7="urn:be:fgov:ehealth:safe:internal:v3" xmlns:ns8="urn:be:fgov:ehealth:safe:common:decryptor:v3" xmlns:ns9="urn:be:fgov:ehealth:safe:common:v3">
<response>
...
</response>
<acknowledge>
...
</acknowledge>
<kmehrheader>
<folder>
<patient>
...
</patient>
<transaction>
<id S="ID-KMEHR" SV="1.0">1</id>
<id S="LOCAL" SL="vitalinkuri" SV="1.0">/subject/72071135503/medication-scheme</id>
<cd S="CD-TRANSACTION" SV="1.6">medicationscheme</cd>
<cd S="CD-HUBSERVICE" SV="1.0">GetTransactionSet</cd>
...
</transaction>
</folder>
</kmehrheader>
</ns3:GetTransactionListResponse>
</soap:Body>
</soap:Envelope> |
...
| Transaction | Element | Meaning | Store for later use? | Extra information |
|---|---|---|---|---|
| MS | <id> | S="ID-Kmehr": this 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. | YES | |
S="LOCAL" SL="vitalinkuri" This is the unique Vitalink-identifier for the MSE 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.
In this set of transactions, MSE/TS transactions can be manipulated as follows:
Manipulation of MS/TSE transaction | Description |
|---|---|
| create | A new MS/TSE transaction is added to the set. Please refer to the paragraph below how created MS/TSE transactions are structured. |
| delete | The MS/TSE transaction that needs to be deleted is not present anymore in the <kmehrmessage> of the putTransactionSetRequest. |
| update | The MS/TSE transaction that needs to be updated is present in the <kmehrmessage> of the putTransactionSetRequest. Please refer to the paragraph below how updated MS/TSE transactions are structured. |
| preserve | The MS/TSE transaction that needs to be preserved is present in the <kmehrmessage> of the putTransactionSetRequest, and is an exact copy of the earlier read transaction. |
The MS transaction itself must also be passed as input for the putTransactionSetRequest.
| Element | Meaning | Extra information |
|---|---|---|
| <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 reproduce this infirmation 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". |
| <version> | The version of the medication scheme on which this manipulation is based. | An application must pass here the value that was earlier read in the reading sequence. |
Here an example of an updated MS transaction:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<transaction>
<id S="ID-KMEHR" SV="1.0">1</id>
<cd S="CD-TRANSACTION" SV="1.4">medicationscheme</cd>
<date>2018-02-09</date>
<time>10:21:13.603+01:00</time>
<author>
<hcparty>
<id S="ID-HCPARTY" SV="1.0">18334780</id>
<id S="INSS" SV="1.0">82051234978</id>
<cd S="CD-HCPARTY" SV="1.1">persphysician</cd>
<firstname>Hannes</firstname>
<familyname>De Clercq</familyname>
</hcparty>
</author>
<iscomplete>true</iscomplete>
<isvalidated>true</isvalidated>
<version>41</version>
</transaction>
|
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
...