...
- 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
Action "updateREF"
Looking a lot like updateSchemREF, this action will update 1 or more specific MSE transactions within the transactiontype MedicationScheme on the vault without touching the other MSE's, not included in the source file.
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 detected in the source file, before executing the update (PutTransaction), a list is provided in the EVS console of all MSE's with their 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
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.
...