Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Uplifted to Published. Updates applied to: Background, Outline Plan and Summary of Change. Effective Date added.
Page Properties
id1

ID

RM234

Version

1.1.0.1

Type

Roadmap Item

Frameworks

Page Properties
id2

Title

GP Registration Service Integration with GP Systems

Description

GP Practice Solutions to automatically process GP Registrations from the Registration Service

Date Added

Standards and Capabilities

Patient Information Maintenance - GP, Interoperability Standard

Change Route

Managed Capacity - Minor/Patch uplifts

Change Type

New

Status

DraftPublished

Publication Date

TBC

Effective Date

TBC

Incentives / Funding

TBCNo

Incentive / Funding Dates

TBC

Background

...

N/A

Background

In 2022, NHS England introduced a digital solution for Patients to register with a GP surgery.

...

This change will focus on the Supplier receiving a Patient registration notification (Type 3 - Transfer) from National Events Management Service (NEMS) , which will in turn create and populate a record in the GP Practice Solution by pulling the information from the Personal Demographics Service (PDS). This change will also auto-populate the Patient’s health and lifestyle questions for those Patients.

Outline Plan

...

All Foundation Suppliers must be compliant against this specification by the Effective Date. Prior to go live Suppliers must have completed the Solution Assurance by NHSE. The Effective Date is reflective of the GP Mandate that comes into effect in October 2024, all Suppliers must be compliant by this date.

Suppliers should engage with the Register with a GP Surgery team at the earliest opportunity to facilitate collaboration.

During development, foundation Foundation Suppliers are required to participate in weekly status meetings to ensure collaboration and prompt resolution of issues.

...

Future phases will expand the user group by following assurance in the Register with a GP Surgery Service and will expand to include registrations that need human review, by creating a mechanism that allows GP administrators to review and accept or reject a registration request before automatically creating a local Patient Record. 

Summary of Change

Patient Information Maintenance - GP: MUST Epic added

E00XXX

E00681-

Automated GP

automated Patient Registration

As a Health or Care Professional

I want Patients to be automatically registered with my GP Practice

So that Patients are registered more efficiently

Acceptance

Criterion

criterion 1: automatically register a Patient

Given a GP Registration Request

event

signal is received

When the Patient’s

Demographics have been

Demographic Information is retrieved from the Personal Demographics Service (PDS)

Then the Patient is automatically registered

Acceptance

Criterion

criterion 2: automatically record Health and Lifestyle information in a Patient’s Electronic Patient Record (EPR)

Given

a

the Patient is registered

to

with the GP Practice

When the

Patient’s

Health and Lifestyle information for the Patient is received

Then the

Patient’s

Health and Lifestyle information is automatically recorded in

their

the Patient’s Electronic Patient Record (EPR)

Acceptance

Criterion

criterion 3: update

Pharmacy information in Electronic Patient Record (EPR) and Personal Demographics

Electronic Prescription Service (

PDS

EPS) Nominated Pharmacy for a Patient

Given

a

the Patient has provided Pharmacy information in their Health and Lifestyle information

When the

Patient’s

Health and Lifestyle information is automatically recorded in

their

the Patient’s Electronic Patient Record (EPR)

Then the Electronic Prescription Service (EPS) Nominated Pharmacy for the Patient is automatically updated

And the Patient’s Personal Demographics Service (PDS) record is updated

Acceptance

Criterion

criterion 4: view Health and Lifestyle information questions and answers in the Patient’s Electronic Patient Record (EPR)

Given

a Patient’s

the Health and Lifestyle information has been automatically recorded in

their

the Patient’s Electronic Patient Record (EPR)

When the Health or Care Professional selects to view the Health and Lifestyle information in the Patient’s Electronic Patient Record (EPR)

Then the Health and Lifestyle information questions and answers are displayed

E00XXX

E00681 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

National Events Management Service (NEMS)
and Health and Lifestyle event messages)Implement the receipt of the Health and Lifestyle messages inline with the FHIR Payload of Health and Lifestyle data document
  • signal)

  • Register with a GP Surgery Service Standard (to obtain Health and Lifestyle information)

  • Follow on system activity should be triggered as it would for a manual registration, including:

    • NHAIS HA/GP Links

    • GP2GP

Info

E00XXX - Supporting Information

For more information on how Patients will trigger this event, see

Multicast Notification Service (MNS): new Standard added

Multicast Notification Service (MNS)

Register with a GP

SurgeryNational Events Management

Service

(NEMS)

:

New

new Standard added

National Events Management Service (NEMS) v0.1.0

Register with a GP Surgery Service

Full Specification

...

...

...

Assurance Approach

  • NHSE will take a risk based approach to Test & Assurance

  • Suppliers will be asked to participate in weekly meetings to review progress, address issues and mitigate risks (Clinical, Functional and Non-Functional)

  • Risk Mitigations will be evidenced and provided to NHSE for sign-off (eg. evidence, explanation, screenshots and/or demonstrations). The risk log will explicitly state the applicable risk mitigations for the respective risk(s)

  • Suppliers are required to conduct and evidence user research to ensure the solution caters for user needs

  • NHSE will review Supplier testing scope, coverage and risk mitigation evidence

  • Suppliers will be asked to collaborate in test environments to verify integration and end-to-end tests

  • Suppliers will be asked to collaborate on a roll out plan and associated testing in live environments

  • Some functional assurance may be performed by the NHSE Solutions Assurance team, where deemed appropriate

  • NHSE will review Supplier's implementation delivers the expected business outcomes the expected business outcomes as stated in the supplied user stories