I am Arohi
Ascending Care. Every Patient.
The practice management intelligence in the DNAi Healthcare Fleet. Arohi serves clinicians directly. She manages patient longitudinal data, surfaces clinical alerts from data contradictions, anticipates scheduling and billing needs, and gives decision support in clinical terminology.
Try Arohi via API Schedule a clinic demoPhysician-facing · Clinical terminology · API-only today
What Arohi Does
The brilliant practice manager who anticipates needs. Arohi runs alongside the clinician, in clinical terminology, in service of the patients on the schedule.
Patient scheduling
Appointment management, follow-up tracking, and overdue-visit flagging across the longitudinal record. Arohi surfaces who has slipped through the cracks.
Billing intelligence
Claims awareness, denied-claim flagging, and coding-aid context for the encounter. The clinician confirms; Arohi prepares the structure.
Clinical alerts
Generated from patient-data contradictions. Missed appointments combined with declining metrics, a new prescription that interacts with an existing regimen, or a positive screening result with no follow-up: Arohi raises the flag.
Physician decision support
Differential cues, guideline-aligned next-step suggestions, and drug-interaction context. Grounded in StatPearls and current clinical guidelines.
Practice analytics
No-show patterns, panel-level adherence rates, screening-rate gaps, and population-level trends. Useful for QI reviews and MIPS reporting.
EHR-adjacent workflows
Arohi is a parallel intelligence to your EHR. She reads structured records via integration, surfaces context the EHR buries, and hands off back to the system of record.
How Arohi Is Grounded
Arohi runs in platform mode with boosts defined in agents/arohi/agent.yaml. The collection mix balances clinical depth against communication-tone fidelity.
| Collection | Boost | Scale | What it carries |
|---|---|---|---|
statpearls_clinical |
1.4x | 76K articles | Peer-reviewed clinical reference, the standard bedside source |
clinical_guidelines_v3 |
1.4x | varies | Current specialty-society practice guidelines (third-generation index) |
clinical_communication |
1.4x | varies | Clinician-to-clinician communication norms, sign-out, consult-letter style |
drug_interaction_knowledge |
1.3x | varies | Drug-drug and drug-condition interactions for polypharmacy awareness |
patient_communication |
1.3x | varies | Patient-facing communication patterns, used when Arohi drafts patient-facing text on the clinician's behalf |
wikipedia_medical |
1.1x | varies | Background medical reference for broad context |
Sacred Constraints
Arohi serves clinicians. That changes which guardrails apply and which intentionally do not.
Auditability
Every alert and every recommendation is traceable to the source data and the corpus citation behind it. Arohi maintains an audit log of decision-support touchpoints.
HIPAA boundary
Patient-identifying data stays within the practice tenant. Arohi runs under DNAi's BAA-covered Vertex AI infrastructure for any LLM call that touches protected health information.
Audience is the clinician
The behavior flag suppress_medical_disclaimers: true is set deliberately in agents/arohi/agent.yaml. The audience is the clinician, not the patient. A trained physician does not need a "consult your doctor" footer on every answer. Disclaimer suppression is contextually correct; it is not a fiduciary shortcut.
No direct patient interaction
Arohi does not chat with patients. She prepares context, drafts, and alerts for the clinician. The clinician owns the patient-facing communication and signs off on every decision.
Emergency escalation preserved
Even with disclaimers suppressed, emergency-flag detection (suppress_emergency_flags: false) remains active. Critical-value labs, suicidality, and acute decompensation are escalated regardless of conversation flow.
Medical contract active
The fiduciary medical contract (apply_medical_contract: true) governs Arohi's output. Asha's other Sacred Refusals (no fabricated citations, no overstated certainty, no fluency over safety) all apply.
How to Reach Arohi
Arohi has no consumer surface today. Clinical pilots run by appointment.
Developers and integrators
Get an API key at dnai.systems/developers. Call POST /a2a/v1/message:send with agent_id: arohi. Wire her into your EHR-adjacent tooling or care-coordination workflow.
Practices and clinics
For a guided pilot in your practice, email the team. We will scope integration, data-residency, and BAA needs before a single PHI byte moves.
Frequently Asked Questions
suppress_medical_disclaimers: true deliberately. A "please consult a doctor" footer on every answer wastes a clinician's time and signals that the agent does not understand its audience. Emergency-escalation behavior and the fiduciary medical contract remain active.