...
Depending on the folder where the input-file is dropped, EVSg will execute an action.
| Info |
|---|
It is not possible to use Sumher transactions as input for actions that belong to the transactiontype "Medicationscheme". Doing this would trigger an error. |
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 MSE transactions within a kmehrmessage does not have an EVS REF yet, an EVS REF will be generated.
In the example below, 3 transactions are dropped to be added to the vault:
Action "
...
generateREF"
This action will export the contents of the vault, without any change to the vault itself. EVSg will do this action once for each dropped file, without parsing this file.
In the example below, a newly created file will trigger an export of the contents of the vault:
Action "generateREF"
This action will generate an EVS REF for each MSE 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 MSE transaction, no new EVS REF will be generated.
If no EVS REF exists, the new EVS REF is put in the instructionforpatient field.
Action "replace"
This action will replace the contents of the vault by all the 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 transactions of the last input file! If one of the MSE transactions within a 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 transactions.
Action "updateschemeREF"
This action will update the complete contents of the vault, based on the input file compared with the current contents of the vault.
The next actions will take place:
- 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 EVS REF already existing in the vault will cause an update if any difference between the input-transaction and vault-transaction is found
- all MSE transactions without corresponding EVS REF in the input file will be removed from the vault
...
generate an EVS REF for each MSE 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 MSE transaction, no new EVS REF will be generated.
If no EVS REF exists, the new EVS REF is put in the instructionforpatient field.
Action "replace"
This action will replace the contents of the vault that belong to transactiontype "Medicationscheme" by all the 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 transactions of the last input file! If one of the MSE transactions within a 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 4 transactions.
Action "updateschemeREF"
This action will update the complete contents of the vault that belong to transactiontype "Medicationscheme", based on the input file compared with the current contents of the vault.
The next actions will take place:
- 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 EVS REF already existing in the vault will cause an update if any difference between the input-transaction and vault-transaction is found
- all MSE transactions without corresponding EVS REF in the input file will be removed from the vault
If the input-file contains MSE transactions with EVS REFs that are not unique, the action will not be executed and an error will be thrown.
| Tip | ||
|---|---|---|
| ||
The 'old' EVS, with Vitalink connector-integration, offered an action 'empty'. EVSg doesn't offer this action anymore. Now, emptying the vault can be done by dropping an empty file for the actions "updateschemeREF" or "replace". |
Which actions for Sumehr? ← Review needed
| Info |
|---|
It is not possible to use MSE or TS transactions as input for actions that belong to the transactiontype "Sumehr". Doing this would trigger an error. |
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 Sumehr transactions within a kmehrmessage does not have an EVS REF yet, an EVS REF will be generated.
In the example below, 3 transactions are dropped to be added to the vault:
Action "empty"
This action will remove all transactions from the vault that belong to transactiontype "Sumehr". EVSg will do this action once for each dropped file, without any parsing.
In the example below, a newly created file will trigger emptying of the vault by removing all existing transactions of transactiontype "Sumehr":
Action "export"
This action will export the contents of the vault that belong to transactiontype "Sumehr", without any change to the vault itself. EVS will do this action once for each dropped file, without parsing this file.
In the example below, a newly created file will trigger an export of the contents of the vault of transactiontype "Sumehr":
Action "generateRef"
This action will generate an EVS REF for each Sumehr 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 Sumehr transaction, no new EVS REF will be generated.
If no EVS REF exists, the new EVS REF is put in the instructionforpatient field.
Action "removeRef"
This action will remove the transactions that belong to transactiontype "Sumehr" identified by the EVS REF in the input file from the vault.
Action "replace"
This action will replace the contents of the vault that belong to transactiontype "Sumehr" by all the 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 transactions of the last input file! If one of the Sumehr transactions within a 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 4 transactions.
Action "updateRef"
This action will update the transactions that belong to transactiontype "Sumehr" identified by the EVS REF in the input file.
...
| title | Empty |
|---|
...
Processed-folder
After execution of an action a variable number of output files are generated in the processed folder.
...