Patient registration, demographics and GP-record transfer
At a glance
Treat registration as four linked but distinct legs: the registration application, Personal Demographics Service (PDS) trace and demographic handling, Primary Care Registration Management (PCRM), and GP2GP longitudinal-record transfer. A completed registration does not prove that the clinical record transferred safely, and a transferred record does not prove that it was reviewed and integrated.
Return to the Out-of-PHC row or Into-PHC row.
Scope and boundaries
This family covers a permanent patient registration or change of GP practice, the identity and demographic work needed to establish the correct NHS record, the formal registration/deduction transaction and transfer of the GP-held clinical record.
Do not compress these legs into one “registration API”. NHS England’s end-to-end guide shows PCRM registration and GP2GP acknowledgement as parallel hand-offs. GP2GP may also be bypassed where both practices use TPP SystmOne, so record-transfer behaviour must be confirmed for the actual systems. CLM-060
Out of primary healthcare
Following a valid request associated with a permanent move, the current practice must identify the correct patient and receiving practice, prepare the transferable electronic record, send it through the applicable GP2GP route and handle any unconfirmed or paper-only portion through the specified fallback. The statutory and contractual transfer period is distinct from the receiving practice’s operational integration target. CLM-061
The sender remains responsible for completeness, provenance, attachments, redaction effects, transfer status, positive business acknowledgement and an auditable fallback where electronic transfer is incomplete or cannot be confirmed.
Into primary healthcare
The new practice receives the application, traces and matches the person through PDS, identifies the current practice, completes the registration through PCRM, requests and receives the GP2GP record where applicable, reviews and files it, and returns a positive business acknowledgement.
Incoming records need controlled handling for wrong-patient or duplicate matches, degraded codes, allergies and medicines, attachments, large records, redactions, missing review dates, incomplete transfer and paper-only content. Medicines must not be treated as safely integrated while unresolved degraded allergy or drug-sensitivity items remain. CLM-062
How the requirement layers apply
| Layer | Workflow-specific position |
|---|---|
| Legislation | UK GDPR, DPA 2018 and DUAA govern the personal-data processing. The Health and Social Care Act 2012 supplies powers for NHS England directions and information services; a direction to NHS England does not itself establish the practice’s purpose or confidentiality route. |
| Regulations and contract | Check the actual GMS, PMS or APMS terms and current amendments. The GMS and PMS regulations, SI 2021/995, SI 2024/575 and SI 2026/532 contain registration-method and GP-record-transfer requirements in their stated scopes. Do not assume the standard GMS contract text applies unchanged to every contractor. |
| Standards and services | NHS Number for General Practice (ISB 0149-01) is the scoped identity standard. Register with a GP surgery, PDS, PCRM and GP2GP are distinct services or technical routes, not one information standard. Current GP2GP base integration is HL7 V3; supplier adaptors do not make every live transfer generically FHIR. |
| Confidentiality and other controls | Apply common-law confidentiality, the executed contract, PDS matching and sensitive-record controls, smartcard/RBAC and audit, GP2GP onboarding, positive acknowledgement, manual review, degraded-data action, paper and outage fallback, correction, incident and offboarding controls. |
Minimum, conditional and higher assurance
- Required floor: the correct person and practices, valid registration route, applicable contract/regulations, necessary application and demographic information, safe record transfer, review, acknowledgement, fallback and audit.
- Conditional envelope: process only the data and service legs needed for the registration and record-transfer purpose; apply separate safeguards to restricted, sensitive, disputed, child, capacity, temporary-resident or out-of-area cases.
- Higher-assurance ceiling: reliable PDS matching, explicit state across Register/PCRM/GP2GP, complete provenance, safe automated integration with exception queues, positive acknowledgement, reconciliation of paper-only content and monitored correction/failure handling.
Failure states and ownership
Test incorrect or duplicate NHS records, wrong current-practice details, incomplete registrations, temporary-resident exclusions, unsupported supplier combinations, failed or unacknowledged GP2GP transfers, oversized records, missing attachments, degraded codes, unresolved medicines/allergy warnings, unavailable paper records, unreviewed incoming tasks and confusion between the 28-day sender requirement and the separate eight-day receiving integration target.
Evidence and open checks
Maintained evidence: SRC-047, SRC-048, SRC-083 and SRC-084. Confirm the executed contract, current amendments, service interfaces, supplier capability, patient category, matching, acknowledgements, fallback and roadmap state through VAL-035.
Continue to Assess and record this workflow.