Impact on availability of relevant patient information at point of need – specifically allergy information
Our network members discussed the need to understand useable data (which is not free text but coded accurately) for use e.g. in dashboards to support clinical decisions and prioritisation. They wanted to be able to develop metrics to capture information relating to specific patients. Using this, they ideally wanted not just a ‘read-only’ alert warning but something that forces the user to do something tangible.
What peers in the network found
Managing free text options
Many recommend disallowing free text, or that it’s best to build in an alert if someone uses a free text allergy to inform them to check. Think about you can quick picks/fields to pick out common reactions
Build your reports and publicise them
Show what the system has prevented to build up enthusiasm and support for its potential
Top tips from the network
- Confusion between what constitutes an allergy vs a serious adverse drug reactions that a patient has.
- Patient preferences – find a way to record these preferences that cross encounter i.e. dislike of banana flavour, without need to repeat on next admission.
- Display of allergies and preferences information – in some systems it’s difficult to display at front end in suitable manner. Important to ensure correct display of information in the immediate discharge letter.
- Be wary of alert fatigue