EPR export de-identification removes patient data from a record extract (CSV, JSON, or a document bundle). The NHS Data Security & Protection Toolkit sets the bar for such exports. anonym.plus de-identifies them on your own device.
When this applies
Analytics and AI work often start with a bulk export of thousands of records. Sending that to a cloud tool is a data-breach risk under the NHS DSP Toolkit. Local work avoids it.
How anonym.plus handles it
- Point anonym.plus at the export folder on your server.
- It scans both identifier columns and free-text note fields.
- Steady labels keep links across joined rows intact.
- Review the summary and tune the column rules.
- Save the clean dataset on your device for later use.
What you need to provide
- The export as CSV, JSON, or a bundle of record files.
- A column map for known identifier fields.
- Replace with a steady label map to keep table joins.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | patient_name → [PATIENT_n] |
| Record IDs | MEDICAL_RECORD_NUMBER | mrn field → [MRN_n] |
| Dates | DATE_TIME | admit_date → shifted [DATE] |
| Contact | EMAIL_ADDRESS | contact_email → [EMAIL] |
| Location | LOCATION | address fields → [ADDRESS] |
| Free text | PERSON / LOCATION | inline names → labels |
Compliance achieved
- Cuts breach risk under the NHS DSP Toolkit by keeping data off the cloud.
- Supports UK GDPR Art. 9 & DPA 2018 once all identifier types go.
- Keeps row links steady, so the data stays useful for analysis.
Anonymise EPR exports offline — see plans & start free →
Limitations & cautions
Bulk files mix tidy columns with messy free text. Column rules handle the first well. Free-text fields need the same review as any note. Test a sample before a full run, and check that date-shifting keeps the gaps your analysis needs.
Frequently asked questions
Can records stay linkable after the swap?
Yes. A steady label map swaps each identifier the same way, so rows for one patient still join while no real identity is left.
Why work locally rather than in the cloud?
Sending raw patient data to a cloud tool is itself a disclosure with breach risk under the NHS DSP Toolkit. Local work skips that risk entirely.
Does it handle both CSV and document exports?
Yes. Tidy CSV or JSON columns and bundled files are both supported.