...
| Name | Values | Meaning |
|---|---|---|
| transactionType | "medicationscheme" "sumehr" "diarynote" | EVS-exporter supports 3 transactiontypes: medicationscheme, sumehr and diarynote. Change this value accordingly. |
| patients | name(s) as defined in EVS 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 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.
|
| generateGatewayMedicationScheme | true|false | true: Each action should be followed by the generation of a global scheme visualisation by the gateway false: No global scheme visualisation by the gateway 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. |
hub (from 3.5.0 onwards) | VITALINK RSW | The Hub to send requests to. |
searchType (from 3.5.0 onwards) | LOCAL GLOBAL | LOCAL: instruct the hub to search only locally. GLOBAL: instruct the hub to search also elsewhere. Only applicable after the hubs will have been linked which is not the case at the time of writing (23/08/2018) |
...