...

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.

How to add an actor?

Extra actors 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 (therapeutic relation, ...) are set in function of the wanted behaviour.

Parameterisation

The next parameters can be passed when launching EVS:

...

Path							Reserved path	Reserved name	Explanation
EVS									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 EVS, configured as needed by the user.
		\actors							All the actors that can be used by EVS.
		\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 EVS.
	\exe
		\certificates							The certificates used in the actor configuration files.
		\exports							The folder were the EVS-exporter will put exported vault contents, see EVS_Manual
		\interaction
			\input
				\katrien
					\gp_van_gucht
						\add
						\empty
						\export
						\removeID
						\removeREF
						\replace
						\updateID
						\updateREF
				\patient_template
			\processed
	\scenarios
		\basic_example
	\system
		\dependency-jars

Appendix B: EVS-exporter

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

...