Design AI surfaces around each role's workflow
A beautiful chatbot in a new tab loses to the EHR inbox nurses already race through between rooms.
Anthony Hildoer
June 10, 2026 · 6 min read
You launched a polished chatbot. Nursing never opened it. Revenue cycle kept Excel. Patients called the desk anyway. The post-mortem blamed "change management." Often the real issue is workflow orphan: AI outside the path where work already happens. Interface strategy starts with the role and their existing software.
One bot is procurement convenience
The usual play: single patient-and-staff chat, one brand, one vendor roadmap. Cognitive fit differs:
- Patient: mobile, anxious, after hours; async works; escalation to a human must be obvious; plain language
- Nurse: seconds between rooms; in-chart card beats a conversational novel; tap-to-accept draft
- Biller: dense tables and copy-paste codes; desktop sidebar beats emoji chat
- Executive: exceptions and dollars; dashboard beats dialogue
Role-first interface means one orchestration backbone and multiple surfaces tuned to mental models.
The tab tax
Every new login is a tab tax on adoption. Clinicians already pay it with the EHR. Funding another "AI portal" is a second job. SSO inheritance and embedded panels beat avatar animations.
"Omnichannel experience" sounds patient-friendly. Staff adoption is where most healthcare AI ROI dies. Phase one should name a primary role, then ship where that role already works.
One brain, many surfaces
Reuse models, gateway, knowledge, and orchestration. Interface is less reusable: patient UI hides internal codes; biller UI shows them. That is respect for practice rather than duplicate engineering for its own sake.
Executive decision for phase one
Pick the role that earns the outcome you promised the board:
- Access: patient plus scheduling embed
- Margin: rev-cycle sidebar
- Quality: clinician in-chart draft with human checkpoints
Skip funding a generic chat until that role ships inside their primary application.
A chatbot floating beside the EHR is the adoption failure mode most teams hit first. Once you pick a primary role, the win is embedding where they already work without another login.