...
For this test, the visualisation and structure itself is out of scope. It is, however, important that no data is lost and that the content of the medicationscheme is interpreted as intended by the uploader of the medicationschemethe medicationscheme within the SUT is out of scope.
This test will begin with uploading the medicationscheme through EVS. Then, the content of that medicationscheme will be checked on the SUT. After that, the user will alter a certain field in each medicationline (the test will explain which field to alter) and sync to Vitalink. Lastly, the EVS action EXPORT will be done, which will generate an export file containing the Kmehrmessages. There, the structure of the Kmehrmessage will be checked, to see that this has remained the same as the original upload file.
W-10: Retaining Kmehr Structure
Preparation:
- Upload the EVS export file.
- Per medicationline, add a dot(.) to the field which can be found in the 'Field' column in the 'Verification Table'. For example, for EVSREF 100, the administrationunit field should be altered.
- Sync to Vitalink.
- Use the EVS action EXPORT on the patient that was used for this test.
- In the processed map of EVS, a file should be generated with an .exp extension. This file should be opened.