PharmacyLive ordering platform explained

Compounded medications for cash-pay clinics move through a defined stack: the prescriber writes the order, an ordering interface routes it, a 503A compounding pharmacy makes it, and a carrier ships it to the patient. PharmacyLive occupies the prescriber portal layer on the pharmacy side — software the compounder bought so doctors stop faxing. It is not the clinic's ordering layer and not the pharmacy fulfillment system itself, though it can integrate with systems like PioneerRx on intake.

Because PharmacyLive is pharmacy-side, its boundaries are clear: catalog depth, pricing, branding, and feature configuration belong to the deploying pharmacy. Compounding quality, certificates of analysis, fill times, and state licensure belong to that same pharmacy. Clinics inherit whatever their compounder configured — which is why multi-compounder practices often need a buyer-side layer above individual portals.

PharmacyLive controls how prescribers experience ordering within one pharmacy's deployment: catalog browse, patient profiles, SIG entry, batch multi-patient ordering, in-portal pharmacy messaging, and real-time workflow status. It also gives the pharmacy CRM dashboards, prescriber activation tracking, and growth analytics. What it does not control is cross-compounder routing — each PharmacyLive instance only knows its own catalog — or clinic-wide margin visibility across partners.

Fizy Health operates at the clinic layer above pharmacy portals. It shows pass-through per-vial 503A cost on each catalog and cart line before checkout, batches refill day across every assigned LegitScript-certified partner in one cart, validates SIGs and prescriber licensure before payment, and routes each line to the right compounder after a single checkout — whether that pharmacy runs PharmacyLive, LifeFile, or another portal on fulfillment.