Use Case - Revoke a Relationship

Proxy Revocation

User Story Summary (Clinical Overview) As a clinical professional,
I need to be able to revoke a proxy relationship where I deem necessary,
So that access remains safe and appropriate.

As a patient with capacity,
I need to be able to revoke a proxy’s access to my records and services,
So that I am empowered to take decisions about who is permitted to access services and make healthcare decisions on my behalf.
Actors (Role) Proxies, Patients, Clinical professional / General practitioner
Frequency of Use Whenever there is a change in circumstances that affects a patient’s wishes or the safety/appropriateness of the relationship.
Triggers
  • Trigger 1: A clinical professional revokes access using a clinical system.
  • Trigger 2: A patient revokes proxy access using a patient-facing service.
Pre-conditions
  • An authorised relationship exists in the National Proxy Service between a given proxy and patient.
  • The patient or clinical professional has determined that the proxy relationship should no longer be in place.
  • Trigger 1: The clinical professional has authenticated in their clinical system.
  • Trigger 2: The patient has authenticated with a patient-facing service that supports proxy revocation.
Post-conditions
  • The proxy relationship has been revoked and can no longer be used for accessing services.
  • A reason for revocation has been recorded for audit purposes.
Main Course Trigger 1:
  1. A clinical professional has determined that access to a patient’s services is no longer safe or appropriate for a given proxy.
  2. The clinical professional queries their clinical system to identify the proxy relationship in question.
  3. The clinical professional revokes the proxy relationship.
Trigger 2:
  1. A patient has determined that they no longer wish a given proxy to be able to access services on their behalf.
  2. The patient uses the patient-facing service to identify the proxy relationship in question.
  3. The patient revokes the proxy relationship.
  4. A confirmation notification is sent to the patient.
Alternate Course The removal or amendment of individual permissions in a clinical system is outside the scope of this use case and is a local concern. Revocation should result in unilateral removal of access.
Exception Patient is not sufficiently verified or authenticated.