e

Table of Contents

Intro

EVS allows to manipulate vault contents using specific actors and specific patients, manually of based on previously exported vault contents.

...

Name	Values	Meaning
writeAsIs	true\|false	false: All patient data from the source Kmehrmessage will be replaced by the correspondign data of the used input patient. Since the Kmehr data model is used for this transformation, it is possible that other Kmehr structure elements are slightly changed too. true: The Kmehrmessage will be sent to the vault untouched. Use this when really no manipulation on the source Kmehrmessage is desired.
exportAfterUpload	true\|false	true: Each action, excepted "export" itself, should be followed by an export. false: No export is needed after execution of the triggered action.
validateExportAfterUpload	true\|false	true: Each action 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. This EVS functionality is still under development!

Appendix A: Folder structure EVS 1.x.y

...

Path							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

...

Name	Source
Subject version	"Version" from FetchDataEntriesResponse->Node as returned by the connector: See http://www.vitalink.be/sites/default/files/atoms/files/Safe_Cookbook_API_v4%202.pdf When the Kmehrmessage is returned by the Vitalink Gateway, this version can be found in folder/transaction[content/cd[text()='medicationscheme']/version.
Node version	"Version" from FetchDataEntriesResponse as returned by the connector. When the Kmehrmessage is returned by the Vitalink Gateway, this version can be found in folder/transaction[content/cd[text()='medicationscheme']/version.
Date	Date	Today.
Time	Now.
Patient	Name of the patient as defined in the EVS configuration.
Nr of data entries	Number of data entries in the vault as as returned by the connector.
Unique code	Code making the filename unique in case multiple exports where done in 1 second.
Actor	"Person" from FetchDataEntriesResponse->UpdatedBy as returned by the connector.
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.

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

...

The next parameters can be passed when launching EVS:

Name	Values	Meaning
transactionType	medication-scheme	This parameter is for future use. For the moment only 1 transaction type is supported.
patients	name(s) as defined in EVS configuration, comma separated	These is(are) the patient(s) that will be used for exporting.
actor	name as defined in EVS configuration	These 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.
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. This EVS functionality is still under development!