See How We Built It
Clear Mind Life is not a monolith. It's an orchestration layer built on three world-class APIs — each doing exactly what it was built for, wired together by autonomous agents.
AssemblyAI
Every provider loses 2+ hours a day documenting what they just said. We eliminated that entirely. The Encounter Agent connects to AssemblyAI's real-time streaming WebSocket API during telehealth sessions — transcribing speech in under 300ms, mapping clinical keywords to ICD-10 codes, and constructing a SOAP note before the physician even hangs up.
We open an AssemblyAI WebSocket session at visit start and stream PCM audio chunks. Partial transcripts fire in <300ms.
AssemblyAI labels "Patient" vs "Provider" segments. Our NLP pipeline processes each speaker separately to extract clinical context.
After session end, we pass the full transcript to LeMUR with a clinical SOAP prompt. Output is structured JSON mapped to FHIR Observation resources.
AssemblyAI PII redaction fires before any text touches our FHIR pipeline — zero PHI leaks into the LLM layer.
NexHealth
The moment a patient books an appointment, a race begins: verify insurance, confirm demographics, send intake forms, collect payment. Most practices lose this race. By wiring the NexHealth API to our Receptionist Agent, we win it automatically — hours before the patient arrives.
NexHealth fires a webhook the moment an appointment is created. Our agent immediately kicks off an insurance eligibility check via the X12 270 EDI pipeline.
We pull the patient's demographics, insurance info, and appointment history via the NexHealth REST API and store them as FHIR Patient and Coverage resources.
We use the NexHealth Forms API to push AI-generated intake questionnaires directly to the patient's phone — pre-filled with existing demographics, requiring only signature.
After insurance is verified, we calculate the exact copay via X12 271 and push a Stripe payment link into the NexHealth message thread — cash collected before the visit.
Twilio
Denied claims don't have to sit in a queue for 90 days. Our Billing Agent uses Twilio Programmable Voice to automatically call payers, navigate IVR trees, and document denial reasons — then uses Twilio SMS to keep patients updated on their balance and payment status in real-time. No human billers on hold.
When a claim is flagged for denial risk, the agent initiates a Twilio outbound call to the payer's provider services line. TwiML scripts navigate IVR trees and capture denial codes via DTMF and speech detection.
After each claim milestone (submitted, approved, underpaid), we send a Twilio SMS to the patient with their balance, EOB summary, and a secure payment link — no confusing paper bills.
For international or preferred patients, we deliver the Explanation of Benefits as a WhatsApp message via the Twilio Business API — same data, frictionless UX.
Every call outcome (IVR navigation result, denial code captured) fires a webhook back to our FastAPI backend, triggering the next step in the appeals workflow automatically.
How They Work Together
Each API handles one layer of the revenue cycle. Our orchestration layer connects them into a single, autonomous pipeline.