Built to exceed healthcare’s strictest standards
Verified, audited, and certified
HIPAA-aligned by design
Every workflow, integration, and data exchange is built to meet HIPAA requirements—not retrofitted after the fact.
SOC 2-certified
Independently audited and certified. Controls across security, availability, and confidentiality are verified—not self-reported.
How we handle your data by product
Alluvium's data architecture varies by product because the workflows are fundamentally different. Here's exactly how each one handles PHI, so your security and compliance teams know precisely what they're evaluating.
Flexible to your environment
Alluvium's deployment architecture adapts to your environment and differs by product.
Always secure and audit-ready
Every query, forecast, and action includes full provenance tracking with cited outputs. Governed scenario modeling across an ensemble AI pipeline—embeddings, classifiers, and language models—each with a documented decision trail so your compliance team always knows exactly what ran, when, and why.
Manage access by role
Set tiered permissions
Executives, operators, and analysts each see exactly what they need. Access is configured at deployment and adjustable as your team evolves.
Manage access by product
Orchestrate customers operate in isolated tenant environments. Referral and Search & Schedule use a secure multi-tenant model with strict logical data separation between health systems.
Audit trail for every action
Every query, dashboard view, and data access is logged with full provenance.
How we connect to your systems
Alluvium reads patient, slot, appointment, provider, and insurance data. For Referral and Search & Schedule, we write patient and appointment data back to your EMR as part of the core workflow. Every integration permission is scoped to minimum necessary access—read and write permissions are explicitly defined, documented, and confirmed during implementation.
Credentials are encrypted at rest, rotated on a defined cadence, and never stored in plain text. Access tokens are scoped per integration and revocable at any time.
When the relationship ends, your data is deleted on a documented schedule. Offboarding procedures are contractually defined—no ambiguity about what happens to your data after termination.
Every API call is logged with timestamp, endpoint, and payload metadata—giving your security team full visibility into what Alluvium accessed and when.
