| Table of Contents |
|---|
<DEPRECATED>
Introduction
EVS allows to manipulate vault contents using specific actors and specific patients, manually or based on previously exported vault contents.
...
| Name | Output suffix | Extension | Description | Remarks |
|---|---|---|---|---|
Validation file | VALIDATION-OK VALIDATION-<###>-FAILED | .val | The report of the validation. | The filename contains the number of warnings and errors when the validation fails. |
Global scheme PDF | globalscheme | A visualisation of the global scheme in PDF format. | - | |
Daily scheme PDF | dailyscheme-<date> | A visualisation of the daily scheme in PDF format. | This is the scheme of the medication that should be taken today. | |
Export file | - | .exp | An export of the contents of the vault. | - |
Input file | - | .inp | The original input file. | The filename does not include the number of data entries in the vault. |
For the moment, only "today" is generated. Future EVS releases will add free choice of the date....
| Note | ||
|---|---|---|
| ||
EVS (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:
...
| Path | Reserved path | Reserved name | Explanation | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| EVS |  | | The root folder. The name and location can be freely chosen. Keep in mind that paths used in scenarios, patient and actor files are possibly impacted by changes to this! | ||||||||||||||
| \config |  | | Everything that defines the behaviour of EVS, configured as needed by the user. | ||||||||||||||
| \actors | | | All the actors that can be used by EVS. | ||||||||||||||
| \log4j | | | Settings of the log4j library. Please refer to https://logging.apache.org/log4j/2.x/manual/configuration.html for more explanation. | ||||||||||||||
| \patients | | | | All the patients that can be used by EVS. | |||||||||||||
| \exe | | | |||||||||||||||
| \certificates | | | The certificates used in the actor configuration files. | ||||||||||||||
| \exports | |
| The folder were the EVS-exporter will put exported vault contents, see AppendixB:EVSexporter | ||||||||||||||
| \interaction | | | |||||||||||||||
| \input | | | | ||||||||||||||
| \input | | | |||||||||||||||
| \katrien | | | |||||||||||||||
| \gp_van_gucht | | | |||||||||||||||
| \add | | | |||||||||||||||
| \empty | | | |||||||||||||||
| \export | | | |||||||||||||||
| \removeID | | | |||||||||||||||
| \removeREF | | | |||||||||||||||
| \replace | | | |||||||||||||||
| \updateID | | | |||||||||||||||
| |||||||||||||||||
| \katrien | | | |||||||||||||||
| \gp_van_gucht | | | |||||||||||||||
| \add | | | |||||||||||||||
| \empty | | | |||||||||||||||
| \export | | | |||||||||||||||
| \removeID | | | |||||||||||||||
| \removeREF | | | |||||||||||||||
| \replace | | | |||||||||||||||
| \updateID | | | |||||||||||||||
| \updateREF | | | |||||||||||||||
| \generateREF |  | | |||||||||||||||
| \updateschemeREF | | | | | |||||||||||||
| \patient_template | | | |||||||||||||||
| \processed | \processed | | | ||||||||||||||
\scenarios | | | |||||||||||||||
| \basic_example | | | |||||||||||||||
| \system | | | |||||||||||||||
| \dependency-jars | | | |||||||||||||||
Appendix B: EVS-exporter
Besides the interaction provided by dropping files in the input folder, EVS offers as extended functionality the continuous monitoring of the vault contents. This functionality is provided by EVS-exporter.
...
Example of a parameterisation:
