Coordination of Benefits Redaction with anonym.plus

Clear IDs across both insurers while the payment order stays.

COB redaction is the removal of IDs from a coordination-of-benefits record, where a person holds two policies. It meets DPA 2018 & UK GDPR. 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 insurers, each with its own membership number. To audit the payment order, clear every ID first.

How anonym.plus handles it

  1. Load the record into anonym.plus on your device.
  2. It finds the patient and both sets of insurer IDs.
  3. Each membership number gets flagged as its own item.
  4. Keep the primary and secondary payment order.
  5. Swap or black out the confirmed IDs.
  6. Save the clean copy on your machine.

What you need to provide

Patient data entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONPatient Sara Volk → [PATIENT]
Primary IDUK_HEALTH_INSURANCE_MEMBERPri BUP-881102 → [PRIMARY_ID]
Secondary IDUK_HEALTH_INSURANCE_MEMBERSec AXA-449920 → [SECONDARY_ID]
AccountACCOUNT_NUMBERAcct 7741 → [ACCOUNT]
DatesDATE_TIMETreatment 02/14 → [DATE]
NI numberUK_NINOQQ 12 34 56 C → [ID]

Compliance achieved

Anonymise COB records offline — see plans & start free →

Limitations & cautions

Dual coverage doubles the IDs. Check that both insurers’ 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 membership 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 insurers stay distinct after the swap?

Yes. An alias map keeps each insurer under its own steady label.