...
| Table of Contents |
|---|
Introduction
EVSg is an evolution of EVS, using gateway-integration instead of Vitalink connector-integration. It allows the manipulation of vault contents using specific actors and specific patients, manually or based on previously exported vault contents.
After initial installation, some examples are available to get familiar with the functionalities of EVSEVSg, without the need for further configuration.
...
EVSg will work with Kmehrmessages of Kmehr-standard 20120401 and Kmehr-standard 20161201. It will automatically convert Kmehrmessages of Kmehr-standard 20120401 to Kmehr-standard 20160401.
All data (among which the metadata) extra data needed for the communication with the gateway will be generated by the EVSg and/or the Vitalink platform. As input the data as depicted in the image below will be used:
How is a "medication" within a Kmehrmessage identified?
For some actions, typically removing and updating data entries"medications", the medication that medication that should be changed needs to have an identification. Those medications are expressed as MSE transactions in the Kmehrmessage. These MSE transactions are identified by using an EVS reference.
| Note |
|---|
TS transactions can not be updated! They can only be added or removed. |
Identification by EVS reference
An EVS reference is put in 1 (and only 1) free text field in the concerned medicationMSE transaction.
The EVS reference can be freely chosen, and facilitates the definition and execution of scenarios.
...
If multiple EVS REFs have been given for 1 medicationMSE transaction, EVSg will not execute an action and will raise an error.
...