Wells Pharmacy Network for clinics: who decides and who uses it

An owner should evaluate Wells on formulary fit and the total cost of the compounder relationship. Because per-Rx pricing surfaces in WellsPx3 after order placement rather than before, the owner's question is whether post-placement pricing gives enough predictability to set patient program prices, and whether the Wells formulary alone covers what the clinic prescribes. An operations lead should evaluate WellsPx3 on daily workflow: how quickly orders move through the portal, how status is tracked per patient, and whether the one-at-a-time order model fits refill volume or creates bottlenecks on busy days.

A prescriber should evaluate the submission path — WPNScripts, fax, or EMR — for speed and accuracy, and confirm that Wells is licensed to compound and ship to the states their patients are in. Each role's evaluation ends at the same dependency: whether Wells's single-compounder model is the right fit, or whether the clinic's ordering needs have grown past what one compounder portal can support.

Fizy Health serves the same three roles but in a multi-partner context. The owner gets pass-through per-vial 503A cost on every catalog and cart line before checkout, with a disclosed facilitation fee — so landed cost is visible before the order is placed, not after. The operations lead gets a single clinic cart that batches every patient's order for refill day across all assigned 503A partners, with cart validation catching SIG errors, prescriber state mismatches, and stock gaps before payment.

The prescriber gets directions and licensure checked before the order submits, reducing post-pay rejections, and support that stays in the app tied to the order and patient. The buyer map is the same as Wells; the platform behavior is different in the ways that matter when single-compounder ordering creates refill-day bottlenecks.