...

EVS can be launched via the "vault-uploader.cmd" batch file:

The behaviour of EVSg must EVS must be determined by passing some mandatory parameters. Instead of using the "vault-uploader.cmd" batch file, it is easier to use the example batch file "start EVS.cmd":

...

Any type of files, with any extension, can be dropped. They are considered as "input-files". EVSg willEVS will, depending on the action folder, parse the files and extract the MSE and TS transactions.

...

A Kmehrmessage is a part of the file that starts with <kmehrmessage ...> and ends with </kmehrmessage>. One file can contain 0 or more Kmehrmessages. One Kmehrmessage can contain 0 or more MSE and TS transactions.

EVSg EVS will work with Kmehrmessages of Kmehr-standard 20120401 and Kmehr-standard 20161201 as input.

All extra data needed for the communication with the gateway will be generated by the EVSgEVS. As input the data as depicted in the image below will be used:

...

In the next example, this REF is "===EVSREF:901===". EVSg EVS detects the reserved format  "===EVSREF:<any text>===" and finally uses "<any text>" as unique REF.

...

If multiple EVS REFs have been given for 1 MSE transaction, EVSg EVS will not execute the action and will raise an error.

...

Depending on the folder where the input-file is dropped, EVSg EVS will execute an action.

Action "add"

...

This action will export the contents of the vault, without any change to the vault itself. EVSg  EVS will do this action once for each dropped file, without parsing this file.

...

...

• the eHealth technical connector logs for EVSgEVS: ehealth_uploader*.log
• the eHealth technical connector logs for EVSgEVS-exporter: ehealth_exporter*.log
• the proprietary EVSg EVS log for EVSgEVS: evs_uploader.log
• the proprietary EVSg EVS log for EVSgEVS-exporter: evs_exporter.log
• a folder 'communication'

...

This folder contains all the requests and responses done by EVSg EVS when communicating with the gateway.

...

This paragraph explains how to configure EVSgEVS.

How to add a patient?

Extra patients can be added by creating files in the next folder:

...

Since EVS follows all the rules for eHealth and Vitalink, it is up to the user to make sure the proper eHealth dependencies (informed consent, therapeutic relation, ...) are set in function of the wanted behaviour.

...

...

Since EVS follows all the rules for eHealth and Vitalink, it is up to the user to make sure the proper eHealth dependencies (therapeutic relation, ...) are set in function of the wanted behaviour.

...

The next parameters can be passed when launching EVSgEVS:

Example of a parameterisation:

Appendix A: Folder structure

...

EVS 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 EVSgEVS.

Path							Reserved path	Reserved name	Explanation
EVSgEVS									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 EVSgEVS, configured as needed by the user.
		\actors							All the actors that can be used by EVSgEVS.
		\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 EVSgEVS.
	\exe
		\certificates							The certificates used in the actor configuration files.
		\exports							The folder were the EVS-exporter will put exported vault contents, see AppendixB:EVSexporter
		\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:

...

EVS-exporter

Besides the interaction provided by dropping files in the input folder, EVSg EVS offers as extended functionality the continuous monitoring of the vault contents. This functionality is provided by EVSgEVS-exporter.

Launching

EVSgEVS-exporter can be launched via the "vault-exporter.cmd" batch file:

The behaviour of EVSgEVS-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 EVSgEVS-exporter means that the vault contents of the patient "katrien" will be monitored.

Output

When EVSgEVS-exporter detects for the given patients a change in the vault contents, an export is executed. The export is also executed after initial launch.

...

The files contain the same as the files generated by EVSg EVS in the processed-folder, but the filenames differ.

For EVSgEVS-exporter, each filename exists out of:
MS_<version>_<patient>_<date>_<time>-<author>_size-<nr of MSE transactions>_<unique code>_<output suffix>.<output extension>

When the export fails, an error file will be generated, which is the same behaviour as for the folder-triggered export action of EVSgEVS.

Parameterisation

The next parameters can be passed when launching EVSgEVS-exporter:

...