Introduction

This document contains UX guidelines that all medical software that use the Vitalink medication scheme should comply with.

All software packages should also comply with the UX guidelines for every software package in Vitalink found here.

Terminology & Abbreviations

A list of the terminology used in this document can be found here.

Automatic questioning of Vitalink

Mandatory

x

Recommendations

x

Delivery of medication

Mandatory

x

Recommendations

x

One combined overview of all active medication

wireframes 2.1-2.4 en 3.1-3.4

Mandatory

It is important that the pharmacist has one overview of the active medication of the patient. Since both information about the active medication can be found in the local EMR and on Vitalink, the general practitioner wishes to see one combined overview. This overview must be shown on the first working screen of the application.

The pharmacist does not want to compare the information from the local EMR and the Vitalink medication scheme manually to determine what has changed. Comparing two different schemes is too time-consuming, too complex and can lead to mistakes. Methods where they can 'update' per line, 'upload' are not well understood. Rows in a table using different status icons can not be interpreted unambiguously.

The principle of a combined overview should be kept simple: provide only an indication 'what is on Vitalink'. 'What is in the local file'. Afterwards, the pharmacist can take further decisions around this.

It is important that this combined overview is displayed automatically, clearly indicating what has changed with respect to the local EMR, any alerts regarding medication lines that may be a problem, etc.
The purpose of this combined overview is that the pharmacist can see at a glance what has changed since the last time he uploaded the patient's medication scheme.

After obtaining the information from Vitalink, the pharmacist sees who has validated the last Vitalink medication scheme and when.

Concretely, the combined overview means the following:

• Draw attention to changes, new additions, inconsistencies in this combined overview.
  
  
• The list of medication stored in the local EMR can continue to exist, but the focus should be on the combined overview of information from Vitalink and information from the local EMR.
  
  
• Visualize clearly which medication line comes from where (Vitalink vs. local). A medication line from Vitalink has the Vitalink icon displayed. A medication line from the local EMR is displayed without an icon.
  
• Visualize changes in the following way:
  
  • Newly added medication with respect to the local EMR:
    
    • Emphasize this with a different background color so that attention is drawn to it (note: people with color blindness do see color shades, so for them it is also visible that there is a difference of color with the other lines).
  • Change in posology, intake moment, etc:
    
    • Cross out the medication line that has been replaced (in this way the pharmacist clearly sees what has changed).
    • Display the relevant medication line from the local EMR and the medication line from Vitalink in a clustered way (in this way the 2 'associated' medication lines are placed underneath each other, making comparison easier for the pharmacist). By keeping the unique URI once the mapping has been made, the connection between 2 'associated' medication lines can be better and faster verified next time. A 'reference algorithm' can be worked out for this.
  • Removal of prescribed medication:
    
    • Cross out the medication line that has been removed.

• The necessary changes (make the deleted medication line active again, change the modified posology to previous posology, etc) can be done by right-clicking on the relevant medication line or by clicking on an action button.
  
  • When the pharmacist does nothing, he/she agrees with the overview of the active medication that he/she sees (deleted medication will disappear, adapted posology will be retained and the previous posology will disappear, etc) and at a next opening of the EMR it is shown as a local scheme.
    
    
• Provide the opportunity to display an alert:
  
  • With, for example, 2x same type of medication but with a different product name. These will also be displayed under each other for clustering.
  • For example, an incomplete medication line.
  • Give, for example, a tooltip after a 'mouse-over' action for the relevant medication line, more information about why there is an alert (eg incomplete medication line).

Recommendations

• Show interactions between medication lines through an alert.

Create a Vitalink medication scheme with one click

Mandatory

x

Recommendations

x

Interactive/Dynamic medication scheme

Mandatory

x

Recommendations

x

Validate the Vitalink medication scheme

Mandatory

x

Recommendations

x

Visualization of the print version of the Vitalink medication scheme

Mandatory

It should be taken into account that the print version of the medication scheme for the patient may evolve in the future.

Depending on the needs of the patient, different types of displays may be necessary.

Each view will be built on the same dataset. This view should be able to be viewed on the screen by the pharmacist & possibly the patient during the consultation, or be printed to give to the patient.

• A display type can be selected on the combined overview of the medication scheme.
• It must be easy to alternate between the different types of view so that the pharmacist can decide in consultation with the patient which visualization of the medication scheme is best suited for the patient.

An exact implementation of this representation(s) will have to be offered by the software supplier.

Recommendations

• Ensure that the pharmacist can easily switch between the different display types.

• Keep the preference for a specific type of display for each patient, so that the pharmacist can know which type he / she should select during a subsequent consultation.

How to handle mistakes

x

Miscellaneous

x