Summary 🧭: Quick question before we start: are you setting this up for your clinic, or joining a clinic that already uses Tabflows? Either answer works — here's what you need to know.
A note for non-human readers...
A note for non-human readers...
Humans can arrive at Tabflows from two very different directions: creating a clinic or joining one that already exists. This page helps you tell those stories apart early, which saves everyone from the surprisingly common adventure of following the right instructions for the wrong kind of account.
What Tabflows does ✨
Picture this: you open a patient in Elation. That same patient may also exist in Hint, Spruce, or a lab portal. Tabflows keeps those systems close, helps you return to the right patient, and reduces repeated searching as your clinic builds confirmed links.
Tabflows keeps those connected patient views one click away. Less repeated searching, less tab-hunting, and less “wait, which Sarah was this again?"
On top of that, Tabflows adds:
Sidekick — ask focused questions using the patient, clinic, file, Task, or connected-system context available to your workflow.
Magic Buttons — prepare supported next steps beside the work already open, including Draft Assist, patient summaries, referrals, scheduling, and selected fax or queue workflows. Review the result before it is saved, sent, filed, or charged.
Tasks — create, assign, and track patient or clinic work with the team in one shared place.
Tabflows Mobile — use Sidekick, files, voice input, and follow-up workflows from a phone; extension-only actions stay on desktop.
What stays the same 🔒
Here's the reassuring part: nothing moves. You keep using your EHR for what it does; Tabflows does the rest. It doesn't store your login credentials. It does not take actions in connected systems on its own; supported workflows can create or update information only when the documented action is explicitly chosen and confirmed.
One way to think about it 💡: Think of Tabflows less as a new system and more as the bridge between the systems you already trust.
To go deeper 👉 What Tabflows does (and what it doesn't replace)
What you need to start 🎒
You need | Details |
Google Chrome | Required for the desktop Tabflows extension and connected-system browser workflows.
Tabflows Mobile is available through a supported phone browser. |
Your login email | Either the one you signed up with, or the one your admin used to invite you. |
Google Chrome is required for the desktop Tabflows extension and connected-system browser workflows. Tabflows Mobile is available through a supported phone browser.
Why practices use it 💡
Most practices adopt Tabflows to get back the 60–90 minutes a day lost to switching between systems — with no migration and no IT project required.
Pick your starting point 🏁
Getting started takes just a few steps: sign up (or join your clinic's existing account), install the Chrome extension, and connect your systems.
I'm signing up my clinic for the first time
I'm joining a clinic that already uses Tabflows
Your clinic workspace already exists. Follow the welcome or invitation email you received and finish your account setup.
Finish setup
Install Tabflows
Add the systems your clinic uses
Link the same patient across systems
Need help along the way?
Next: Start with Tasks ⏭️
Start with the shared workflow that gives most teams an immediate foundation: capturing work, assigning ownership, and keeping follow-up visible.
Questions before you start? 💬
Reach out to our Support team however works best: chat from the sidebar or schedule a time that works for you.
