...
The EVS parameter writeAsIs must be set to false.
R-10: General test of medication scheme information
- Upload this EVS export file for your patient with an actor of your choice, let's call this actor ACTOR_B and your patient PATIENT_X.
- Log on to the SUT with a different actor, let's call this actor ACTOR_A
...
If above fields appear anywhere else in the SUT, verify that the values correspond to the ones displayed on the patient print
W-15: Medication scheme information after local modification
- Execute test "General test of medication scheme information" and save the patient print somewhere. Let's call this print PRINT_1
- Change the posology of one of the medication scheme elements in the SUT. Save the changes but don't upload the changes to Vitalink
- Generate the patient print again. Let's call this print PRINT_2
...
Only the "Date and hour of print" field should have changed in PRINT_2 when compared to PRINT_1. All other fields in the header should not have changed. Since changes have not been uploaded to Vitalink yet, they should not be reflected in the patient print yet.
W-20: Medication scheme information after removal of medication
Execute test "General test of medication scheme information" and save the patient print somewhere. Let's call this print PRINT_1
Note title Important Make sure that ACTOR_B is the author of the medication scheme in PRINT_1, and not ACTOR_A
Remove one of the medication elements from the medication scheme in the vault, by uploading this EVS file with EVS-action removeREF.
Note title Important This EVS action must be executed by:
- either a third actor which is different from ACTOR_A and ACTOR_B (PREFERRED)
- or ACTOR_A (if you don't have an actor other than ACTOR_A and ACTOR_B)
Let's call the actor who performed the remove action ACTOR_C
- Generate the patient print again. Let's call this print PRINT_2
...