Admission Record Anonymization with anonym.plus

Clear IDs from intake files while the clinical context stays.

Admission-record anonymization is the removal of the intake IDs from a file. It meets the HIPAA Privacy Rule (45 CFR Part 164) before reuse. anonym.plus works on your device and keeps the complaint and history for analysis.

When this applies

Intake files are ID-dense: full demographics, insurance, next of kin, and contacts. To use them for capacity work or teaching, strip that data first.

How anonym.plus handles it

  1. Open the file in anonym.plus on your device.
  2. It finds demographic, insurance, and next-of-kin fields.
  3. Contact names and numbers get flagged as related-party IDs.
  4. Swap or black out the confirmed items.
  5. Save the clean intake file on your device.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONpatient & next of kin → [NAME]
IdentifiersNATIONAL_IDinsurance ID → [INSURANCE_ID]
ContactPHONE_NUMBERemergency tel → [PHONE]
LocationLOCATIONhome address → [ADDRESS]
DatesDATE_TIMEadmit date → [DATE]
Record IDsMEDICAL_RECORD_NUMBERencounter ID → [ENCOUNTER]

Compliance achieved

Anonymize admission records offline — see plans & start free →

Limitations & cautions

Intake forms often pack insurance and guarantor data into fixed layouts. Check that your custom fields are mapped, so nothing slips by. Relatives' IDs must go too, since they are PHI when tied to the patient.

Frequently asked questions

Are contact details PHI?

Yes. When a relative's name or number sits in the patient's file, it is PHI and must go for de-identification.

Can I keep diagnosis codes?

Yes. Non-ID clinical and admin codes can stay while personal data goes, via an allow-list.

Does this work on EHR intake summaries?

Yes. Printed forms and structured EHR intake exports are both supported.