| Page Properties | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Background
The objective of PCRM is to migrate primary care registration management functionality onto Spine in order to support the transformed primary care support services in England and enable the decommissioning of the National Health Application and Infrastructure Services (NHAIS).
The first phase of this transformation introduces some changes to GP Links messaging and, in order to support Patient registration on PDS, will also introduce Postcode Access File (PAF) validation at source to ensure that address updates are consistently applied to Spine.
Outline Plan
Whilst PCRM doesn’t have an agreed go-live date at present (due in part to dependencies on other programmes like Cervical Screening), ensuring that these changes are implemented as early as possible will aid with a smooth transition and help improve data quality before the switch.
Summary of Change
GPSS to implement address integrity checking against PAF each time an address is amended on the GP System.
Assurance Approach
Initiation workshop with the supplier and NHS Digital stakeholders (Programme, SA - Functional, Non-Functional, Clinical Safety, IG and Service Management) - Activity
Supplier Implementation Plan, Release Scope definition (RSD) document and an RTM (Requirements Traceability Matrix) submissions by the supplier. An initiation workshop with an appropriate agenda may negate the need for a RSD and Supplier Implementation Plan - Deliverable
Supplier technical design documentation (if required) - Deliverable
Test environment setup for testing in the path to live environment - Activity
Test outputs (test scripts, test results, test messages etc) from the suppliers testing that they meet the PCRM requirements through their own testing and test results of any specific NHS Digital authored test(s) which we might mandate suppliers to execute – Deliverable.
WebEx / face to face sessions for Suppliers to demonstrate areas which we deem as higher risk and/or areas which are more appropriately evidence through demos - Activity
Clinical Safety assurance and Clinical Safety Hazard logs and Clinical Safety Report – Deliverable and Activity
Non Functional assurance (V&P, RFO) , test report (if applicable) - Deliverable and Activity
Penetration testing and penetration testing report (if applicable) - Deliverable and Activity
IG assurance (if applicable) – Activity
Training Plan (if applicable) – Deliverable
FOT (First Of Type) DevMAC award to the GP System supplier for deployment to FOT sites - Award
DVC - Deployment Verification Period in FOT sites - Activity
Supplier Delivery Plan – to include timescales for development, test and deployment.
Test Report / Evidence – Standard report with evidence from recordings, screen grabs or code to show changes have past the Suppliers own Testing.
Following approval of the above Test Report by NHSD the Supplier is then expected to follow the standard RfC route to implement these changes keeping the PCRM Project Manager informed as to when said RfC has been submitted.
The Programme would also ask that the changes be rolled out across the GPSS entire estate ASAP once the RfC is approved with the PM again being kept up to date.