...
EVSg 3.x.y expands on this by adding Sumehr and Diarynote integration.
After initial installation, some examples are available to get familiar with the functionalities of EVSg, without the need for further configuration.
This manual describes EVSg v3.3.0.1.
Functionality
General
EVSg allows a certain actor to perform a number of actions for a certain patient. These actions are different, depending on the transactiontype.
...
After initial installation, 2 3 types named "m", "s" and "sd" (meaning "Medicationscheme", "Sumehr" and "SumehrDiarynote" respectively) are available:
...
Any type of files, with any extension, can be dropped. They are considered as "input-files". EVSg will, depending on the action folder, parse the files and extract the MSE, TS, Sumehr and Sumehr Diarynote transactions.
| Note |
|---|
All MS transactions are ignored as input. |
...
For some actions, typically removing and updating "sumehrs", the sumehr that should be changed needs to have an identification. Those sumehrs are expressed as Sumehr transactions. These Sumehr transactions are identified by using an EVS reference.
How is a "Diarynote" identified?
For some actions, typically removing "diarynotes", the diarynote that should be changed needs to have an identification. Those sumehrs are expressed as Diarynote transactions. These Diarynote transactions are identified by using an EVS reference.
Identification by EVS reference
An EVS reference is put in 1 (and only 1) free text field in the concerned MSE, Sumehr or Sumehr Diarynote transaction.
The EVS reference can be freely chosen, and facilitates the definition and execution of scenarios.
...
This action will update the transactions that belong to transactiontype "Sumehr" identified by the EVS REF in the input file.
Which actions for Diarynote?
| Info |
|---|
Only transactions of transactiontype "Diarynote" can be used for input. Any other transactiontype will be ignored. |
Action "add"
This action will add a transaction to the vault for all transactions found in each Kmehrmessage found in all dropped files. If one of the Diarynote transactions within a kmehrmessage does not have an EVS REF yet, an EVS REF will be generated.
Action "export"
This action will export the contents of the vault that belong to transactiontype "Diarynote", without any change to the vault itself. EVSg will do this action once for each dropped file, without parsing this file.
Action "generateRef"
This action will generate an EVS REF for each Diarynote transaction currently in the vault.
If an EVS REF exists already in the Diarynote transaction, no new EVS REF will be generated.
If no EVS REF exists, the new EVS REF is put in the first Text or TextWithLayout field. If none of these exists, a new TextWithLayout field is created.
Action "updateRef"
This action will update the transactions that belong to transactiontype "Diarynote" identified by the EVS REF in the input file.
...