Try five live demosdemo.gravixar.com

Module library

HIPAA-aware AI guardrail

Two separate locks keep patient data away from the AI. One scans typed text for things like Social Security and medical record numbers and blocks it before it is saved. The other tells the AI, on every call, to refuse patient data.

The usual way patient data reaches an AI model is not an attack. It is a developer pasting a patient note into a "summarize this" request. The guardrail makes that mistake hard to make, and it does it in code rather than in a policy document.

Under the hood

PHI doesn't belong in prompts. Two defenses keep it out. First, phiSniffer.ts runs regex pattern checks (SSN-shaped numbers, MRN tells, common chart-note structures) on every free-text input pre-persistence and rejects what trips. Second, withHipaaGuardrail() wraps every Claude call and prepends a stop-clause to the system prompt: "You will not process protected health information. If the user input contains PHI, refuse and ask for the redacted form."

The discipline is enforced socially as well: direct @anthropic-ai/sdk imports outside claude.ts are treated as bugs, and a contributor doc says so explicitly. The belt is the wrapper. The suspenders are the sniffer. Both run on every call.

Related modules

Also in AI with guardrails

Bring me a real operations problem. I will show you the system running before you sign anything.

The Ops Leak Audit is the fixed-price first step: I count the hours your tools cost your team, then price the fix. Rather talk first? Book a 30-minute call. If it is not a fit, you still leave with notes you can use.