...
This action will update the transactions that belong to transactiontype "Sumehr" identified by the EVS REF in the input file.
Processed-
...
folder ← To be updated
After execution of an action a variable number of output files are generated in the processed folder.
The next screenshot shows the output of a successful add-action. Each output file will be explained below:
Each filename of transactiontype "Medicationscheme" exists out of:
<date>-<time>_<patient>_<actor>_<action>_<input filename>_size-<nr of data entries>_<output suffix>.<output extension>
| 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 of the contents belonging to transactiontype "Medicationscheme" of the vault. | - |
Input file | - | .inp | The original input file. | The filename does not include the number of data entries in the vault. |
Each filename of transactiontype "Sumehr" exists out of:
<date>-<time>_<patient>_<actor>_<action>_<input filename>_size-<nr of data entries>.<output extension>
| Name | Extension | Description | Remarks |
|---|---|---|---|
| Export file | .exp | An export of the contents belonging to transactiontype "Sumehr" of the vault the vault. | - |
| Input file- | .inp | The original input file. | The filename does not include the number of data entries in the vault. |
If for some reason the action fails, an error output file is generated:
| Name | Output suffix | Extension | Description | Remarks |
|---|---|---|---|---|
Error file- | .err | The report containing the error. | The content of the error file will identify the problem. |
...
This paragraph gives a brief overview of the folder structure after initial installation. It can be used as reference while using and configuring EVSg.
| Path | Reserved path | Reserved name | Explanation | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| EVSg |  | | 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 EVSg, configured as needed by the user. | ||||||
| \actors | | | All the actors that can be used by EVSg. | |||||||
| \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 EVSg. | |||||||
| \exe | | | ||||||||
| \certificates | | | The certificates used in the actor configuration files. | |||||||
| \exports | |
| The folder were the EVS-exporter will put exported vault contents, see EVSg_3_Manual | |||||||
| \interaction | | | ||||||||
| \input | | | ||||||||
| \katrien | | | ||||||||
| \gp_van_gucht | | | ||||||||
| \m | ||||||||||
| \add | | | ||||||||
| \export | | | ||||||||
\generateREF | | | ||||||||
| \replace | | | ||||||||
| \updateschemeREF | | | ||||||||
| \s | ||||||||||
| \add | | | ||||||||
| \empty | | | ||||||||
| \export | | | ||||||||
| \generateREF | | | ||||||||
| \removeREF | | | ||||||||
| \replace | | | ||||||||
| \updateREF | | | ||||||||
| \patient_template | | | ||||||||
| \processed | | | ||||||||
| \logs | | | Can be configured through the log4j settings. | |||||||
| \communication | | | ||||||||
\scenarios | | | ||||||||
| \basic_example | | | ||||||||
| \system | | | ||||||||
| \dependency-jars | | | ||||||||
...