2.1 Functionalities ‐ Medicationscheme
Depending on the folder where the input-file is dropped, EVS will execute an action.
ℹ️ Only transactions of transactiontype "Medicationscheme" can be used for input. Any other transactiontype will be ignored.
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:
This action will export the contents of the vault that belong to transactiontype "Medicationscheme", 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:
This action will generate an EVS REF for each MSE transaction currently in the vault. ℹ️ 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.
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.
If you want to 'empty' the medicationscheme in the vault. Drop an empty textfile OR a valid XML without any MSE in the REPLACE folder.
In the next example, after processing the next 3 input files, the vault contains 4 transactions.
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.
Looking a lot like updateSchemREF, this action will update 1 or more targetted MSE transactions within the transactiontype MedicationScheme on the vault without touching the other MSE's, not included in the source file. So the source file does NOT include the complete MS with updated + non-updated MSE's but an MS with only the MSE's you want to alter.
An ERROR status is thrown in following cases:
- 1 or more of the included MSE in the MS of the sourcefile contains an EVSREF that was not found in the MS on the vault, no update will happen untill corrected
- 1 or more of the included MSE in the MS of the sourcefile does not contain an EVSREF, no update will happen untill corrected
If no difference is found between input MS and vault MS, no update will happen.
The next actions will take place:
- If no ERROR is detected in the source file, before executing the update (PutTransaction), a list is provided in the EVS console of all MSE's entries with their maching EVSREF's found within the targetted MS on the vault, together if it will be updated or not.
- an MSE transaction with EVSREF already existing in the vault will be updated if any difference between the input-MSE transaction and vault-MSE transaction is found and versionnr of MSE + MS will be +1
✔️ Empty - The 'old' EVS, with Vitalink connector-integration, offered an action 'empty'. EVS doesn't offer this action anymore. Now, emptying the vault can be done by dropping an empty file for the actions "updateschemeREF" or "replace".