...
The Kmehrmessage can be preceeded by a Vitalink URI.
The Vitalink ID can not be chosen, but are dynamically generated by the Vitalink platform when adding new data entries. As a consequence, they are not deterministisc and are hard to use in when defining scenarios.
In the next example, this URI is /subject/83051839468/medication-scheme/32055/1. From this URI, EVS finally EVS detects the reserved format "/subject/###########/medication-scheme/32055" and 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.
The EVS reference can be freely chosen, and support the definition and execurion of scenarios.
In the next example, this REF is "===EVSREF:901===". EVS detects the reserved format "===EVSREF:###===" and finally uses "901" as unique REF.
Which actions?
Depending on the folder where the inout-file is dropped, EVS will execute an action.
...