...
This test will begin with uploading the medicationscheme through EVS. 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 input file.
W-10: Retaining Kmehr Structure
...
- Upload the EVS export file.
- Per medicationline, alter 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. This alteration can be something like adding a dot(.) to the field, but in many cases a valid value has to be given.
NOTE: for EVSREF 115, multiple fields have be checked and 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.
...
- TS-1: There is a medicationscheme with 16 medications and 2 treatmentsuspensions.
- TS-2: The export file that has been generated (after the alteration has been done) contains the new values in the same place as they can be found in the original input file. Per medicationline, only the field described in the 'Field' column of the 'Verification Table' has to be checked. NOTE: the actual place that stores the value can be found through the 'Tree Structure' column of the 'Verification Table'.
Verification Table:
This verification table will show the field that is being checked per medicationline and the tree structure of where this field can be found (and altered) in the Kmehrmessage.
...