...
<date>-<time>_<transactiontype>_<patient>_<actor>_<action>_<input filename>_size-<nr of MSE transactions>_<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 belonging to transactiontype "Medicationscheme" of the vault. | - |
Input file | - | .inp | The original input file. | The filename does not include the number of transactions in the vault. |
Each filename of transactiontype "Sumehr" exists out of:
<date>-<time>_<transactiontype>_<patient>_<actor>_<action>_<input filename>_size-<nr of Sumehr transactions>.<output extension>
| Name | Extension | Description | Remarks |
|---|---|---|---|
| Export file | .exp | An export of the contents belonging to transactiontype "Sumehr" of the vault | - |
| Input file | .inp | The original input file. | The filename does not include the number of transactions in the vault. |
If for some reason the action fails, an error output file is generated:
| Name | Extension | Description | Remarks |
|---|---|---|---|
Error file | .err | The report containing the error. | The content of the error file will identify the problem. |
Logs-folder
Root
This folder will be automatically generated once "start EVS.cmd" or "start EVS exporter.cmd" has been run for the first time.
...
The next parameters can be passed when launching EVSg:
| Name | Values | Meaning |
|---|---|---|
| rootdir | "..\exe\interaction" | Relative or absolute path to the folder that needs to be watched by EVSg. This folder should contain the requested actions. |
| writeAsIs | true|false | false: All patient data from the source Kmehrmessage will be replaced by the correspondign data of the used input patient. Since the Kmehr data model is used for this transformation, it is possible that other Kmehr structure elements are slightly changed too. true: The Kmehrmessage will be sent to the vault untouched. Use this when really no manipulation on the source Kmehrmessage is desired. |
| exportAfterUpload | true|false | true: Each action, excepted "export" itself, should be followed by an export. false: No export is needed after execution of the triggered action. |
| validateExportAfterUpload | true|false | true: Each action should be followed by validation of the vault content. false: No validation is needed. |
| generateGlobalMedicationScheme | true|false | true: Each action should be followed by the generation of a global scheme visualisation PDF. false: No global scheme visualisation is needed. |
| generateDailyMedicationScheme | true|false | true: Each action should be followed by the generation of a daily scheme visualisation PDF. false: No daily scheme visualisation is needed.
|
| dailyMedicationSchemeDate | date("yyyy-MM-dd") | If no date has been given, it will generate a daily medication scheme of the current date. If a date has been given, it will generate a daily medication scheme of the given date. |
| startTransactionId | number | This number will be the number for the first transaction within the kmehrmessage of a putTransactionSetRequest in the context of a medicationscheme. |
| shiftAction | no_tag_and_no_shift tag_and_no_shift shift_and_tag | no_tag_and_no_shift: tag_and_no_shift: shift_and_tag: |
Example of a parameterisation:
...
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 | | | This folder contains the actions for transactiontype "Medicationscheme" | |||||||
| \add | | | ||||||||
| \export | | | ||||||||
\generateREF | | | ||||||||
| \replace | | | ||||||||
| \updateschemeREF | | | ||||||||
| \s | | | This folder contains the actions for transactiontype "Sumehr" | |||||||
| \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 | | | ||||||||
Appendix B: EVSg-exporter
...
For EVSg-exporter, each filename of transactiontype "Medicationscheme" exists out of:
<transactiontype>_<version>_<patient>_<date>_<time>-<author>_size-<nr of MSE transactions>_<unique code>_<output suffix>.<output extension>
| Name | Source |
|---|---|
| Transactiontype | |
Version | "Version" from the 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 MS transaction. |
Time | Time of the latest update derived from the MS transaction. |
| Author | "Author" of the latest update, derived from the MS transaction->UpdatedBy as returned by the gateway. |
| Nr of MSE transactions | The amount of MSE transactions in the vault. |
| Unique code | Code making the filename unique in case an export exists already. |
| Output suffix | Hard coded, depending on file type. For the validation file, the number of warnings and errors and possible failure are shown. |
| Output extension | Hard coded, depending on file type. |
For EVSg-exporter, each filename of transactiontype "Sumehr" exists out of:
<transactiontype>_<version>_<patient>_size-<nr of Sumehr transactions>_<unique code>.<output extension>
| Name | Source |
|---|---|
| Transactiontype | |
| Version | "Version" from the 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. |
| Nr of Sumehr transactions | The amount of Sumehr transactions in the vault. |
| Unique code | Code making the filename unique in case an export exists already. |
| Output extension | Hard coded, depending on file type. |
When the export fails, an error file will be generated, which is the same behaviour as for the folder-triggered export action of EVSg.
...
The next parameters can be passed when launching EVSg-exporter:
| Name | Values | Meaning |
|---|---|---|
| transactionType | "medicationscheme" | This parameter is for future use. For the moment only 1 transaction type is supported. |
| patients | name(s) as defined in EVSg configuration, comma separated | This(these) is(are) the patient(s) that will be monitored and whose vault content(s) will be exported. |
| actor | name as defined in EVSg configuration | This is the actor that will be used for exporting. |
| exportDir | default "..\exe\exports" | This is the path where the output files will be generated. This location can be freely chosen. |
| validate | true|false | true: Each export should be followed by validation of the vault content. false: No validation is needed. |
| generateGlobalMedicationScheme | true|false | true: Each action should be followed by the generation of a global scheme visualisation PDF. false: No global scheme visualisation is needed. |
| generateDailyMedicationScheme | true|false | true: Each action should be followed by the generation of a daily scheme visualisation PDF. false: No daily scheme visualisation is needed.
|
| dailyMedicationSchemeDate | date("yyyy-MM-dd") | If no date has been given, it will generate a daily medication scheme of the current date. If a date has been given, it will generate a daily medication scheme of the given date. |
Example of a parameterisation:
...