Search loading...


Explore and Make use of Nationally Defined Messaging APIs


A care professional user of the Local Care Record (LCR) reviews a patient’s GP practice risks and warnings

Use case for a care professional user of the local care record reviews a patient’s GP Practice risks and warnings

Brief description

A patient is admitted to hospital. The clinician responsible for the care of that patient in the hospital needs to review their care history and their recorded current and past risks and warnings from the GP practice clinical system to assist in determining the appropriate care provision and support. They have access to the LCR, which shares clinical information relevant to the direct care of their patient from a variety of local hospital, community and GP organisations.

Use case justification

Currently, when a patient’s record is viewed in the LCR, their current and past risks and warnings from the GP practice clinical system are presented as a static HTML view from a third-party supplier, which is rigid and not in keeping with the needs of professionals, the design of the system’s UI – nor is it the preferred strategy for sharing patient information within the LCR landscape. Electronically consuming the FHIR®-compliant profiles for a patient’s current and past problems from their GP practice clinical system will allow the LCR to:

  • Share this data in a manner which is congruent and consistent with all other care partners.
  • Present the data in a manner which is appropriate for the care setting.
  • Share more relevant data, pertinent to the role of the professional involved and improve care delivery.
  • Present the data in a uniform and streamlined interface.
  • Provider a higher quality user experience.
  • Provide a higher fidelity audit record.

Primary actors

  • Care professionals
  • Clinicians
  • LCR subsystem

Secondary actors

  • Patient


  • At the point of direct care, during a consultation or care delivery setting, the professional/clinician is discussing the medical history with their patient.


  • Patient has been admitted onto the hospital’s Patient Administration System (PAS) and has gone through identification including retrieving their NHS Number.
  • The clinician has been advised by the local hospital’s system that their patient has information available within the LCR.
  • The clinician is logged into, and has a valid session with, the LCR.
  • The clinician has relevant access and permission to view the patient’s details in the LCR.
  • The patient has been registered within the GP practice clinical system and has data available for sharing with other clinical systems. Note: If no such data is available, it will not be possible to initiate the basic flow.
  • The GP practice clinical system exists within the Spine Secure Proxy (SSP).


  • On success:
    • The patient’s list of current and past risks and warnings is taken from the GP practice clinical system and presented in the LCR.
  • Guaranteed:
    • Access and data returned is recorded for auditing purposes.

Basic flow with alternative and exception flows

Step Description
Step 1 Clinician requests the current and past risks and warnings for the patient using the LCR interface.
Step 2 The LCR identifies the patient’s GP practice endpoint using Personal Demographics Service (PDS)/Spine Directory Service (SDS) lookup.
Step 3 The LCR requests the patient’s list of risks and warnings from their registered GP practice.
Step 4 Spine Security Proxy (SSP) checks organisation to organisation sharing agreement exists between requesting organisation (LCR) and the patient’s registered GP practice, and that the interaction (e.g. Get List of Risks & Warnings) is part of the sharing agreement.
Step 5 GP practice clinical system checks patient permissions and consent to share.
Step 6

The LCR receives the list of risks and warnings via the GP Connect service and presents the results to the clinician within the LCR user interface (UI).

The following information is returned and presented in the LCR UI, as a minimum, for all current and past risks and warnings:

  • Summary of the risk/warning (e.g. allergy/adverse reaction)

  • Identification code

  • Status of the risk/warning (e.g. registered/preliminary/final)

  • Verification status (if known)

  • Date and time of assessment

  • Clinician who performed the assessment

  • Reason for the assessment (if available)

  • Prediction of outcome for the patient, including likelihood, relative risk and justification

  • Mitigation instructions (if available)

  • Additional comments (if available)

(Further information may be utilised depending on the type of Risk & Warning, for example if the patient has adverse reactions or allergies, or intolerances).

For the current release this is limited to the identification of a patient allergies and adverse reactions. Other risks and warning are not in scope.

Step 7 The clinician then reviews the information presented and determines the best course of action in response to the information. This may involve requesting additional datasets from GP Connect to supplement the data already presented within this list.
Step 4a SSP sharing agreement between ‘to’ organisation and ‘from’ organisation doesn’t exist.
Step 4b Exception is reported in LCR user interface; user is directed to contact local service desk for resolution.
Step 5a The patient has not consented to the sharing of medical data from the GP practice.
Step 5b Exception is reported in the LCR user interface.
Step 6a A logic or integration exception occurs in the retrieval of data
Step 6b Exception is reported in the LCR user interface and is logged within the LCR’s exception-tracing database; user is directed to contact local service desk for resolution.

Use case diagram:

All content is available under the Open Government Licence v3.0, except where otherwise stated