HP038 Subject Access Status SAR

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 it do?

The protocol provides a clear and structured workflow for monitoring, updating, and completing SARs. It flags overdue requests and ensures timely communication with patients regarding their data access requests.

Why is it important?

This tool supports legal compliance with the General Data Protection Regulation (GDPR) and the Data Protection Act 2018. It reduces the risk of missing deadlines, enhances patient trust, and ensures proper record-keeping.

What does it look like?

See below screenshots which shows examples of the protocol in use:




System Dependencies

This protocol relies on accurate recording and coding of Subject Access Requests in your system.
  1. Required codes: SAR request initiation, SAR status updates, SAR completion.
  2. Staff training: Clinicians and administrative staff must understand the importance of correct coding and use of this protocol to ensure compliance.

System Triggers

System trigger: Manually launched

Change management considerations

Fitting your practice 
Staff need to be made aware that this protocol exists and how to access it. The protocol can be found in the OneLauncher Admin under the "Coding Team Tools" option.
Best Practices
To integrate this protocol effectively:
  1. Review your current workflows for managing SARs.

How to get it

This protocol is automatically installed in your system. 


    • Related Articles

    • 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: On loading the patient record the system is ...

    • 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 ...

    • How to access the Referral Tree

      Once the PCIT Referral Tree has been installed into your site, you'll be able to access it through the OneLaunchers. The option should be available on either the OneLauncher Prescriber, OneLauncher Non-Prescriber or the OneLauncher Admin. 1. From a ...

    • Same day diabetes foot access (HP012)

      Purpose: This protocol will trigger when booking appointments for diabetics with recorded increased foot risk to ask the receptionist to enquire about whether it is a foot problem that needs looking at so that the appointment can be appropriately ...

    • 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 ...