...
| 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:
Each filename of transactiontype "Diarynote" exists out of:
<date>-<time>_<transactiontype>_<patient>_<actor>_<action>_<input filename>_size-<nr of Diarynote transactions>.<output extension>
| Name | Extension | Description | Remarks |
|---|
| Export file | .exp | An export of the contents belonging to transactiontype "Diarynote" 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 | errThe report containing the error. | The content of the error file will identify the problem. |
...
| 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_templated | add | | | This folder contains the actions for transactiontype "Diarynote" | ||||||||||
| export | | | ||||||||||||
| generateREF | | | ||||||||||||
| updateREF | | | ||||||||||||
| \patient_template | | | ||||||||||||
| \processed | | | ||||||||||||
| \logs | | | Can be configured through the log4j settings. | |||||||||||
| \communication | | | ||||||||||||
\scenarios | | | ||||||||||||
| \basic_example | | | ||||||||||||
| \system | | | ||||||||||||
| \dependency-jars | | | ||||||||||||
...
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. As such, there are different naming conventions for "Medicationscheme" and "Sumehr".
...
initially started.
The files contain the same as the files generated by EVSg in the processed-folder, but the filenames differ. As such, there are different naming conventions for "Medicationscheme", "Sumehr" and "Diarynote".
For EVSg-exporter, each filename of transactiontype "Medicationscheme" exists out of:
<current-date>-<current-time>_<transactiontype>_<version>_<patient>_<date>_<time>-<author>_size-<nr of MSE transactions>_<unique code>_<output suffix>.<output extension>
| Name | Source |
|---|---|
| current-date | Date of performing the export (from 3.3.0 onwards) |
| current-time | Time of performing the export (from 3.3.0 onwards) |
| 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 "MedicationschemeSumehr" exists out of:
<current-date>-<current-time>_<transactiontype>_<version>_<patient>_<date>_<time>-<author>_size-<nr of MSE Sumehr 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. | ||||
| current-date | Date of performing the export (from 3.3.0 onwards) | ||||
| current-time | Time of performing the export (from 3.3.0 onwards) | ||||
| Transactiontype | |||||
| Version | "Version" | Date | Date of the latest update derived from the MS transaction. | Time | Time of the latest update In case of an empty medicationscheme, the "version" is derived from the MS transactiongetLatestUpdate method. |
| AuthorPatient | "Author" Name of the latest update, derived from the MS transaction->UpdatedBy as returned by the gatewaypatient as defined in the EVSg configuration. | ||||
| Nr of | MSESumehr transactions | The amount of | MSESumehr 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 shownunique in case an export exists already. | ||
| Output extension | Hard coded, depending on file type. |
For EVSg-exporter, each filename of transactiontype "SumehrDiarynote" exists out of:
<current-date>-<current-time>_<transactiontype>_<version>_<patient>_size-<nr of Sumehr transactions>Diarynote transactions>_<unique code>.<output extension>
| Name | Source |
|---|---|
| current-date | Date of performing the export (from 3.3.0 onwards) |
| current-time | Time of performing the export (from 3.3.0 onwards) |
| 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 |
| Diarynote 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.
...
| Name | Values | Meaning |
|---|---|---|
| transactionType | "medicationscheme" "sumehr" "diarynote" | EVSg-exporter supports 2 3 transactiontypes: medicationscheme, sumehr and sumehrdiarynote. Change this value accordingly. |
| 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. |
...