...
| 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 the vault, 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
- Change the posology of one of the medication scheme elements in the SUT. Save the changes but don't upload the changes to Vitalinkto the vault
- 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 the vault yet, they should not be reflected in the patient print yet.
...