Workflow snapshot
Context in, action out — what Tabflows reads, and what it does.
Trigger
A patient sends a refill request through Spruce (or your team flags one in their thread).
Apps connected
Spruce
Elation
DoseSpotSteps
- 1Reads the request
- 2Pulls chart context
- 3Drafts the refill in DoseSpot
- 4Routes for approval
- 5Replies and charts
Action out
Refills clear the inbox in seconds — the kind of busywork that used to eat afternoons.
How it runs
Each step Tabflows takes, from the trigger to the final action.
- 1Reads the requestGatheringTabflows parses the message — medication, dose, and any quantity or pharmacy preferences the patient mentions.
- 2Pulls chart contextThinkingLast fill date, prescriber, allergies, and recent labs are surfaced from Elation alongside the message.
- 3Drafts the refill in DoseSpotDraftingThe prescription is staged with the right strength, sig, and pharmacy — pulled from the patient's preferred pharmacy on file.
- 4Routes for approvalWaitingProvider gets a one-click approve in their Tabflows queue. No more switching tabs to verify history.
- 5Replies and chartsDoneTabflows sends the patient a confirmation in Spruce and logs the refill in the Elation chart automatically.
Paste this into Assist
Drop this into Tabflows Assist and it'll set the workflow up for you.
Hey Tabflows — set up refill coordination from Spruce. When a patient messages asking for a refill, parse the med, dose, and any pharmacy or quantity hints. Pull last fill date, prescriber, allergies, and recent labs from Elation. Draft the script in DoseSpot using their preferred pharmacy on file. Route it to me for one-click approval, then reply to the patient in Spruce and log the refill in the chart.
Get this workflow
Tabflows lives in your browser, connects your tools, and quietly handles the in-between.
Get started freeGet started freeGet started freeGet started freeGet started freeRelated workflows
More workflows borrowed from the best DPC clinicians.
