...
| Note |
|---|
TS transactions can not be updated and should not contain EVS references! They can only be added or removed. |
...
If multiple EVS REFs have been given for 1 MSE transaction, EVSg will not execute an the action and will raise an error.
Which actions?
...
Action "add"
This action will add a data entry transaction to the vault for all transactions found in each Kmehrmessage found in all dropped files. If one of the medications MSE transactions within a kmehrmessage does not have an EVS REF yet, this an EVS REF will be generated.
In the example below, 3 Kmehrmessages transactions are dropped to be added to the vault:
...
This action will generate an EVS REF for each medication within a kmehrmessageMSE transaction currently in the vault.
| Note |
|---|
The 'old' EVS, with Vitalink connector-integration, added the references to the input file, followed by putting this in the vault. |
If an EVS REF exists already in the medicationMSE transaction, no new EVS REF will be generated.
...
This action will replace the contents of the vault by all the Kmehrmessages transactions found in the input file. Be aware of the fact that dropping multiple files in the replace-folder will result in a vault with as contents the Kmehrmessages transactions of the last input file! If one of the medications MSE transactions within a kmehrmessage file does not have an EVS REF yet, this will be generated.
In the next example, after processing the next 3 input files, the vault contains 2 data entriestransactions.
Action "updateschemeREF"
...
The next actions will take place:
- a medication an MSE transaction with EVS REF not yet existing in the vault will be added to the vault, together with all TS transactions which are linked with this MSE transaction
- an MSE transaction with a medication with EVS REF already existing in the vault will cause an update but only if medication differs from the vault-medicationif any difference between the input-transaction and vault-transaction is found
- all MSE transactions all medications without corresponding EVS REF in the input file will be removed from the vault
If the input-file contains medications MSE transactions with EVS REFs that are not unique, the action will not be executed and an error will be thrown.
...
| Note | ||
|---|---|---|
| ||
EVSg (and EVS-exporter) should be restarted when newly added patients will be used. |
How to add an actor?
Extra actors can be added by creating files in the next folder:
| Note |
|---|
The 'old' EVS, with Vitalink connector-integration, used another syntax in this files. EVSg is not compatible with this old format! |
After initial installation, some actor config files are already present. All can be used as example (copy-paste) to add extra actors. The name of the file, without the extension, needs to be used to identify by which actor the action needs to be performed.
...
After copy paste of the appropriate example file, insert the correct info for the new actor:
The needed info in the above template is the certificate name, the password of the certificate, the SSIN, the NIHII number and the actor's name. The location of the certificate can be freely chosen, but it is good practice to put it in the same folder as the example by installation:
...