The platform
The HIPAA-compliant engine under SettleStack.
Every SettleStack deployment runs on the same core: BAA-covered infrastructure, a reasoning layer built on frontier models through Azure OpenAI, and tools purpose-built for retrieving, chasing, and reconciling documents from outside providers — with your case management on top.
Core capabilities
What every deployment ships with.
The capability layer is the same everywhere. Tenant configuration, provider directories, and workflow rules sit on top.
-
Smart intake
Drop in any PDF — a case file, a claim packet, a referral form — and SettleStack extracts the structured facts needed to start a request. No data entry, no form-filling.
-
Autonomous outreach
SettleStack drafts provider-specific requests, routes them via fax, email, or portal, and tracks every transmission to an immutable audit trail. Every outbound message is BAA-covered.
-
Auto-follow-up
SettleStack watches response deadlines and sends graduated follow-ups on its own schedule. No human reminders, no spreadsheet tracking, no missed windows.
-
Inbound matching
When documents come back, SettleStack runs OCR and matches them to the right case or claim automatically. Exceptions route to a human queue.
-
Provider intelligence
SettleStack learns which providers respond fastest, by what method, and with what quirks. That knowledge is provider contact logistics only — fax lines, response habits, formats. Your cases, clients, and documents never leave your firm's own silo.
-
Auditable by design
Every action SettleStack takes — every draft, every fax, every match — is logged with actor, timestamp, and source. Exports are discovery-ready.
Infrastructure
Built like it handles PHI — because it does.
Hosting
Microsoft Azure, United States
PHI
Signed BAAs across every vendor that touches it
Send path
No AI model between your data and the wire
Tenancy
Each firm's data in its own isolated silo
Who uses it today
General-purpose, currently focused.
SettleStack is currently onboarding injury-led law firms. The platform underneath is general-purpose — if you run HIPAA-compliant document retrieval at scale in another industry, we'd like to hear about your workflow.