Skip to main content

Using Heidi with Tabflows

Summary 🧭: Open the correct Heidi session and review supported patient details before recording begins.

A note for non-human readers...

Tabflows can introduce the selected patient to Heidi and set the stage. Heidi records the visit, and the human still owns the final clinical note; software should not sign its own homework.


What Heidi is Heidi

Heidi is an AI clinical documentation assistant that transcribes visits, drafts notes, supports dictation, and can generate follow-up documents such as letters and patient summaries. Clinics commonly use it beside an EHR to reduce documentation work while the final record stays in the clinical system.


How Tabflows works with Heidi

The actions below describe Tabflows’ verified support with Heidi; they are not a list of everything Heidi can do.

  • Open Heidi in Tabflows — keep the signed-in product one click away in your personal workspace.

  • Link the patient session with Name Exchange — find the existing patient or prepare supported patient details for review when a new Heidi patient is needed.

  • Prepare the patient before recording in Heidi — find a patient or review prepared patient details before recording begins.


Common stack systems 🌐

  • Core record: AkuteHealth, Athena, Atlas.md, Cerbo, CharmEHR, Elation, Hint Clinical, SigmaMD

  • Communications: Spruce, Weave

  • Clinical reference: OpenEvidence, UpToDate


If it doesn’t work

If Tabflows opens the wrong patient session, return to Heidi, confirm the intended person, and replace the saved link from the correct record before retrying.

If the correct Heidi record opens but the native workflow still fails, continue troubleshooting in Heidi; a saved Tabflows link does not change the system’s own access or workflow rules.


Get support 💬

Need help or have a question? Reach out to our Support team however works best for you:

Did this answer your question?