Executive Summary
This case study documents the most serious application of the Data Continuity and Sovereignty Test: a continuity failure within NHS medical records that resulted in direct personal harm.
Using lawful UK GDPR Article 15 Subject Access Requests (SARs) and follow-up enquiries, the test revealed that the data subject's childhood and early-adult medical history (approximately 1967–2002) was not indexed as structured records, but instead existed—where present at all—as a single unindexed scan inaccessible to clinicians. The effect was not theoretical. The absence of longitudinal medical continuity directly influenced clinical interpretation, eligibility assessments, and support decisions decades later.
This case demonstrates that continuity failure in health data is not merely inconvenient—it is dangerous.
1. Purpose of the Test
The objective was not to challenge clinical judgement or individual practitioners. The objective was to determine whether the NHS medical record system preserves developmental continuity such that a patient's full medical history can be accessed and understood as a coherent whole.
Research questions:
- Can the NHS reconstruct a patient's longitudinal medical history across decades?
- Are early records preserved in a form usable by modern clinical systems?
- What are the effects when continuity breaks in health data?
1.1 What This Test Is Not
This study is not:
- a complaint about individual clinicians
- a denial of medical expertise
- a criticism of safeguarding practice
- a retrospective demand for diagnosis
It is a continuity test of medical record stewardship.
2. Definition Framework
2.1 Linguistic Baseline (Oxford Languages)
Continuity is defined as "the unbroken and consistent existence or operation of something over time."
2.2 Operational Extension (This Study)
Medical Continuity: The ability of a health system to preserve, index, and present a patient's full developmental and clinical history such that present-day decisions are informed by past reality, not administrative absence.
Health Data Sovereignty: The patient's ability to access and present their own medical history as a coherent, continuous record.
3. Methodology
3.1 Instrument
Multiple UK GDPR Article 15 SARs and data access requests submitted to NHS primary care and secondary care providers, alongside direct clinical enquiries.
3.2 Rationale
Health records uniquely depend on longitudinal continuity. Missing early records distort diagnosis, risk assessment, and eligibility.
3.3 Evidence Handling
Disclosures, refusals, and explanations were archived. Where records were stated to be absent, follow-up investigation examined how they were absent.
4. Case Background
The data subject experienced childhood and adolescent medical issues including recurrent ear pain, sensory distress, and respiratory illness. As an adult, these early experiences became clinically relevant in the context of neurodevelopmental and respiratory assessments.
Repeated enquiries over more than twelve months were met with assertions that early records "did not exist." Later examination revealed that early records had been collapsed into a single scanned document, unindexed and effectively invisible to clinicians using modern systems.
5. Observed Continuity Failures
5.1 Administrative Non-Existence
Records were treated as absent because they were not indexed, not because they were untrue.
5.2 Single-Document Collapse
Decades of medical history were reduced to a single scan, removing temporal structure and clinical usability.
5.3 Clinical Impact
The absence of childhood records:
- erased early symptom patterns
- distorted developmental timelines
- undermined eligibility for support
- forced adult-only interpretation of lifelong conditions
6. Harm Analysis
This continuity failure caused real harm:
- delayed or distorted assessments
- denial of support pathways contingent on historical evidence
- emotional distress caused by repeated denial of lived reality
The system gave the appearance that the records "did not exist." In practice, the continuity layer failed.
7. Findings
7.1 Containers vs Continuity (Healthcare Variant)
The NHS retained data, but not continuity.
7.2 Continuity Failure Equals Clinical Risk
When continuity fails, medical decisions are made on incomplete reality.
7.3 Patient as Continuity Holder
The patient was forced to reconstruct and defend their own medical history.
8. Interpretation
This case demonstrates that health data continuity is a safety issue.
- Missing records ≠ missing conditions
- Administrative absence ≠ clinical truth
- Compliance ≠ care
9. Implications
9.1 For Patients
- Loss of trust in medical records
- Increased burden to self-advocate
9.2 For the NHS
- Legacy record migration is a patient safety issue
- Indexing and continuity layers are essential infrastructure
9.3 For Regulators
- Continuity failures should be treated as harm-bearing events
10. Design Response
This case establishes the strongest requirement for patient-held continuity:
- lifelong, append-only medical timelines
- patient-owned continuity copies
- NHS systems as contributors, not sole custodians
11. Conclusion
The NHS case completes the Data Continuity and Sovereignty Test.
Across all examined institutions, the pattern is consistent—but in healthcare the consequences are severe:
When continuity breaks in health data, harm follows.
This is not a documentation problem. It is a safety problem.
Appendices
Appendix A — Evidence Index
- SAR correspondence and NHS record disclosures
- Clinical assessment correspondence
Appendix B — Reproducibility
This test can be reproduced within healthcare systems by examining the usability—not just existence—of early medical records.