...
| Note | ||
|---|---|---|
| ||
EVSg (and EVSEVSg-exporter) should be restarted when newly added actors will be used. |
...
| Name | Values | Meaning |
|---|---|---|
| rootdir | "..\exe\interaction" | Relative or absolute path to the folder that needs to be watched by EVSEVSg. 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. |
Example of a parameterisation:
Appendix A: Folder structure EVSg 2.
...
x.
...
y
This paragraph gives a brief overview of the folder structure after initial installation. It can be used as reference while using and configuring the EVSEVSg.
| 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 user manual | ||||||
| \interaction | | | |||||||
| \input | | | |||||||
| \katrien | | | |||||||
| \gp_van_gucht | | | |||||||
| \add | | | |||||||
| \export | | | |||||||
\generateREF | | | |||||||
| \replace | | | |||||||
| \updateschemeREF | | | |||||||
| \patient_template | | | |||||||
| \processed | | | |||||||
| \logs | | | Can be configured through the log4j settings. | ||||||
| \communication | | | |||||||
\scenarios | | | |||||||
| \basic_example | | | |||||||
| \system | | | |||||||
| \dependency-jars | | | |||||||
Appendix B:
...
EVSg-exporter
Besides the interaction provided by dropping files in the input folder, EVSg offers as extended functionality the continuous monitoring of the vault contents. This functionality is provided by EVSEVSg-exporter.
Launching
EVSEVSg-exporter can be launched via the "vault-exporter.cmd" batch file:
The behaviour of EVSEVSg-exporter must be determined by passing some mandatory parameters. Instead of using the "vault-exporter.cmd" batch file, it is easier to use the example batch file "start EVS.cmd":
...
After initial installation, launching the EVSEVSg-exporter means that the vault contents of the patient "katrien" will be monitored.
Output
When EVSEVSg-exporter detects for the given patients a change in the vault contents, an export is executed. The export is also executed after intial initial launch.
The exported files are put in the next folder, with for each monitored patient a subfolder. The subfolder is automatically created when the monitoring for this patient is initially started.
...
The files contain the same as the files generated by EVSg in the processed-folder, but the filenames differ.
For EVSEVSg-exporter, each filename exists out of:
MS_<version>_<patient>_<date>_<time>-<author>_size-<nr of MSE transactions>_<unique code>_<output suffix>.<output extension>
...
The next parameters can be passed when launching EVSEVSg-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 EVS 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 EVS 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. |
...