...
| Field # | Field | Expected value | |||||
|---|---|---|---|---|---|---|---|
| 1 | Name, first name & NISS number of the patient | As registered in the patient file of PATIENT_X within the SUT | |||||
| 2 | Identification of the care provider who changes the medication scheme | Details of ACTOR_B. As returned by Vitalink, see M. Concept: Author of the medication scheme | |||||
| 3 | Date and hour of last change | The moment on which ACTOR_B uploaded the EVS file. The exact date + time is also available in the file name of the EVS Exporter | |||||
| 4 | identification of the care provider who prints the medication scheme (details of the pharmacy + owner) | Details of ACTOR_A. If the actor is a pharmacist, then also show the details of the pharmacy. If the actor is a person within an organisation, then also show the details of the organisation. | |||||
| 5 | Date and hour of print | The moment on which ACTOR_A printed the medication scheme.
| |||||
| 6 | Medication scheme version | The version of the medication scheme |
...
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 either this EVS file (EVSEVSc) with EVS-action removeREF, or by uploading this EVS file (EVSgEVS) with EVS-action updateschemeREF.
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
...