Carer status [HP014]

Carer status [HP014]

Type: Protocol Alert

Purpose

To drive awareness of carer status - both if the patient has a carer, and if they are a care themselves.

What does it actually do?

The protocol performs the following functions:
  1. On loading the patient record the system is queried to see if the patient is coded as a carer, or that they have a carer
  2. If they do, an alert is shown providing that information to the user
  3. If the alert is double clicked, a template launches where this information can be added to or updated.

What does it look like?

This is the alert that is shown (both options showing for this patient):



When the user hovers over this, this kind of information is shown:




When the user double clicks the alert they are taken to this template to record further details:


System Dependencies:

This protocol is dependent on accurate coded information within EMIS web, contemporaneously recording carer status. 

System Trigger

System Trigger: Load record and update record

Run mode: Always run 

Enable trigger for: All clinical job categories 

Fitting your practice

Your teams need to be aware that this alert may show, and how to double click the alert to take action

How to get it

This is a base handy protocol and will automatically be installed in your system.  

Support Information

Development Log

VERSION NUMBER 2.0.0

Published 1/4/22
Release notes:
Initial release



    • Related Articles

    • Subject Access Requests Status (HP038)

      Subject Access Requests Status (HP038) Overview/Purpose This protocol assists staff in tracking the status of Subject Access Requests (SARs), ensuring compliance with data protection laws and improving the efficiency of request management. What does ...
    • Frailty Status and Assessment (HP345)

      Purpose: This protocol will: 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 ...
    • Consent to Share Info Status (HP041)

      Purpose: When starting a consultation, this protocol will highlight if you have data sharing recorded for your patient, including when this was given. It will also ask you if you want to update this information so it is current. Key features Allows ...
    • OneStroke (HP174)

      Overview/Purpose This protocol generates a summary overview of observations and findings related to the management of a patient on the Stroke/TIA register. Resource type HP174 is a Base Handy Protocol. These means all users will have this by default. ...
    • OneDiabetes (HP175)

      Overview/Purpose This protocol generates a summary overview of observations and findings related to the management of a patient on the diabetes register. Resource type HP175 is a Base Handy Protocol. These means all users will have this by default. ...