Frailty Status and Assessment (HP345)

Purpose:

This protocol will:

1. help to ensure that frailty awareness is optimised within your practice

What does it actually do?

If a patient is over 65, the protocol looks to see if the patient has had a code of mild, moderate or severe frailty entered last.  If this is the case, the user is alerted to the patients current frailty status and when this data was entered so they can review it or update it.  If there is no frailty assessment recorded the record is assessed to see if the patient has a moderate or severely scored eFI.  If this is the case, the user is alerted to consider undertaking a frailty assessment.  In all cases, the frailty status of the patient can be updated by double clicking on the alert shown.

What does it look like?

The alert looks like this:

If the user hovers over it, further information is shown:

 

or

If the alert is double clicked then the information can be updated:

System Dependencies:

This relies on users coding activity accurately within the clinical system.

System Trigger

System Trigger: Load a patient

Run mode: Always run 

Enable trigger for: All clinical prescribers

Fitting your practice

Your practice team need to know that you are setting this alert live in your system

How to get it

This protocol is an optional handy protocol, please submit a ticket to have this activated within your system

Support Information

Development Log

VERSION NUMBER 1.0.0

Published 2/10/24
Release notes: Initial build

• Related Articles

• 021 Data Quality: Coding

  This folder is part of 021 Data Quality Overview Outlier height/weight/BMI This group of searches are closely related. Outlier heights and weights have been defined as values which fall outside a normal range. Not every adult patient appearing in ...

• Shingles alert (HP062)

  Shingles Alert (HP062) Overview/Purpose This shingles alert is a protocol alert for EMIS Web, which has been designed to fill the void of a previously active EMIS authored alert. The alert is designed to show users that: The patient is eligible for a ...

• OneRecall Closing Support (PT00165)

  Purpose: When starting a consultation, this protocol will show which disease registers the patient is on, their latest relevant diary entry for QOF, their latest invitation, latest annual review, whether they have a diary entry marking a future ...

• Potential Cancer Alert (HP239)

  Purpose: This protocol will: Searches for common symptoms known to lead to cancer. Flags repeated occurrences over 12 months. Prompts clinicians to "think cancer" for timely diagnosis. What does it actually do? On saving the patient record, the ...

• Eligible for Diabetes Prevention Programme (HP267)

  Purpose: This protocol will: Increase the proportion of patients newly diagnosed with NDH that are referred to the Diabetes Prevention Programme What does it actually do? The protocol performs the following functions: Checks when loading the record ...