Member Enrollment File De-Identification with anonym.plus

Clear IDs from the enrollment feed while the plan choices stay.

Member enrollment de-identification is the removal of personal IDs from an enrollment record (often an 834 feed). It meets the HIPAA Privacy Rule (45 CFR Part 164). anonym.plus works locally and keeps the plan choices for analysis.

When this applies

The record is ID-dense: full demographics, dependents, and a plan choice. To study take-up rates or train staff, strip those IDs first.

How anonym.plus handles it

  1. Open the feed in anonym.plus on your device.
  2. It finds demographic, dependent, and contact fields.
  3. Dependent names get flagged as related-party IDs.
  4. Keep the plan choice and the tier you need.
  5. Swap or black out the confirmed items.
  6. Save the clean copy on your machine.

What you need to provide

PHI entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONEnrollee D. Roth → [MEMBER]
DependentPERSONDependent child → [DEPENDENT]
Member IDUS_HEALTH_PLAN_BENEFICIARYMbr 22-8841 → [MEMBER_ID]
SSNUS_SSN298-44-1120 → [ID]
DatesDATE_TIMEDOB 1985 → [DOB]
AddressLOCATIONhome address → [ADDRESS]

Compliance achieved

Anonymize enrollment records offline — see plans & start free →

Limitations & cautions

Dependents' IDs must go too, since they are PHI when tied to the enrollee. Check that custom demographic fields are mapped, so nothing slips past in a fixed layout.

Frequently asked questions

Are dependents anonymized too?

Yes. A dependent's name or birth date in the enrollee's record is PHI and is flagged for removal along with the member's own.

Does the plan choice stay?

Yes. The chosen plan and the tier stay, so the data is still useful for take-up studies.

Can I process an 834 feed?

Yes. Structured 834 exports and printed enrollment pages both work locally.