Tools › Entity types

Health data

Redact health plan identifiers from text, JSON, and CSV

A plan ID links a person to their insurer, their employer, and their claims history. It is also one of the 18 HIPAA identifiers.

Try it on the live API No signup. 2,000 characters, 20 runs per 10 minutes.
Output appears here.

How Redactly detects health plan identifiers

  • Detected from a member, policy, or plan cue together with the value.
  • Handles both all-numeric and alphanumeric identifiers.
  • The value must contain a digit, so a plan name alone is not captured.

Why redact health plan identifiers?

Plan IDs expose the payer relationship, which is both health and employment information.

Example request

curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "Member ID: HPN-88231-04, group 5567, plan PPO.", "style": "replace"}'

Every hit in the response carries entity, text, start, and end. The offsets index into the text you sent, so you can apply the redactions to your own copy of the document. The full response schema is in the API reference.

Questions

Does Redactly redact health plan identifiers automatically?

Yes. Send text to the API and every detected type is redacted, including health plan identifiers. To redact only this type, pass the value healthcare.health_plan_id in the entities filter. No training or configuration is required.

What happens to health plan identifiers after redaction?

With style set to replace, each match becomes [healthcare.health_plan_id] — the entity type in square brackets. Setting style to mask replaces every character with a block character, and remove deletes the span entirely.

Related entity types

Redact health plan identifiers in production

Get an API key and send your first request in a minute. Plans start at $24/month.

See pricing