...
In the example below, 3 transactions are dropped to be added to the vault: KM->transaction(s)
Action "export"
...
If no EVS REF exists, the new EVS REF is put in the instructionforpatient field. Moet "New textdocument.txt" worden
Action "replace"
...
In the next example, after processing the next 3 input files, the vault contains 2 transactions. KM->transaction(s)
Action "updateschemeREF"
This action will update the complete contents of the vault, based on the input file compared with the current contents of the vault. KM->transaction(s)
The next actions will take place:
...
If for some reason the action fails, an error output file is generated: KM->transaction(s)
| Name | Output suffix | Extension | Description | Remarks |
|---|---|---|---|---|
Error file | - | .err | The report containing the error. | The content of the error file will identify the problem. |
...
- the eHealth technical connector logs for EVSg: ehealth_uploader*.log
- the eHealth technical connector logs for EVSg-exporter: ehealth_exporter*.log
- the proprietary EVSg log for EVSg: ivlab-automation evs_uploader.log
- the proprietary EVSg log for EVSg-exporter: ivlab-automation evs_exporter.log
- a folder 'communication'
File browser creenshot met wat voorbeelden
Communicaton-folder
This folder contains all the requests and responses done by EVSg when communicating with the gateway.
File browser creenshot met wat voorbeelden
Configuration
This paragraph explains how to configure EVSg.
...