# Refill Coordination from Spruce to Elation > Refill requests become reviewed drafts and chart-ready follow-up. Markdown view of https://www.tabflows.com/workflows/refill-coordination — the HTML page is canonical. 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. [Get Tabflows free](https://www.tabflows.com/) Free to start. No credit card required. ## Workflow snapshot Context in, prepared action out — what Tabflows reads in a user-started browser session, and what it stages for review. ### Initiation An authorized clinic user starts the workflow from a refill request in Spruce, or from a thread the team has flagged. User-initiated. Runs in the authorized clinic user's active browser session and uses the systems the user is already signed into. ### Apps connected Spruce Elation ### Steps 1. 1Reads the request 2. 2Pulls chart context 3. 3Sorts the refill queue 4. 4Prescriber decides 5. 5Prepares reply and chart note ### Action out Refills move from inbox request to a prescriber's decision, an approved patient reply, and a chart-ready note. Tabflows does not store EHR credentials, does not independently initiate EHR access, and prepares work for review rather than acting as an open-ended autonomous EHR agent. Saves ~8 minutes per refill ## How it runs Each step Tabflows prepares, from user initiation to clinic review. 1. 1Reads the requestGatheringTabflows parses the message — medication, dose, and any quantity or pharmacy preferences the patient mentions. 2. 2Pulls chart contextThinkingLast fill date, prescriber, allergies, and recent labs are surfaced from Elation alongside the message. 3. 3Sorts the refill queueDraftingRefill 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. 4Prescriber decidesWaitingThe prescriber approves, changes or declines the refill and e-prescribes it from the EHR or prescribing tool. Tabflows never issues a prescription. 5. 5Prepares reply and chart noteDoneTabflows drafts the Spruce confirmation and chart note so the clinic can review and complete the follow-up. ### Paste this into Assist Drop this into Tabflows Assist to set up the reviewed workflow. Hey Tabflows — set up user-initiated refill coordination from Spruce. When I choose a patient refill message, parse the med, dose, and any pharmacy or quantity hints. Pull last fill date, prescriber, allergies, and recent labs from Elation, and tell me if Elation flags it as a controlled substance. Once I've decided, draft the patient reply in Spruce and prepare the chart note for review. ### Get this workflow Tabflows lives in your browser, our team connects your tools, and the workflow quietly prepares the in-between work. [Get started free](https://www.tabflows.com/) ### Related workflows More workflows borrowed from the best DPC clinicians. Visit Notes to Tasks with AI Scribes Visit notes become reviewed chart updates and follow-up tasks. Lab Result Follow-Through Lab results become reviewed triage and follow-up drafts. New Patient Onboarding from Hint to Elation Membership sign-ups become reviewed onboarding drafts. ## How this workflow runs 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. - Trigger: An authorized clinic user starts the workflow from a refill request in Spruce, or from a thread the team has flagged. - Initiation mode: User-initiated - Access model: Runs in the authorized clinic user's active browser session and uses the systems the user is already signed into. - Capability caveat: Tabflows does not store EHR credentials, does not independently initiate EHR access, and prepares work for review rather than acting as an open-ended autonomous EHR agent. - Outcome: Refills move from inbox request to a prescriber's decision, an approved patient reply, and a chart-ready note. - Time saved: ~8 minutes per refill - Systems involved: Spruce, Elation 1. **Reads the request** (context) — Tabflows parses the message — medication, dose, and any quantity or pharmacy preferences the patient mentions. 2. **Pulls chart context** (context) — Last fill date, prescriber, allergies, and recent labs are surfaced from Elation alongside the message. 3. **Sorts the refill queue** (context) — 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** (review) — 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** (prepared_action) — Tabflows drafts the Spruce confirmation and chart note so the clinic can review and complete the follow-up. Reported by Dr. James Gaor, Halcyon Health. ## Related markdown Section index: [Workflows](https://www.tabflows.com/workflows.md) Alongside this page: - [Lab Result Follow-Through](https://www.tabflows.com/workflows/lab-result-follow-through.md) - [New Patient Onboarding from Hint to Elation](https://www.tabflows.com/workflows/new-patient-onboarding.md) - [Visit Notes to Tasks with AI Scribes](https://www.tabflows.com/workflows/visit-notes-to-tasks.md) Start here: - [Tabflows](https://www.tabflows.com/index.md) - [Tabflows pricing](https://www.tabflows.com/pricing.md) - [Tabflows FAQ](https://www.tabflows.com/faqs.md) - [About Tabflows](https://www.tabflows.com/about.md) - [Contact Tabflows](https://www.tabflows.com/contact.md) - [DPC workflow software](https://www.tabflows.com/dpc-workflow-software.md) - [Directory](https://www.tabflows.com/directory.md) - [DPC finder](https://www.tabflows.com/dpc-finder.md) - [Roi](https://www.tabflows.com/roi.md) Every page listed in sitemap.xml has a markdown twin at the same URL with `.md` appended, or by sending `Accept: text/markdown` to the canonical URL. Wider index: [llms.txt](https://www.tabflows.com/llms.txt), [llms-full.txt](https://www.tabflows.com/llms-full.txt), [sitemap.md](https://www.tabflows.com/sitemap.md), [sitemap.xml](https://www.tabflows.com/sitemap.xml). Support documentation: https://www.tabflows.com/university/library — append `.md` to any article URL for its raw markdown.