You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Scope

This page contains the Kmehrmessages for testing the behaviour of the SUT when transactions are put in the vault that do not conform to the recommended build of a transaction.

Instructions for EVS use:

IMPORTANT: This test has to be performed using the new version of EVS: EVSg

This EVS export file contains all the transactions used for this test.

Before starting the test, this export file should be uploaded using the EVS-action REPLACE and your own test patient.

The EVS parameter writeAsIs must be set to false.


Description:

After reading the medication scheme, the results can be verified in the SUT.

Depending on the SUT, the handling of the medication scheme may vary slightly.


R-10: Reading Gateway Validation Fails

Before testing this, make sure you have uploaded the medication scheme.

Verify the following:

  • The SUT keeps functioning in a normal fashion.
  • Either there should be no medications in the UI or print, or all 24 medications are present. The SUT should not display only a set of the medicationlines.
  • The user should be able to notice that there is an abnormality with his medication scheme.


W-15: Writing Gateway Validation Fails

Before testing this, make sure you have performed the 'R-10: Reading Gateway Validation Fails' test.

Alter every medication by putting an extra dot (.) in the 'Instruction For Patient'. Then sync the altered medication scheme with Vitalink.

Verify the following:

  • The SUT should have succesfully altered the medication scheme.
  • Either there should be no medications in the UI or print, or all 24 medications are present. The SUT should not display only a set of the medicationlines.
  • The user should be able to notice that there is an abnormality with his medication scheme.
  • No labels