Search loading...


Explore and Make use of Nationally Defined Messaging APIs



Use case for problems

Brief description

A professional user of the Local Care Record (‘care professional’) needs to review a patient’s GP practice information:

  • current and past problems

A patient is admitted to hospital and the clinician responsible for the care of that patient in the hospital needs to review their care history, with current and past problems in the GP practice clinical system, to assist in determining the appropriate care provision and support. They have access to the Local Care Record (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 problems 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 user interface (UI), nor is it the preferred strategy for sharing of 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
  • provide 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 Security Proxy (SSP)


  • On success:

    • the patient’s list of current and past problems 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 Problems' for the patient using the LCR interface.
Step 2 The LCR identifies the patient's GP practice endpoint using PDS/SDS lookup.
Step 3 The LCR requests the patient's 'List of Problems' 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 (for example, Get List of Problems) 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 Problems' 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 problems:

  • Brief summary of the problem (for example, Asthma)

  • Onset date/time

  • Abatement date/time (if relevant)

  • Status of the problem (for example, confirmed/refuted/provisional)

  • Subjective severity of the problem

  • Problem code(s)

  • Anatomical location (if relevant)

  • Details of formal assertion/confirmation (for example, date/time, clinician asserting)

  • Formal problem-specific assessment details (for example, stage)

  • Supporting evidence (for example, manifestation/symptom codes)

  • Additional notes/annotations

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 data sets 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.

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