...
| Note |
|---|
All MS transactions are ignored as input. |
Where to put the acceptation-environment-token from Vitalink ?
Since EVS went opensource we decided to not use a hard-coded acceptation-key anymore but a 'replaceable' key in the config which is read at run-time.
This key can be added in the (to be used) actor configuration file at the location as described hereabove in the topic 'Which actor?'.
Example:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<authenticationConfiguration>
<evs>
<type>fallback</type>
<certificates>
<certificate>
<type>identification</type>
<path>..\config\certificates\SSIN=[INSS+SPECIAL CODE].acc-p12</path>
<password>[PW]</password>
</certificate>
</certificates>
</evs>
<ehealth>
<entry>kmehr.hubservicev3.software.id.local.value.1=[VITALINK ACC-KEY]</entry>
<entry>user.inss=[INSZ]</entry>
<entry>user.nihii=[NIHII]</entry>
<entry>user.firstname=[FIRSTNAME]</entry>
<entry>user.lastname=[LASTNAME]</entry>
<entry>careprovider.inss=${user.inss}</entry>
<entry>careprovider.nihii=${user.nihii}</entry>
<entry>careprovider.firstname=${user.firstname}</entry>
<entry>careprovider.lastname=${user.lastname}</entry>
... |
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 either 0 or more MSE and TS transactions, or it can contain 0 or more Sumehr transactions.
...