skills.rest
maziyarpanahi
maziyarpanahiCOMMUNITY
Explore all skills by this author →
Website𝕏@maziyarpanahiGitHub

pseudonymizing-for-gdpr

Apply reversible pseudonymization to clinical text with separate key-vault mapping.

5.0k|615|Updated Oct 4, 2025
Search Tags:#gdpr#key vault#pseudonymization#privacy compliance#re-identification#clinical text
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill pseudonymizing-for-gdpr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pseudonymizing-for-gdpr
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/pseudonymizing-for-gdpr
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill pseudonymizing-for-gdpr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill applies reversible pseudonymization to clinical and personal data so organizations can protect working datasets while retaining a separately controlled ability to re-link records when legally authorized. It preserves the distinction between pseudonymization and irreversible anonymization under GDPR.

Core Features & Use Cases

  • GDPR-aligned pseudonymization: Use OpenMed replacement surrogates with the GDPR pseudonymization policy and a retained mapping.
  • Separate key management: Route pseudonymized text to ordinary processing systems while storing the re-linkage mapping in a separate, access-controlled key vault.
  • Authorized re-linkage: Restore original values only when a lawful basis exists, with audit logging that avoids recording restored plaintext.
  • Retention and risk controls: Apply independent retention to the mapping, protect it as a high-sensitivity secret, and assess residual quasi-identifier risk.
  • Use Case: Prepare EU clinical notes for analytics while preserving a controlled ability to reconnect records for an authorized patient request or longitudinal study.

Quick Start

Use the pseudonymizing-for-gdpr skill to pseudonymize the attached clinical text under GDPR, keep the re-linkage mapping in a separate key vault, and check the output for residual identifiers.

Frequently Asked Questions about pseudonymizing-for-gdpr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does pseudonymization work for GDPR compliance with clinical text?▼

Pseudonymization for GDPR compliance replaces personal identifiers in clinical text with replacement surrogates while retaining a separately controlled mapping for authorized re-identification. It preserves the distinction from irreversible anonymization under GDPR Article 4(5).

What is the difference between anonymization and reversible pseudonymization under GDPR?▼

Reversible pseudonymization under GDPR retains a separately controlled re-linkage mapping in a protected key vault, allowing authorized re-identification. Irreversible anonymization removes this capability entirely, preventing original values from being restored.

How do I pseudonymize clinical notes for analytics while keeping re-linkage for authorized patient requests?▼

Use replacement surrogates to pseudonymize clinical notes for analytics, storing the re-linkage mapping in a separate, access-controlled key vault. Authorized re-linkage restores original values only when a lawful basis exists, with audit logging avoiding restored plaintext.

Can I store the re-identification mapping in a separate key vault for GDPR workflows?▼

Yes, you can route pseudonymized text to ordinary processing systems while storing the re-linkage mapping in a separate, access-controlled key vault. The mapping is protected as a high-sensitivity secret with independent retention controls.

Does pseudonymizing clinical data remove quasi-identifier re-identification risk?▼

Pseudonymizing clinical data applies replacement surrogates and assesses residual quasi-identifier risk, but does not guarantee complete risk removal. A residual re-identification risk review is conducted to evaluate remaining quasi-identifiers.

When should I not use reversible pseudonymization for personal data?▼

Reversible pseudonymization should not be used when permanent, irreversible anonymization is legally required. It is designed for GDPR workflows needing controlled record linkage and authorized re-identification, retaining a mapping that must be actively protected.

Related Skills

Explore More Legal & Compliance Skills→
shawnpetrosshawnpetros

ingest

Convert URLs, PDFs, markdown, and text into wikilinked vault pages.

Community
Advanced
maziyarpanahimaziyarpanahi
5.0k

reidentifying-text

Pseudonymize clinical text and restore protected health information via OpenMed's reidentify workflow.

Community
Advanced
maziyarpanahimaziyarpanahi
5.0k

configuring-privacy-policies

Select and customize OpenMed de-identification policies for clinical text.

Community
Advanced
maziyarpanahimaziyarpanahi
5.0k

reviewing-reidentification-risk

Assesses re-identification risk in de-identified datasets using k-anonymity and l-diversity analyses.

Community
Advanced