...
<date>-<time>_<transactiontype>_<patient>_<actor>_<action>_<input filename>_size-<nr of data entries>MSE transactions>_<output suffix>.<output extension>
...
<date>-<time>_<transactiontype>_<patient>_<actor>_<action>_<input filename>_size-<nr of data entries>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 data entries in the vault. |
...
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 |
...
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".
For EVSg-exporter, each filename of transactiontype "Medicationscheme" exists out of:
MS<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.
...