Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In the example below, 3 transactions are dropped to be added to the vault: KM->transaction(s)

Action "export"

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.

...

If no EVS REF exists, the new EVS REF is put in the instructionforpatient fieldMoet "New textdocument.txt" worden

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. KM->transaction(s)

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. KM->transaction(s)

The next actions will take place:

...

If for some reason the action fails, an error output file is generated: KM->transaction(s)

NameOutput suffixExtensionDescriptionRemarks

Error file

-

.errThe report containing the error.

The content of the error file will identify the problem.

...

NameSource

Version


"Version" from the medicationscheme MS transaction.

In case of an empty medicationscheme, the "version" is derived from the getLatestUpdate method.

Patient

Name of the patient as defined in the EVSg configuration.

Date

Date of the latest update derived from the medicationsscheme MS transaction.

Time

Time of the latest update derived from the medicationsscheme MS transaction.

Author"Author" of the latest update, derived from the medicationsscheme MS transaction->UpdatedBy as returned by the gateway.
Nr of MSE transactionsThe amount of MSE transactions in the vault.
Unique codeCode making the filename unique in case an export exists already.
Output suffixHard coded, depending on file type. For the validation file, the number of warnings and errors and possible failure are shown.
Output extensionHard coded, depending on file type.

...