Incident Studio / INC-013
Duplicate patient record created
1. Capture
Done- Reported by
- [Practice manager], Hillside Surgery, through the Trust Portal
- Occurred
- 1 Oct 2026, 16:40
- Product
- AI Triage Platform 2.3
- What happened
- A returning patient with a hyphenated surname was given a new record instead of being matched
- Patients affected
- 1
- Harm
- None known
- Immediate action
- Practice linked the records manually
- Attachments
- Screenshot.png
2. Triage
Done- Severity
- Minor harm possible · likelihood possible
- Priority
- P2 · triage deadline met
- MHRA
- Not reportable: no harm, assessed 2 Oct
- ICO
- Not a personal data breach: nothing disclosed
- LFPSE
- Practice’s decision · not reported
- Triaged by
- Zak Yahiya, 2 Oct 11:20 · Qyro draft accepted
3. Engagement
Done| Stakeholder | Role | Last contact | Next update |
|---|---|---|---|
| [Practice manager] | Reporter | 9 Oct · portal | 16 Oct |
| [Clinical lead], Hillside | Deploying CSO | 9 Oct · call | 16 Oct |
| Zak Yahiya | Supplier CSO | – | – |
| [DPO] | Data protection | 2 Oct · email | Closed |
- Duty of candour
- Not required: no harm
- Communications
- 4 logged · Open log
4. Risk assessment
Done- Hazard
- H-15 Patient identity mismatch
- Risk now
- Major × low, 8
- Proposed
- Major × medium, 12 · Suggested by Qyro
- Containment
- Practices asked to check matches for hyphenated surnames · sent 3 Oct
5. Replication
Done- Reproduced
- Yes, 4 of 5 attempts
- Environment
- Staging, release 2.3
- Steps
- Register “Smith-Jones”, return as “Smith Jones”
- Evidence
- Screen recording Matching logs
- By
- [Engineer], 7 Oct
6. Root cause and CAPA
In progressRoot cause drafted by Qyro · confirm before it counts
- Method
- 5 whys
- Contributing
- Root cause
- Patient matching compares surnames exactly, so spelling variants of the same name create a new record
7. Risk management
To do- Hazard log
- H-15 updated with this cause and the new control
- Residual risk
- Re-estimated after the fix
- Safety case
- Update needed? CSO decides
- Sign-off
- Supplier CSO
8. Delivery
To do- Fix
- Release and version
- Change control
- Runs through the Change control workflow
- Verified
- Test evidence attached
- Customers told
- Release note through each Trust Portal
9. Closure
To do- Closure checks
- All CAPAs done · hazard log updated · reporter told
- Effectiveness
- Check scheduled by the Planner
- Learning
- Summary shared with staff and the practice
- Closed by
- Owner, with CSO approval