How does Olympia Pharmacy handle batch refills on refill day?

For a clinic running standing protocols on Olympia's formulary — semaglutide, tirzepatide, sermorelin, NAD+, testosterone — new patient orders are a fraction of weekly volume; refills are the rest. The portal that makes refill day fast for single-compounder ordering batches the work: it shows who is due, lets staff add every refill to one cart, validates the batch once, and processes a single payment. A portal that processes one patient at a time multiplies clicks, payment steps, and error opportunities by the patient count.

Since Olympia Pharmacy's DrScript does not publicly document its refill batching behavior, treat batching and due-date surfacing as demo questions. Ask to refill twenty patients in one DrScript session and observe whether it is one checkout or twenty.

Fizy Health builds refill day around one clinic cart with per-patient lines across all assigned 503A partners: staff add every patient who is due, the whole cart is validated before payment, and checkout routes each line to the right compounder in a single run. Refill reminders flag which patients are coming due so refills are scheduled rather than chased.

The result is one build, one validation pass, and one checkout — with rejections prevented up front instead of surfacing after a batch is paid. For clinics that need medications from more than one compounder, Fizy Health handles the entire multi-pharmacy session; for clinics that only use Olympia, the question is whether DrScript supports a comparable batch capability.