GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Healthcare organisations face a specific configuration of obligations shaped by the personal data they collect, the regulatory environment they operate in, and the systems they use to do it.
This page covers the GDPR obligations specific to Healthcare, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: National supervisory authorities + healthcare regulators (CQC, HAS, etc.)
Key personal data categories: patient records, clinical notes, appointment data, billing records, employee H&S records
Special category data present: Yes — requires Article 9 lawful basis in addition to Article 6
Primary lawful bases: Article 9(2)(h) (medical diagnosis and treatment), Legal Obligation (retention), Consent (research, marketing)
Healthcare organisations face a structural tension between GDPR's storage limitation principle and regulatory requirements to retain medical records for defined periods (typically 8–10 years for adult records under national law). The retention schedule must document both obligations and make clear that the longer regulatory period takes precedence — but that data must not be used for other purposes during that extended period.
The hard part
Healthcare DSARs require clinical review before response — the data subject has a right to their records, but records that contain references to third parties (other patients, family members) must be redacted. An automated DSAR response without a clinical review gate creates liability.
This is the implementation decision that most Healthcare GDPR programmes get wrong. It is also the issue most likely to appear in a supervisory authority audit or a data subject complaint.
Required controls
- Separate lawful basis for clinical care vs. research vs. marketing
- DSAR workflow with mandatory clinical review gate before response
- Retention schedules reconciling GDPR data minimisation with regulatory retention mandates
- Breach notification covering both 72-hour GDPR obligation and sector-specific incident reporting
- Processor agreements with clinical software vendors and cloud infrastructure providers
GDPR gap assessment framework for Healthcare
A gap assessment for a Healthcare organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Healthcare operations: patient records, clinical notes, appointment data, billing records, employee H&S records. Document the purpose, lawful basis, retention period, and third-party recipients for each. The ROPA must be current — a snapshot taken at implementation and not updated is not compliant.
2. Lawful basis audit
For each processing activity, confirm the lawful basis is documented and appropriate. Healthcare organisations frequently find that processing that was assumed to be covered by legitimate interests has not had a Legitimate Interests Assessment completed. Where special category data is present, Article 9 requires a separate documented basis.
3. Consent management
Where consent is the lawful basis, verify that consent records meet GDPR Article 7 requirements: freely given, specific, informed, unambiguous, and withdrawable. Legacy consent from before the current privacy notice version should be assessed for adequacy.
4. DSAR readiness
Test the DSAR workflow with a synthetic request. The test should cover: intake, identity verification, data discovery across all systems identified in the data inventory, response assembly, and delivery within the 30-day deadline. Most Healthcare DSAR gaps are discovered at the data discovery stage — systems that hold personal data but are not connected to the DSAR workflow.
5. Breach preparedness
Verify the incident log, the severity classification matrix, and the 72-hour notification workflow. The Healthcare-specific question is: which data categories, if breached, trigger notification to individuals (not just to the supervisory authority)? Notification to individuals is required where the breach is likely to result in high risk to their rights and freedoms.
Implementation priority order
For Healthcare organisations starting a GDPR programme:
- Data inventory — identify all systems holding personal data before configuring any controls
- Lawful basis documentation — stop processing for which there is no documented basis
- DSAR workflow — rights requests can arrive at any time; the workflow must be operational before launch
- Consent remediation — address legacy consent before running any marketing to the affected population
- ROPA — live, connected to source systems, reviewed quarterly
- Breach procedure — tested annually; DPO and legal team both trained on the 72-hour obligation