Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The tests are generally split between reading tests and writing tests, each labeled with 'R-' and 'W-' respectively. Whenever a 'W-' test is finished, it is advisable to perform an EXPORT action with EVSg. This will generate several files in the processed folder and among these files is the validation file (with a .val extension). This file should not contain any validation fails.

Info

If something is incorrect in these scenarios (e.g. medicationscheme doesn't work), send us an email at imec.hie@imec.be with the necessary information.
We'll sort it out as soon as possible.


#Test
Link
S01Basic testing of the usage of Kmehr tables
EVS_Scenarios_S01_Basic_test
S02Testing of the required combinations of frequency and day
EVS_Scenarios_S02_Combined_Use_Of_Frequency_And_Day
S03Testing of the interpretation of treatment suspensions
EVS_Scenarios_S03_Treatment_Suspensions
S04Testing of the medication scheme header information
EVS_Scenarios_S04_Medication_Scheme_Information
S05Testing of the visualisation of the specific times
EVS_Scenarios_Visualisation_Of_Specific_Times
S06Testing of the calculation of the endmoment for administration
EVS_Scenarios_Calculated_Endmoment
S07Testing of the identification of the medication
EVS_Scenarios_Medication_Identification
S08Testing of the visualisation of the begincondition and endcondition
EVS_Scenarios_Beginconditions_And_Endconditions
S09Testing of the behaviour after uploading an empty scheme
EVS_Scenarios_Behaviour_Empty_Scheme
S10Testing of the behaviour when using discontinuous schemes
EVS_Scenarios_Discontinuous
S11Testing of the behaviour with unusual transaction builds
EVS_Scenarios_Validation_Fails
S12Testing of the interpretation of temporality
EVS_Scenarios_Temporality
S13Testing of the behaviour with conflicting medicationschemes
EVS_Scenarios_Collision
S14Testing of the integration between connector, gateway and SUT
EVS_Scenarios_Gateway-Connector
S15Testing which medication is shown with 'delivered' medication
EVS_Scenarios_Intended_VS_Delivered_Medication
S16

Testing of the interpretation of fields with maximum characters

EVS_Scenarios_Maximum_Length
S17Testing of the calculation of the daily medicationscheme
EVS_Scenarios_Day_Calculation
S18Testing of the retention of the
Kmehr StructureEVS_Scenarios_Retaining_
Kmehr
_
Structure
S19Testing of the sorting of the medicationlines
EVS_Scenarios_Sorting
S20Testing if the local print doesn't show the Vitalink logo
S21Testing of the synchronisation with Vitalink
S22Testing of the calculation of the weekly medicationscheme

Read

The Read-tests are for application that read medication schemes from Vitalink.

All application that integrate Vitalink have to do these tests.


Write

The Write-tests are for application that write medication schemes to Vitalink.


Daily medication scheme

Every application that offers a daily medication scheme, have to perform these tests.


Weekly medication scheme

Every application that offers a weekly medication scheme, have to perform these tests.


Local print

Every application that allows their local medication scheme (not synced with Vitalink) to be shown to the patient, have to perform these tests.