General

After initial installation, some examples are available to get familiar with the functionalities of the EVS, without the need for further configuration.

Usage

Functionality

The EVS allows a certain actor to perform, for a certain patient, a number of actions.

These actions are triggered by dropping certain input files in certain folders. EVS watches these folder(s), executes the action(s) and generates output.

Which patient?

The patient is determined by the used folder under "..\exe\interaction\input".

After initial installation, 1 patient named "katrien" is available:

Which actor?

The actor is determined by the used folder under "..\exe\interaction\input\<patient folder>".

After initial installation, 1 actor named "gp_van_gucht" is available:

Which files?

Any type of files, with any extension, can be dropped. They are considered as "input-files". EVS will, depending on the action folder, parse the files and extract the Kmehrmessage(s).

What is a Kmehrmessage?

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

EVS will only work with Kmehrmessages of Kmehr-standard 20120401. In this standard, 1 medicationschemeelement transaction and 0 or more treatmentsuspension transactions were considered as the business data of 1 "data entry".

All other data (among which the metadata) will be generated by the EVS and/or the Vitalink platform. As input the business data as depicted in blue here below will be used:

How is a Kmehrmessage identified?

For some actions, typically removing and updating data entries, the input Kmehrmessage need to have an identification.

There are 2 way to identify Kmehrmessages: by Vitalink ID and by EVS reference.

Identification by Vitalink ID

The Kmehrmessage can be preceeded by a Vitalink URI.

In the next example, this URI is /subject/83051839468/medication-scheme/32055/1. From this URI, EVS finally uses "32055" as unique ID.

Identification by EVS reference

An EVS reference is put in 1 (and only 1) free text field in the concerned Kmehrmessage.

Which actions?

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

Action "add"

This action will add a data entry to the vault for each Kmehrmessage found in all dropped files.

In the example below, 3 Kmehrmessages are dropped to be added to the vault:

Action "empty"

This action will remove all data entries from the vault. EVS will do this action once for each dropped file, without any parsing. 

In the example below, a newly created file will trigger emptying of the vault by removing all existing data entries:

Action "export"

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

In the example below, a newly created file will trigger exporting the contents of the vault by removing all existing data entries:

Action "removeID"

This action will remove the data entries identified by the URI in 

Action "removeREF"

Action "replace"

Action "updateID"

Action "updateREF"

Summary of the actions

Configuration

This paragraph explains how to configure the EVS for your own needs.

Configure a patient

Configure an actor

Appendix A: Folder structure EVS 1.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 the EVS.

Path								Reserved path	Reserved name	Explanation
<zip folder> default=EVS+version	\<root folder> default=EVS	\config								Everything that defines the behaviour of the EVS, configured as needed by the user.
			\actors
			\log4j
			\patients
		\exe
			\certificates
			\exports
			\interaction
				\input
					\katrien
						\gp_van_gucht
							\add
							\empty
							\export
							\removeID
							\removeREF
							\replace
							\updateID
							\updateREF
					\patient_template
				\processed
		\scenarios
			\basic_example
		\system
			\dependency-jars