Treating each patient order as a separate checkout session forces ops staff to repeat login, validation, and payment for every line on refill day — the opposite of how high-volume cash-pay clinics actually work. Fizy Health provides one cart per clinic where every line ties to a patient, the same SKU can appear for different patients, duplicate patient-SKU pairs merge quantity, and the whole refill cohort checks out with a single payment across assigned 503A partners.
If refill day still means one checkout per patient, this page explains how one cart for every patient works on Fizy Health.
Cash-pay clinics batch refills for dozens of patients every Friday — but per-patient portal checkouts made ops treat each order as an island. Fizy Health matches how ops actually works: one clinic cart holding every patient who needs an order today.
Ops leads describe these results after one clinic cart becomes the refill day standard — faster builds, cleaner validation, and checkout once for the whole cohort.
Add new starts and refills for every patient who needs an order today to a shared clinic cart. Ops builds the whole refill cohort in one session instead of restarting checkout for each patient.
Refill day finishes with one payment, not dozens.
Each cart line ties to a patient. The same SKU for two different patients appears as separate lines; re-adding the same patient and SKU merges quantity instead of duplicating — clean data for validation and routing.
Cart state that matches how ops thinks about refill day.
Cart validation runs on every patient line before the single checkout. SIG, licensure, and stock issues surface once for the whole cart — fix everything, then pay once.
Fewer partial refill days stuck mid-validation.
After one payment, multi-pharmacy routing sends each line to the correct assigned compounder. Patient context travels with the line — no manual split by pharmacy after checkout.
Per-patient fulfillment without per-patient checkouts.
One cart for every patient on Fizy Health is the core wedge for cash-pay clinic ordering — here is the workflow ops teams adopt.
One cart exists per clinic per organization. Ops opens the shared cart and begins adding every patient who needs an order today — new starts and refills in the same build session.
Search the formulary, select SKU, and tie each line to a patient. Pass-through landed cost appears on every line. Same SKU for different patients adds separate rows; same patient-SKU re-add merges quantity.
Run cart validation across every patient line. Fix SIG, licensure, or stock flags while the whole cohort is still editable — then proceed to checkout with confidence.
Submit one payment for the entire cart. Each patient line routes to the correct 503A partner with per-line status — fulfillment per patient, checkout per clinic.
These product surfaces power the shared clinic cart — the core wedge behind one cart for every patient on Fizy Health.
Build the whole refill day in one clinic cart and submit a single payment across new starts and refills.
Validation catches SIG, licensure, and stock issues on every patient line before you pay.
A single payment routes each patient line to the right partner with per-line tracking.
Each clinic has one shared cart per organization. Ops adds every patient line for refill day to that cart — each line tied to a patient — then validates and checks out once. One payment routes each line to the correct 503A partner.
Yes. The same SKU for different patients appears as separate cart lines, each tied to its patient. Re-adding the same patient and SKU merges quantity instead of creating a duplicate row.
Once per clinic cart. You build every patient line for refill day, validate the full cart, and submit a single payment. Multi-pharmacy routing handles per-line fulfillment after checkout.
Cart validation runs before checkout on every line in the cart — SIG, licensure, stock, and data completeness per patient. Fix all flagged lines, then checkout once on a validated cohort.
No. Fizy Health ties order lines to patients for pharmacy fulfillment and audit. Clinical documentation stays in your EMR — the cart is the ordering layer for 503A volume.
Start free with patient-linked lines, validation before payment, and single checkout across every 503A partner.