Remittance advice redaction is the removal of UK GDPR Art. 9 identifiers from a provider payment notice. A network provider like a hospital or clinic usually processes the same patient's claim as its own separate controller, alongside the insurer, so UK GDPR Art. 26 governs how the two share responsibility for the record rather than one simply instructing the other under Art. 28. anonym.plus runs on your device. The payment lines stay clear, but the page no longer names the individual.
When this applies
A remittance notice lists each person, the adjustment codes, and amounts paid to a provider that holds its own controller relationship with the patient under Art. 26. To study declines or train billers, clear the IDs first and keep the adjustment codes and paid amounts.
How anonym.plus handles it
- Open the notice in anonym.plus on your device.
- Local OCR reads the printed grid, even on a scan.
- The tool flags patient names and membership numbers.
- Keep the adjustment codes and the paid amounts.
- Replace each ID with a steady alias, or redact it.
- Save the clean notice on your machine.
What you need to provide
- The notice (PDF, scan, or insurer export).
- An operator: Replace, Redact, or Mask.
- Optional alias map for repeat individuals.
Patient data entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | Patient M. Sole → [PATIENT] |
| Member ID | UK_HEALTH_INSURANCE_MEMBER | ID AXA-772031 → [MEMBER_ID] |
| Account | ACCOUNT_NUMBER | Acct 9920 → [ACCOUNT] |
| Claim ref | ID | Claim CL-5512 → [REF] |
| Dates | DATE_TIME | Treatment 03/09 → [DATE] |
| Provider | ORGANIZATION | Clinic GMC → [PROVIDER] |
Compliance achieved
- Strips UK GDPR Art. 9 health identifiers from the notice.
- Reflects the provider's own controller role under UK GDPR Art. 26, distinct from the insurer's.
- Catches patient names and membership numbers as personal data.
- Fully offline — no cloud upload required.
- On-device AES-256-GCM guards working copies.
Anonymise remittance notices offline — see plans & start free →
Limitations & cautions
A remittance grid can list many patients per page. Check that every row is scanned, since one missed name still exposes a person. The adjustment codes stay and are not treated as identifiers.
Frequently asked questions
Do the payment lines survive redaction?
Yes. The adjustment codes and the paid amounts stay untouched. Only patient IDs change, so the page is still useful for a review of payment patterns.
Why does the provider count as its own controller?
A hospital or clinic in the insurer's network usually holds and processes the same patient's data for its own clinical and billing purposes, not purely on the insurer's instructions, which is what makes it a separate controller under UK GDPR Art. 26 rather than a processor. That does not change what gets redacted here, but it does mean the provider's own copy of the record needs its own separate anonymisation pass.
Can a scanned remittance be cleaned?
Yes. Local OCR reads scanned pages, so IDs in image files are caught the same way as in a digital export.