reviewing-reidentification-risk

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

5.0k|615|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill reviewing-reidentification-risk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-reidentification-risk
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/reviewing-reidentification-risk
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill reviewing-reidentification-risk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps determine whether a de-identified dataset has a very small risk of re-identification by identifying quasi-identifiers, measuring uniqueness, and documenting residual risk for HIPAA Expert Determination support.

Core Features & Use Cases

  • Quasi-Identifier Analysis: Identify combinations of age, geography, dates, sex, rare diagnoses, providers, and other attributes that may enable singling out.
  • Privacy Risk Scoring: Compute k-anonymity and l-diversity, identify singleton records, and run OpenMed's empirical auxiliary-data linkage attack.
  • Risk Reduction and Documentation: Recommend generalization or suppression, re-score the dataset, and produce a defensible residual-risk memo without exposing raw records.
  • Use Case: Evaluate a proposed clinical dataset release, test whether age and ZIP combinations create unique records, and document the assumptions and attack metrics supporting an expert determination.

Quick Start

Use this skill to score the attached de-identified dataset with its auxiliary records, identify low-k and singleton records, run the empirical re-identification attack, and draft a residual-risk memo.

Frequently Asked Questions about reviewing-reidentification-risk

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

FAQPage Schema
How do I measure re-identification risk in a de-identified dataset?

To measure re-identification risk, analyze quasi-identifiers like age, geography, and dates to measure record uniqueness, compute k-anonymity and l-diversity, and run empirical auxiliary-data linkage attacks to document residual risk.

What is k-anonymity and l-diversity analysis for HIPAA Expert Determination?

K-anonymity and l-diversity analysis for HIPAA Expert Determination involves scoring combinations of quasi-identifiers to identify singleton records and ensure a dataset has a very small risk of re-identification before release.

How do I test for linkage attacks using auxiliary data?

Test for linkage attacks by running empirical re-identification attack metrics against your dataset using auxiliary records to identify unique combinations of quasi-identifiers that could enable singling out.

What is the best way to document residual risk for a clinical dataset release?

Document residual risk for a clinical dataset release by applying generalization or suppression to reduce risk, re-scoring the dataset, and producing a defensible residual-risk memo detailing attacker assumptions and attack metrics.

Does this approach support HIPAA Expert Determination requirements?

Yes, this approach supports HIPAA Expert Determination by measuring record uniqueness, documenting attacker assumptions, running empirical linkage attacks, and generating a residual-risk memo without exposing raw records.

What quasi-identifiers create singleton records in privacy audits?

Combinations of age, geography, dates, sex, rare diagnoses, and providers often create singleton records during privacy audits, enabling singling out and increasing the risk of successful linkage attacks.