Does Aqurio use patient data to train AI models?
No. Aqurio does not train base models on customer PHI. Customer data is used only to operate the workflows the customer has authorised. Workflow tuning and template adjustments happen on de-identified data with explicit customer opt-in.
How does Aqurio decide when to escalate to a human?
Every workflow has explicit escalation rules: clinical urgency keywords, billing disputes, low-confidence transcription, payer denials, behavioral-health crisis language, and any patient request for a human. Escalations route to the customer's queue with full conversation context attached.
Can patients opt out of AI?
Yes. Aqurio supports per-call opt-out ("I want to speak to a person" routes immediately to staff) and per-patient persistent opt-out (chart flag respected on all future inbound). Opt-out is also captured in SMS / chat workflows and respected across channels.
How does Aqurio handle clinical advice?
Aqurio does not give clinical advice. SmartAgent answers operational questions (scheduling, eligibility, prior-auth status, billing) and triages clinical questions to the appropriate care team queue — never to a diagnosis, dosing decision, or treatment recommendation. The triage logic is reviewed quarterly by our clinical advisory bench.
What model providers does Aqurio use?
Aqurio operates a multi-model architecture: enterprise-tier LLMs from OpenAI, Anthropic, and AWS Bedrock under BAA-covered contracts, plus Aqurio's own healthcare-tuned models for tasks like clinical-terminology recognition and payer-specific document assembly. Model routing is governed by per-task confidence and safety constraints.
How is bias monitored?
Aqurio runs continuous bias monitoring across language proficiency, accent, demographic markers, and outcome equity. Every quarter we publish a customer-facing fairness report comparing AI handle outcomes across patient cohorts; deviations beyond threshold trigger model retuning under our clinical advisory bench.