Get the Medicare Coverage You’ve Been Missing

Protect patient data inside logs, analytics and AI prompts

With most plans at $0/month, Clover is a Medicare Advantage plan giving members more coverage for less cost — but operational teams still need a safe way to work with patient text. This interactive prototype shows Shroud detecting and either redacting or tokenizing PHI/PII from mock Clover patient records before they leave the application.

Live redaction — local demo of Shroud's Tier-1 rules

Deterministic local tokenization for demo only — vault tokens require Shroud service

Paste a patient log or clinical note (sample below). Fields detected: EMAIL, PHONE, SSN, MRN, NPI, CARD, AMOUNT, IP.

Tokenize (reversible via vault)

Matches

—

Latency

—

Output

(Run the demo to see redacted/tokenized output)

Why this matters for Clover Health

Keep PHI out of log aggregation and analytics while preserving join keys via tokenization.
Local Tier-1 rules (regex + checksums) catch deterministic identifiers (MRN, NPI, SSN, cards) at low latency.
Drop-in integration for logging frameworks means you can ship safe logs without refactoring telemetry pipelines.

Demo constraints

This prototype runs Shroud's Tier-1 patterns inside the browser for instant feedback. Tokenization here is deterministic but non-reversible; the real Shroud service issues reversible vault tokens and supports HIPAA BAA for production use.

Integration preview

Add Shroud to your logging/ETL step — shown here as a Python example Clover engineers can drop into backend services.

from shroud import Client

shroud = Client(api_key="sk_live_…")
clean = shroud.redact(log_line)
# → Patient: [NAME]\nDOB: 03/12/1948\nMRN: [MRN]\n... 

# for analytics requiring joins, use tokenize:
clean_tok = shroud.redact(log_line, mode="tokenize")
# → MRN tok_mrn_a3f2b1 (deterministic short token)

How it fits Clover's stack

Place Shroud in the logging before sending to Sentry/Datadog to ensure PII never leaves services.
Use tokenize mode for analytics joins; only the token vault can reverse. Fits data governance and HIPAA scopes.
Low latency Tier-1 rules avoid adding meaningful CPU cost to real-time request paths.

Next steps

Evaluate on a sampling of Clover logs (Hobby/Startup tiers allow gradual rollout).
Enable tokenize + vault once joint-testing completes; request a BAA for production HIPAA coverage.
Instrument a rollback-safe logger wrapper (examples: Django, Express, FastAPI) and run for 2 weeks.