From privacy-impact-assessment-skills
Guides DPIA for health/medical data processing under GDPR Art. 9 exemptions, HIPAA crosswalk, clinical trials (EU CTR 536/2014), genetic data. For healthcare systems, research, apps, devices.
npx claudepluginhub mukul975/privacy-data-protection-skills --plugin privacy-impact-assessment-skillsThis skill uses the workspace's default tool permissions.
Health data is classified as a special category under GDPR Art. 9(1), requiring both a lawful basis under Art. 6(1) and an Art. 9(2) exemption for processing. Processing of health data on a large scale triggers a mandatory DPIA under Art. 35(3)(b). This skill provides a DPIA methodology for health data processing scenarios: electronic health records, clinical trials, health research, telemedici...
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Health data is classified as a special category under GDPR Art. 9(1), requiring both a lawful basis under Art. 6(1) and an Art. 9(2) exemption for processing. Processing of health data on a large scale triggers a mandatory DPIA under Art. 35(3)(b). This skill provides a DPIA methodology for health data processing scenarios: electronic health records, clinical trials, health research, telemedicine, health applications, medical devices, and genetic data analysis.
GDPR Art. 4(15) defines data concerning health as "personal data related to the physical or mental health of a natural person, including the provision of health care services, which reveal information about his or her health status."
This includes:
| Exemption | Reference | Application |
|---|---|---|
| Explicit consent | Art. 9(2)(a) | Patient consent for specific health processing. Must be separate from treatment consent. |
| Employment obligations | Art. 9(2)(b) | Occupational health assessments required by employment law. |
| Vital interests | Art. 9(2)(c) | Emergency medical treatment where patient cannot consent. |
| Healthcare provision | Art. 9(2)(h) | Processing necessary for preventive or occupational medicine, medical diagnosis, provision of health or social care, or management of health systems. Must be processed by or under the responsibility of a professional subject to medical secrecy. |
| Public health | Art. 9(2)(i) | Processing necessary for public health purposes including protecting against serious cross-border threats, ensuring high standards of quality and safety of health care, medicinal products, or medical devices. |
| Scientific research | Art. 9(2)(j) | Processing necessary for scientific research purposes (including clinical trials) subject to Art. 89(1) safeguards: data minimisation, pseudonymisation where possible. |
For each health data processing activity, document:
| Requirement | Documentation |
|---|---|
| Art. 6(1) lawful basis | Which Art. 6(1)(a)-(f) basis applies |
| Art. 9(2) exemption | Which Art. 9(2)(a)-(j) exemption applies |
| Member State derogation | Whether national law provides additional conditions (Art. 9(4)) |
| Professional secrecy | Whether processing is under a professional subject to secrecy obligation (Art. 9(3)) |
| Data subject consent | If relying on Art. 9(2)(a), evidence of explicit consent separate from treatment consent |
| Assessment Area | Requirements |
|---|---|
| Informed consent | CTR Art. 28 consent separate from GDPR consent; plain language; withdrawal right without impact on treatment |
| Pseudonymisation | Clinical trial data should be pseudonymised with key held by principal investigator; sponsor should not hold re-identification key |
| Data minimisation | Collect only data specified in the clinical trial protocol; no speculative data collection |
| International transfers | Multi-centre trials involve transfers; each transfer requires Chapter V mechanism |
| Retention | CTR Art. 58: sponsor retains trial master file for 25 years; reconcile with GDPR storage limitation |
| Secondary use | Re-use of clinical trial data for future research requires additional ethical approval and GDPR lawful basis |
| HIPAA Provision | GDPR Equivalent | Gap Assessment |
|---|---|---|
| HIPAA Privacy Rule (45 CFR 164.500-534) | GDPR Art. 5 principles + Art. 9 special categories | GDPR is more restrictive: broader definition of health data; explicit consent standard higher; no Treatment-Payment-Operations (TPO) exception |
| HIPAA Security Rule (45 CFR 164.302-318) | GDPR Art. 32 security of processing | Largely aligned: both require risk assessment, encryption, access controls, audit logging |
| HIPAA Breach Notification (45 CFR 164.400-414) | GDPR Art. 33-34 | GDPR stricter: 72-hour notification to SA; HIPAA allows 60 days |
| HIPAA Minimum Necessary | GDPR Art. 5(1)(c) data minimisation | Aligned in principle; GDPR applies more broadly |
| HIPAA Business Associate Agreement | GDPR Art. 28 DPA | Both require written agreements with processors; GDPR DPA is more prescriptive |
| HIPAA Patient Rights | GDPR Art. 15-22 | GDPR provides broader rights (portability, erasure, restriction, objection) |
| HIPAA De-identification (Safe Harbor / Expert) | GDPR Recital 26 anonymisation | Different standards: HIPAA Safe Harbor has 18 specific identifiers; GDPR requires irreversibility assessment |
| Risk | Description | Typical Level |
|---|---|---|
| HD-R1 | Health data breach exposing sensitive diagnoses, conditions, or genetic information | Very High |
| HD-R2 | Re-identification of pseudonymised health data through linkage with other datasets | High |
| HD-R3 | Discriminatory use of genetic data (insurance denial, employment discrimination) | High |
| HD-R4 | Unauthorised access by healthcare staff beyond clinical need-to-know | High |
| HD-R5 | Secondary use of clinical trial data without participant awareness | Medium |
| HD-R6 | Cross-border transfer of health data to jurisdictions with weaker protections | High |
| HD-R7 | Patient re-identification through aggregation of fitness/wellness app data | Medium |
Genetic data has unique privacy characteristics:
Additional requirements for genetic data: