Restructure PDS Record Change event requirements
ID | RM238 |
|---|---|
Version | 1.0.0 |
Type | Roadmap Item |
Frameworks |
Title | Restructure PDS Record Change event requirements |
|---|---|
Description | Restructuring of the PDS Record Change event requirements to make them clearer for new Suppliers. |
Date Added | May 9, 2024 |
Standards and Capabilities | Patient Information Maintenance - GP, Personal Demographics Service |
Change Route | Managed Capacity - Minor/Patch uplifts |
Change Type | Uplift |
Status | Draft |
Publication Date | May 23, 2024 |
Effective Date | Jun 6, 2024 |
Incentives / Funding | No |
Incentive / Funding Dates | N/A |
Background
As part of the RM135 - Personal Demographics Service Record Change Event Roadmap Item, new requirements were introduced to ensure existing Solutions subscribed to and actioned these PDS Record Change event messages appropriately.
Improvements to how the requirements are documented have been identified to help New Market Entrants better understand what is required and so these requirements are being restructured.
Outline Plan
No work is required from existing Suppliers. The requirements will be restructured on the Effective Date.
Summary of Change
Patient Information Maintenance - GP: MUST Epic added |
E00XXX - automatically update Patient details for received PDS Record Change notificationsAs a Health or Care Professional I want to receive notifications when PDS information for a Patient is updated by the Patient So that the information held for Patients by my Healthcare Organisation can be automatically updated Acceptance Criterion 1: automatically update mobile phone number for PatientsGiven a PDS Record Change notification has been received for a Patient And the source of the change is specified as the Patient in the PDS Record Change notification When the PDS Record Change notification includes a mobile phone number change for the Patient Then the Patient’s mobile phone number is automatically updated Acceptance Criterion 2: automatically update email address for PatientsGiven a PDS Record Change notification has been received for a Patient And the source of the change is specified as the Patient in the PDS Record Change notification When the PDS Record Change notification includes an email address change for the Patient Then the Patient’s email address is automatically updated E00XXX - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
|
National Events Management Service (NEMS) Standard: MUST requirement added | |||
GP Suppliers | NEMS02 | Subscribe to and implement the receipt of PDS Record Change event messages inline with the latest specification version. | MUST |
Personal Demographics Service (PDS) Standard: MUST requirement removed | ||
All Suppliers | Implement and maintain PDS Record Change Event in line with the latest version specification. See National Event Management Service (NEMS) for further information. | MUST |
National Events Management Service (NEMS) Reference Page: retired |
Full Specification
National Events Management Service (NEMS) v0.1.0
The updated Patient Information Maintenance - GP Capability and Personal Demographics Service Standard will be added at a later date. Proposed changes can be viewed in the Summary of Change above.
Assurance Approach
N/A