Virtual Care Dataset De-Identification with anonym.plus

Turn a pooled virtual-care set into anonymous data outside GDPR scope.

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 GDPR Recital 26. anonym.plus does this on your device and keeps the care patterns for study.

When this applies

A research set pools visits, 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

  1. Open the pooled set in anonym.plus on a local device.
  2. It scans ID columns and free-text fields alike.
  3. Outcome and visit-type columns stay in place.
  4. Swap the personal parts with the map turned off.
  5. Save the anonymous collection on your machine.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONpatient column → [PATIENT_n]
ContactEMAIL_ADDRESScontact email → [EMAIL]
IdentifiersIDdevice handle → [DEVICE]
NetworkIP_ADDRESSsession IP → [IP]
DatesDATE_TIMEvisit date → shifted [TIME]
Free textLOCATIONinline city → [PLACE]

Compliance achieved

Anonymize 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 geographies, keep no re-link key, and weigh the residual risk before you call it anonymous.

Frequently asked questions

When is the set truly anonymous under GDPR?

When no one can reasonably re-identify it. That needs no kept key and low residual risk from rare row combinations.

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.