Security & privacy
Private by default, with every view and decision logged
Clarity handles referral packets and patient records with HIPAA-aligned controls: a private VPC, hard tenant and patient isolation, encryption in transit and at rest, and an audit trail behind every decision.
How data is handled
The controls your reviewers will ask about
Clarity was built for regulated healthcare data from the start. These six controls apply to every screen in the product.
HIPAA-aligned handling
Clarity works as a business associate under a BAA. HIPAA-aligned controls cover how data is stored, who can access it, and how each access is recorded.
Private by default
Services run inside a private VPC with no public endpoints, and every service-to-service call is IAM-signed.
Hard tenant and patient isolation
Every query is scoped to one tenant and one patient, and isolation is verified in evaluation.
Role-based access
Each person sees only what their role needs. Admissions, billing, and administrators each get their own view of the record.
Audit logging
Every view, recommendation, decision, and override is logged with who did it and when.
Encryption, clean logs
Data is encrypted in transit and at rest, and PHI is scrubbed from application logs.
Demo environments and screenshots use synthetic patients only: Robert Davis · 73 · MRN 8472301 is not a real person.
Responsible AI
The AI shows its work and your team makes the call
You don’t have to take Clarity’s word for anything. Every answer is tied to the exact quote on the exact page of the source chart, one click from the claim. When the packet doesn’t hold the answer, Clarity flags insufficient evidence instead of guessing.
- Clarity recommends; your team makes the accept or decline
- Ambiguous findings come back as needs review for a person to decide
- Overrides require a note and are audit-logged
Deal-breaker · Pain management
“Pain well controlled on Tylenol 650mg q6h… 3/10 at rest”
Clarity Beacon · launching soon
Privacy limits built into Beacon
Clarity Beacon, care-transition alerts launching soon, is being built with these privacy limits as fixed design principles.
Monitoring will stop at the end of a hard 31-day post-discharge window, with automatic unsubscribe. The window brackets Medicare’s 30-day return rule exactly.
Treatment and care coordination only. Beacon will not be used for population analytics, surveillance, or model training.
Beacon will never monitor anyone you declined, and the alert ping itself carries no patient details.
Why 31 days? A patient who returns to skilled care within 30 days of discharge needs no new qualifying hospital stay, so monitoring ends when that rule stops applying.
Bring your security team
We’ll walk your security or compliance reviewers through the architecture, the isolation evaluation, and the audit trail, and we’ll route your security questionnaire.