COB redaction is the removal of IDs from a coordination-of-benefits record, where a person holds two policies. It meets the HIPAA Privacy Rule (45 CFR Part 164). anonym.plus works locally and keeps the order-of-payment logic intact.
When this applies
A dual-coverage record names the patient and lists two payers, each with its own member number. To audit the payment order, clear every ID first.
How anonym.plus handles it
- Load the record into anonym.plus on your device.
- It finds the patient and both sets of payer IDs.
- Each member number gets flagged as its own item.
- Keep the primary and secondary payment order.
- Swap or black out the confirmed IDs.
- Save the clean copy on your machine.
What you need to provide
- The record (PDF, DOCX, or payer export).
- An operator (Redact for slim audit copies).
- Optional alias map so each payer maps cleanly.
PHI entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | Patient Sara Volk → [PATIENT] |
| Primary ID | US_HEALTH_PLAN_BENEFICIARY | Pri 88-1102 → [PRIMARY_ID] |
| Secondary ID | US_HEALTH_PLAN_BENEFICIARY | Sec 44-9920 → [SECONDARY_ID] |
| Account | ACCOUNT_NUMBER | Acct 7741 → [ACCOUNT] |
| Dates | DATE_TIME | DOS 02/14 → [DATE] |
| SSN | US_SSN | 412-90-3321 → [ID] |
Compliance achieved
- Meets the HIPAA Privacy Rule (45 CFR Part 164) for reuse.
- Catches both payers' member numbers as separate identifiers.
- Keeps the order-of-payment logic for audit.
- Offline work keeps the record inside your site.
Anonymize COB records offline — see plans & start free →
Limitations & cautions
Dual coverage doubles the IDs. Check that both payers' numbers are mapped, since a missed secondary ID can still name the person. The payment-order logic stays and is not treated as an identifier.
Frequently asked questions
Why do COB records carry extra IDs?
A person holds two policies, so the file lists a primary and a secondary member number. Both are identifiers and both are flagged.
Does the payment order survive redaction?
Yes. The primary and secondary order stays, so the record is still useful for audit.
Can the two payers stay distinct after the swap?
Yes. An alias map keeps each payer under its own steady label.