| Table of Contents |
|---|
Abbreviations used
| Abbreviation | Meaning |
|---|---|
| SUT | Software Under Test |
| EVS | External Validation Tool, a reference test tool developed by imec's interop lab to facilicate testing for software vendors |
| MS | Medication Scheme |
| Sumehr | Summarised Electronic Healthcare Record |
| GP | General Practitioner |
Sumehr
...
...
Definition of tests for Sumehr is under construction.
Medication scheme
During the execution of the tests, EVSg EVS will often be used. Whenever this is the case, a file will be made available for use in EVSg EVS and the test itself will explain which action to use.
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 EVSgEVS. 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. Underneath READ and WRITE tests need to be executed in the Jira Test Management Suite where all test executions accompanied by their results, issues and screenshots are registered so a manual validation can be done by the HIE interop lab. The software packages who generate their own print version of the medication scheme (for patient or caregiver) need to execute some extra tests and can be found in this block at the bottom of this page. |
| # | Test | |
|---|---|---|
| S01 | Basic testing of the usage of Kmehr tables | |
| S02 | Testing of the required combinations of frequency and day | |
| S03 | Testing of the interpretation of treatment suspensions | |
| S05 | Testing of the visualisation of the specific times | |
| S06 | Testing of the calculation of the endmoment for administration | |
| S07 | Testing of the identification of the medication | |
| S08 | Testing of the visualisation of the begincondition and endcondition | |
| S09S09 | Testing of the behaviour after uploading an empty scheme | |
| S10 | Testing of the behaviour when using discontinuous schemes | |
| S11 | Testing of the behaviour with unusual transaction builds | |
| S12 | Testing of the interpretation of temporality | |
| S13 | Testing of the behaviour with conflicting medicationschemesS14 | Testing of the integration between connector, gateway and SUT |
| S15 | Testing which medication is shown with ' delivered ' medication | |
| S16 | Testing of the interpretation of fields with maximum characters | |
| S17 | Testing of the calculation of the daily medicationscheme | |
| S18 | Testing of the retention of the Kmehr Structure | |
| S19 | Testing of the sorting of the medicationlines | |
| S20 | Testing if the local print doesn't show the Vitalink logo | |
| medication lines | ||
| S21 | Testing of the synchronisation with Vitalink the vault. | |
| S22 | Testing of the calculation of the weekly medicationscheme |
All application that integrate with the regional vaults have to do these tests.
Read | Write |
The Read-tests are for |
...
applications that read medication schemes from |
...
the vault. |
All application that integrate Vitalink have to do these tests.
Write
The Write-tests are for |
...
applications that write medication schemes to |
...
the vault.
| ||||||||||||||||||||||||||||||||||||||||||||||||
| S05 | W-15 | Altering specific times | ||||||||||||||||||||||||||||||||||||||||||||||
|
Above testcases into categories:
Daily medication scheme
Every application that offers a daily medication scheme, have to perform these tests.
| # | ID | Test |
|---|---|---|
| S17 | R-10 | Daycalculation |
| S17 | R-15 | Daycalculation with Treatment Suspensions |
Weekly medication scheme
Every application that offers a weekly medication scheme, have to perform these tests.
| # | ID | Test |
|---|---|---|
| S22 | R-10 | Weekly scheme with daily medication |
| S22 | R-15 | Weekly scheme with medication every # days |
...
| Anchor | ||||
|---|---|---|---|---|
|
Every application that allows their local medication scheme (not synced with Vitalinka vault) to be shown to the patient, have has to perform these tests.
| # | ID | Test |
|---|---|---|
| S20 | R-10 | Generate print after adding new line |
| S20 | R-15 | Generate print after altering existing line |
| S20 | R-20 | Generate print after adding private line |
| S20 | R-25 | Generate print after changing existing line to private |
| S04 | R-10 | |
| S04 | W-15 | |
| S04 | W-20 | |
| S05 | R-10 | Visualisation of specific times |
| S05 | W-15 | Altering specific times |
| S09 | R-10 |