Introduction

...

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

What is a Kmehrmessage?

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 will work with Kmehrmessages of Kmehr-standard 20120401 and Kmehr-standard 20161201 . It will automatically convert Kmehrmessages of Kmehr-standard 20120401 to Kmehr-standard 20160401.as input.

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

How is a "medication"

...

 identified?

For some actions, typically removing and updating "medications", the medication that should be changed needs to have an identification. Those medications are expressed as MSE transactions in the Kmehrmessage. These MSE transactions are identified by using an EVS reference.

...

• an MSE transaction with EVS REF not yet existing in the vault will be added to the vault, together with all TS transactions which are linked with this MSE transaction
• an MSE transaction with EVS REF already existing in the vault will cause an update if any difference between the input-transaction and vault-transaction is found
• all MSE transactions without corresponding EVS REF in the input file will be removed from the vault
  
  

If the input-file contains MSE transactions with EVS REFs that are not unique, the action will not be executed and an error will be thrown.

...