Dataset de-identification is the removal of personal data from a pooled virtual-care collection. Once it is truly anonymous, it is no longer personal data under UK GDPR Recital 26. anonym.plus does this on your device and keeps the care patterns for study.
When this applies
A research set pools consultations, messages, and outcomes from many patients. Each row ties back to a person via name, email, and device. Those must go.
How anonym.plus handles it
- Open the pooled set in anonym.plus on a local device.
- It scans identifier columns and free-text fields alike.
- Outcome and visit-type columns stay in place.
- Swap the personal parts with the map turned off.
- Save the anonymous collection on your machine.
What you need to provide
- The collection (CSV, JSON, or a record bundle).
- Replace with the re-link map off for anonymity.
- Optional column map for identifier fields.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | patient column → [PATIENT_n] |
| Contact | EMAIL_ADDRESS | contact email → [EMAIL] |
| Identifiers | ID | device handle → [DEVICE] |
| Network | IP_ADDRESS | session IP → [IP] |
| Dates | DATE_TIME | visit date → shifted [TIME] |
| Free text | LOCATION | inline city → [PLACE] |
Compliance achieved
- True anonymity puts the set outside scope by UK GDPR Recital 26.
- Strips UK GDPR Art. 9 health personal data.
- On-device work supports UK data residency.
Anonymise virtual care datasets offline — see plans & start free →
Limitations & cautions
A pooled set raises re-identification risk, since rare combinations across rows can single out one person. Coarsen dates and small postcodes, keep no re-link key, and apply the ICO motivated-intruder test before you call it anonymous.
Frequently asked questions
When is the set truly anonymous under UK GDPR?
When no one can reasonably re-identify it. That needs no kept key and low residual risk from rare row combinations, per UK GDPR Recital 26.
Do the outcome columns stay?
Yes. Outcomes and visit types remain. Only the personal fields and free-text clues are removed.
Does it read both columns and notes?
Yes. Structured fields and free-text entries in the bundle are both handled locally.