Table of Contents |
---|
Introduction
The wireframes below have been created based upon observations in several Flemish hospitals.
The observations were based on the use of the home medication throughout the hospital practice.
Note |
---|
Please note that the wireframes below illustrate only an example of the workflows described in the use cases. They do not represent all features of the hospital software, nor all information. |
Wireframes
1.Ambulant Visit
AnchorUX Ambulant - Basic Flow UX Ambulant - Basic Flow
Basic flow: Home medication EHR section is already in sync with Vitalink
UX Ambulant - Basic Flow | |
UX Ambulant - Basic Flow |
Example when the system is still working on the sync with Vitalink.
- In this wireframe, the home medication of the local EHR is visible.
- It is visible that the system is syncing with Vitalink (upper right corner).
- This is done automatically, without interference of the healthcare professional.
- It is important that the automatic sync starts when opening the EHR of the patient (and not only when opening the medication module of the EHR).
- The healthcare professional should be aware that the system is syncing with Vitalink. Therefore it is recommended to use an icon and/or textual label expressing what the system is doing.
- The sync can only be done with Vitalink if IC & circle of trust are OK.
- While syncing, the healthcare professional can do all actions in the medication module of the hospital software (add new medication, re-prescribe, transfer to admission medication, ...).
- It is possible to validate the active medication list of the local EHR; but preferably this is only done when the Vitalink data are synced with the medication data of the local EHR.
- The automatic import and analysis of the information from the Vitalink medication scheme should take a minimum of time. Preferably 4 to 6 seconds or less; with a maximum of 10 seconds.
Example when the sync with Vitalink is completed.
- Here, it is visible that the sync with Vitalinkis completed (upper right corner). The healthcare professional can be informed about this by:
- Using a meaningful icon, combined with another icon expressing a status.
- Information about the latest validation date of the Vitalink medication scheme (in this case: 29.05. 2019, 19:30).
- If the user wants to obtain more information (e.g. validated by, sync info, version number, ...) or wants to do manually a new sync with Vitalink, this information can be provided via a tooltip when moving over this status information. For example:
Example when the latest validation was done by a general practitioner.
Example when the latest validation was done by a specialist in an hospital (only the hospital will be visible).
- When the sync with Vitalink isn't possible, it should be indicated that the sync couldn't be done successfully (status information).
- When doing a mouse over, more information about the failure should be provided via a tooltip.
- It should be possible to initiate a new sync with Vitalink.
When there isn't a Vitalink medication scheme for the patient, this should be indicated.
It should be possible to create a Vitalink medication scheme for the patient via 1 click.
When checking the check box in the example below, the medication list that is validated by the healthcare professional will be uploaded to Vitalink at the end of the contact.
- In the examples above, each time Vitalink is addressed as external source.
- If Réseau Santé Wallon is addressed as external source, the RSW icon & textual label should be used.
- If Réseau Santé Bruxellois is addressed as external source, the RSB icon & textual label should be used.
- When the sync with Vitalink is done, it is visible in the wireframe that there is no difference between the home medication of the local EHR and the medication on Vitalink.
- If there would be a difference, the medication lines coming from Vitalink would be highlighted & labeled (cfr. next wireframe).
AnchorUX Ambulant - Variant 1 UX Ambulant - Variant 1
Variant 1: There is no Home Medication data in the EHR
UX Ambulant - Variant 1 | |
UX Ambulant - Variant 1 |