Skip to content

Coordinate refill requests from Spruce to Elation

Refill requests become reviewed drafts and chart-ready follow-up.

  • Spruce
  • Elation
  • Saves about 8 minutes per refill

The situation

An authorized clinic user starts the workflow from a refill request in Spruce, or from a thread the team has flagged. Runs in the authorized clinic user's active browser session and uses the systems the user is already signed into.

When an authorized clinic user starts from a refill request in Spruce, Tabflows pulls in chart context, sorts the request for the prescriber's decision, and drafts patient follow-up for review without claiming unattended delivery or chart writing.

Steps

  1. Reads the request Tabflows parses the message — medication, dose, and any quantity or pharmacy preferences the patient mentions.
  2. Pulls chart context Last fill date, prescriber, allergies, and recent labs are surfaced from Elation alongside the message.
  3. Sorts the refill queue Refill requests in the Elation practice queue are grouped apart from scheduling, labs and urgent clinical work, with the medication, quantity and directions, and Elation's controlled-substance flag.
  4. Prescriber decides The prescriber approves, changes or declines the refill and e-prescribes it from the EHR or prescribing tool. Tabflows never issues a prescription.
  5. Prepares reply and chart note Tabflows drafts the Spruce confirmation and chart note so the clinic can review and complete the follow-up.

The outcome

Refills move from inbox request to a prescriber's decision, an approved patient reply, and a chart-ready note.

Ask Sidekick

Sidekick is the AI assistant inside Tabflows.