NHS Integration for Digital Health Products: Interoperability, Identity and Workflow Design
How digital health products integrate with the NHS in England: NHS login, PDS FHIR, GP and hospital systems, DTAC, clinical safety standards and onboarding.
What does NHS integration involve for a digital health product?
In England, NHS integration usually combines four things: patient identity through NHS login; NHS number and demographic checks through the Personal Demographics Service (PDS) FHIR API; clinical or administrative data exchange with GP systems (through IM1 pairing or GP Connect) or hospital systems (usually through a trust's integration engine); and assurance, including NHS England digital onboarding, the Data Security and Protection Toolkit (DSPT), the Digital Technology Assessment Criteria (DTAC), clinical safety under DCB0129 and DCB0160, and medical device regulation where the software is a medical device. The technical connection is often quicker than the assurance, so plan both from the start.
This guide is for founders and product teams building patient-facing apps, clinical tools and service platforms for the NHS in England. It is general information as at October 2026, not regulatory or clinical safety advice. Scotland, Wales and Northern Ireland have separate arrangements.
Key takeaways
- Start from the use case NHS England will need to approve, not the API list.
- Use NHS login for patient identity, not your own identity checks.
- Match patients on a verified NHS number, never on name and date of birth alone.
- Budget time for DTAC, DSPT and a DCB0129 clinical safety case.
- Expect each trust's hospital integration to differ.
- Scope the devolved nations separately.
Which NHS integration do you need?
| Need | Typical route | Notes |
|---|---|---|
| Patient sign-in with verified identity | NHS login (OpenID Connect) | Partner onboarding; identity verification levels determine what the app can show |
| Check NHS number and demographics | PDS FHIR API | Digital onboarding with a valid use case; separate access modes for patients, healthcare workers and applications |
| Read or write GP record data | IM1 pairing with GP system suppliers, or GP Connect | IM1 involves a supplier conformance assessment (SCAL), a model interface licence and supplier-specific integration packs |
| Referrals | NHS e-Referral Service APIs | Check current onboarding requirements with NHS England |
| Hospital appointments and patient administration | Trust integration engine, often HL7 v2 messages or FHIR | Agreed with each trust; data sharing agreements and local testing |
| Healthcare worker sign-in | NHS Care Identity Service 2 (CIS2) | Needed where clinicians access national services |
Assurance you should plan for
| Assurance | What it covers | Who asks |
|---|---|---|
| Digital onboarding | Use case, technical conformance and connection agreements for NHS England APIs | NHS England |
| DTAC | Clinical safety, data protection, technical security, interoperability, usability and accessibility; refreshed form with full transition by 6 April 2026 | NHS and social care buyers |
| DSPT | Annual self-assessment of data security for organisations with access to NHS patient data and systems | NHS England and buyers |
| DCB0129 / DCB0160 | Clinical risk management: hazard log and safety case (manufacturer); deployment assessment (health organisation) | Buyers, NHS England; standards under review |
| Medical device regulation | Whether the software is a medical device and needs conformity marking | MHRA |
| Data protection | Lawful basis, special category conditions, DPIA, processor contracts | ICO; buyers' information governance teams |
Worth noting
The refreshed DTAC removed duplication with the DSPT and pre-acquisition questionnaires and dropped the requirement for the Clinical Safety Officer to complete NHS Digital training. Some third-party summaries describe further changes that NHS England's own pages do not confirm; check the official guidance.
Identity and patient matching
Wrong-patient errors are a clinical safety hazard, so matching deserves design time. Use NHS login to establish who the patient is, and the NHS number, verified through PDS, as the key when exchanging data. Do not merge records on name and date of birth alone; send uncertain matches to a person. Handle superseded and merged NHS numbers, deceased flags and sensitive records according to PDS rules, and record your matching logic in the hazard log.
Designing workflows around patient administration systems
Many products need appointments, referrals or waiting list data from hospital patient administration systems (PAS). Trusts usually expose these through an integration engine rather than direct database access, using HL7 v2 messages (for example admissions and scheduling events) or FHIR APIs. Each trust's set-up, codes and testing process differ.
- Agree message types, codes and responsibilities with the trust's integration team early.
- Process messages idempotently; engines can resend.
- Handle cancellations, rebookings and out-of-order messages.
- Show staff when data is stale or a feed has stopped.
- Keep the trust's PAS as the source of truth for appointments.
- Log every message for troubleshooting and audit.
Clinical safety in practice
Under DCB0129, the manufacturer appoints a Clinical Safety Officer, a registered clinician with suitable training, keeps a hazard log and produces a clinical safety case report for each release. Hazards for integrated products include wrong-patient matching, missed or delayed messages, incorrect units or codes, and alerts that fail silently. Each deploying organisation completes its own DCB0160 assessment, using the manufacturer's documentation. Build the hazard log alongside the backlog, not at the end.
Scotland, Wales and Northern Ireland
Health is devolved. NHS Scotland uses the Community Health Index (CHI) number; Health and Social Care in Northern Ireland uses the Health and Care Number; NHS Wales has its own national services and digital programme. Integration routes, assurance and procurement differ, so treat each nation as a separate scope rather than assuming an England integration carries over.
Hypothetical example: a physiotherapy app
This example is hypothetical. A start-up builds an app that delivers home exercise programmes for NHS musculoskeletal services in England. Patients sign in with NHS login; clinicians are invited by the trust. The app verifies NHS numbers through PDS FHIR, receives referral details and appointment events from one trust's integration engine, and sends discharge summaries back as documents. Before the pilot, the team completes digital onboarding, the DSPT, a DTAC submission and a DCB0129 safety case with a hazard log covering patient matching and missed appointments. The trust completes DCB0160.
Common mistakes
- Building integrations before agreeing the use case and onboarding route.
- Leaving clinical safety documentation until procurement.
- Matching patients on demographics alone.
- Assuming one trust's integration will work for the next.
- Treating England's routes as UK-wide.
- Relying on old DTAC forms or third-party summaries.
Sources
Assurance: NHS England: DTAC guidance; NHS Innovation Service: updated DTAC form and guidance (March 2026); NHS England: digital clinical safety assurance; AI and Digital Regulations Service: clinical risk management standards.
Integration: NHS service manual: Personal Demographics Service; NHS England: partner onboarding; NHS England: IM1 standards.
Accessed 10 October 2026. Some NHS England developer pages block automated access and some details come from summaries; confirm requirements with NHS England. Nothing here is regulatory or clinical safety advice.
Conclusion
NHS integration succeeds when the use case, identity, patient matching and assurance are designed together. Use NHS login and PDS for identity, agree GP and hospital routes early, keep a living hazard log, and plan DTAC, DSPT and onboarding into the timeline. Scope Scotland, Wales and Northern Ireland separately. For general patterns, see integration architecture patterns.
Planning an NHS-connected product?
ZSpace Labs is a remote-first technology studio that works with clients globally on health web platforms and integrations and patient and clinician apps. We have no UK office and do not provide Clinical Safety Officer services; we work alongside your clinical safety and information governance leads. If it would help to plan the integration and assurance work, we are happy to talk it through.
Common questions.
NHS login is the identity service that lets patients in England prove who they are once and sign in to approved health apps and websites. It uses OpenID Connect, and partners join through NHS England's onboarding process.