Clinical, user and governance requirements that must be supported by the solution

User stories and logical data model

The GP Connect Requirements Catalogue for Access Record Structured Data contains the full set of business requirements that need to be met to support the retrieval of medications and allergy data in a structured format:

GP Connect Requirements Catalogue for Access Record Structured Data

The requirements are described as a set of user stories with separate acceptance criteria for the provider and consumer systems.

The logical data model identifies and defines the data items that are required by the business. Each logical data item is mapped to the FHIR® profile that will be used to transmit the data.

Use cases and business processes

The use cases define how and where there is a business need that can be supported by GP Connect structured data. They contain the following key components:

• Description
• Justification
• Process flow (including data requirements)

The level of detail varies from use case to use case.

• 3.1 Active checking of a prescription in unscheduled care

• 3.2 View GP current medication in Coordinate My Care

• 3.3 View patient-centric summary in Leeds Care Record

• 3.4 A care professional user of the Local Care Record reviews a patient’s GP practice medication information

• 3.5 Medicines reconciliation for acute care admissions

• 3.6 Out of hours GP accesses medications, allergies and problems

• 3.7 Admission of patient to the Yorkshire Centre for Eating Disorders

• 3.8 Community nurse reviews the GP record when they visit a patient

• 3.9 Dentist reviews the GP record when they treat a patient

• 3.10 Import patient record for acute care admissions (including medication reconciliation)

• 3.11 Import patient record for a private hospital

• 3.12 Referral to single point of access for mental health

• 3.13 Triaged by Clinical Assessment Service clinician after referral to Single Point of Access for mental health

• 3.14 Health visitor appointments during a child’s early years

• 3.15 School nurse appointments

• 3.16 Medications reconciliation following admission of patient to Leeds Teaching Hospital

• 3.17 Out of hours and extended hours GP appointments in a federated GP environment

• 3.18 Medications reconciliations prior to admission of patient to Becklin Centre

• 3.19 Community pharmacy managing patients

• 3.20 Community pharmacy giving vaccinations

• 3.21 A care professional user of the Local Care Record reviews a patient’s GP practice risks and warnings

• 3.22 Clinical Triage Platform consumes GP-held patient data

• 3.23 Midwife views patient record before visiting patient

Clinical engagement

To help ensure that the functionality being developed will be able to support a wide range of clinical uses, GP Connect has engaged with a range of clinicians and other stakeholders to get an understanding of how that data may be used and what is required to support its use.

This engagement has included:

• Hospital consultants and doctors
• Hospital pharmacists and technicians
• Mental health nurses
• Mental health pharmacists and technicians
• Mental health point of access centre
• General practitioners
• Community pharmacists
• Midwives
• Health visitors
• Health system suppliers
• Commissioning support units
• Hospital trusts

The feedback from these stakeholders has been used to develop the business use cases, user stories and the logical data model. These will form the basis of the technical specification and will be used to assure that the GP Connect API meets the needs of the business.