How AmarilloMD uses Tabflows and Sidekick to bring AI into the clinical workflow
AmarilloMD shows what happens when AI sits inside the workflow instead of beside it. Sidekick becomes more useful because it lives near the patient context and the tools the clinic already uses, across three Texas Panhandle locations.
AmarilloMD TL;DR
- AmarilloMD pairs Sidekick with SideTab as its daily clinical operating surface.
- The practice has run as a direct primary care clinic since 2016, founded by Dr. Deborah Moore.
- AmarilloMD now serves three Texas Panhandle communities: Amarillo, Dumas, and Hereford.
The problem
AI can be impressive and still fail inside a clinic if it is disconnected from the work. A separate chat window does not know which patient the team is looking at, which tools are open, or what needs to happen next.
“DPC clinics need AI that shows up where the work already happens.”
DPC clinics need AI that shows up where the work already happens, not in a tab of its own.
Why Tabflows
Tabflows gives AmarilloMD a single surface for SideTab navigation and Sidekick support. SideTab handles movement across the clinic stack. Sidekick brings AI into the same workflow layer.
The result is a stronger story than adding AI on the side. It is putting AI where clinical work actually happens.
What changed
AmarilloMD's usage pattern points to a clinic using Tabflows as part of daily navigation across three locations, with Sidekick activity showing AI becoming part of the same operating rhythm.
The story here is practical AI adoption grounded in clinical protocol work and patient-record context, not a novelty feature bolted onto the side.
