Patient Portal Export Anonymization with anonym.plus

Clean a portal download — fields and notes — without leaving your network.

Export anonymization is the removal of PHI from a patient portal download (CSV, JSON, or a bundle). The HITECH Act raised the stakes on moving such data. anonym.plus anonymizes it on your own device, off the cloud.

When this applies

A portal lets people pull their own records, messages, and results into one download. For analytics that file must be stripped of identity first.

How anonym.plus handles it

  1. Point anonym.plus at the download folder on your server.
  2. It scans ID columns and any free-text fields.
  3. Steady labels keep links across joined rows intact.
  4. Review the summary and tune the column rules.
  5. Save the clean dataset on your device for later.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONaccount name → [PATIENT]
ContactEMAIL_ADDRESSportal email → [EMAIL]
IdentifiersUSERNAMElogin handle → [HANDLE]
DatesDATE_TIMElogin date → shifted [TIME]
NetworkIP_ADDRESSaccess IP → [IP]
Record IDsMEDICAL_RECORD_NUMBERmrn field → [MRN]

Compliance achieved

Anonymize patient portal exports offline — see plans & start free →

Limitations & cautions

A portal download mixes tidy columns with free-text notes and message bodies. The columns map cleanly; the free text needs the same review as any note. Test a sample before a full run.

Frequently asked questions

Can records stay linkable after the swap?

Yes. A steady label map swaps each ID the same way, so rows for one person still join while no real identity remains.

Why work locally rather than in the cloud?

Sending raw portal data to a cloud tool is itself a disclosure with breach risk under HITECH. Local work skips that risk.

Does it handle both fields and message bodies?

Yes. Structured columns and free-text message bodies in the bundle are both supported.