Fizyhealth
Promise Pharmacy prescription submission flow

How the Promise Pharmacy prescription submission flow works

The Promise Pharmacy prescription submission flow moves a patient-specific compounded prescription from prescriber authorization into Promise's in-house 503A pharmacy: the provider enters or transmits the Rx through the portal or REST API, Promise verifies the SIG, prescriber licensure, and compound availability, then queues accepted prescriptions for compounding and direct-to-patient shipment. Promise both receives and fills the prescription — there is no external partner pharmacy handoff.

This page details how prescriptions enter Promise's workflow, where verification fails on refill day, and how Fizy Health validates Rx details before checkout when you batch across multiple 503A partners.

Compare Fizy Health vs Promise Pharmacy

Proudly Partnered With

The submission steps

From prescriber authorization to Promise verification

Promise describes e-prescribing workflow setup and API integration on its telehealth pages. Confirm eRx vendor specifics during onboarding.

  1. 01

    Prescriber authorizes the compounded Rx

    A licensed provider evaluates the patient and authorizes the compounded medication — strength, quantity, and directions for use — for a specific patient in a state where Promise is licensed to ship.

  2. 02

    Submit through portal or API

    Clinic staff enter the order in the provider portal, use configured e-prescribing workflow, or transmit via REST API endpoints after telehealth integration setup. Test orders run the full Rx-to-delivery path before launch.

  3. 03

    Promise pharmacy intake verifies the Rx

    Promise's in-house pharmacists verify the prescription, prescriber credentials, patient eligibility, and compound availability. Custom formulations may involve pharmacist collaboration on strength and dosage form.

  4. 04

    Quality review and compounding queue

    Accepted prescriptions enter compounding with USP 795/797/800 compliance, third-party potency testing, and sterility testing. Certificate of Analysis documentation is available per batch through the portal.

  5. 05

    Dispense and ship direct-to-patient

    Promise dispenses and ships to the patient — white-label packaging for qualified partners — with tracking and fulfillment analytics returned to the portal reporting dashboard.

Where it breaks

  • SIG rejected at verification

    Non-standard or incomplete directions for use return for correction, restarting the timeline — painful when fifty refills hit verification the same afternoon.

  • Prescriber-state mismatch

    Promise ships to 42 licensed states; a prescriber not licensed in the patient's state blocks the Rx until rerouted or corrected.

Why the prescription handoff is where refill day breaks

Every compounded prescription must pass SIG completeness, prescriber licensure, and stock availability before compounding starts. On refill day, those checks multiply by patient count. Promise verifies in-house, which keeps the chain short, but a per-patient submission flow means each Rx is tested individually — and each rejection becomes its own recovery loop while the rest of the queue waits.

Fizy Health validates prescription details before they leave your clinic cart. SIGs, prescriber state licensure, and stock are checked before payment across the whole batch, so the Rx Promise or another assigned partner receives is one it can fill. That is especially valuable when refill day mixes Promise lines with SKUs routed to other 503A partners in one checkout.

Is Promise-only Rx submission enough — or do you batch across compounders?

Promise Pharmacy fits if

Promise Pharmacy

Every prescription compounds at Promise and portal submission fits your volume.

  • Your protocols map to Promise's formulary and in-house verification is fast enough for your refill cadence.
  • E-prescribing or API integration covers your telehealth Rx volume without a separate batch layer.
  • Your prescribers rarely hit SIG or cross-state licensure issues on refills.
Consider Fizy Health if

Fizy Health

You want Rx details validated before submit across a whole refill batch.

  • You batch dozens of refills and want SIG and licensure checked once before payment — not patient by patient after rejection.
  • You route some lines to Promise and others to different 503A partners in one prescriber-side cart.
  • You want directions-for-use support that keeps SIGs fillable across GLP-1 titration changes.
If you choose Fizy Health

What pre-submit prescription validation gives you.

Promise verifies Rx details in-house. These outcomes help when refill day is a batch across partners.

See all features
Keep evaluating the flow

More on how prescriptions move through Promise Pharmacy.

See the full workflows guide
FAQ

Promise Pharmacy prescription submission — common questions.

  • Flow

    How does a prescription get submitted to Promise Pharmacy?

    A prescriber authorizes the compounded order, then clinic staff submit through the provider portal, configured e-prescribing workflow, or REST API. Promise's in-house 503A pharmacy verifies and compounds — there is no external partner handoff.

  • Role

    Does Promise Pharmacy fill its own prescriptions?

    Yes. Promise is a state-licensed 503A compounding pharmacy. It verifies, compounds, quality-tests, and ships direct-to-patient rather than routing Rx to another compounder.

  • SIG

    Why do compounded prescriptions get rejected at Promise?

    Common reasons are incomplete or non-standard SIGs, prescriber licensure mismatches for the patient's state, or unavailable compound stock. Each rejection on refill day adds a correction cycle.

  • Telehealth

    Does Promise Pharmacy support API prescription submission?

    Yes. Promise publishes REST API endpoints for order submission, status tracking, and patient notification, with engineering support during telehealth integration setup.

  • Validation

    When does Promise Pharmacy verify the prescription?

    Verification happens at Promise's in-house pharmacy after portal or API submission. Fizy Health additionally validates SIGs, licensure, and stock before checkout when you batch across assigned partners.

  • Comparison

    How is the Fizy Health submission flow different?

    Fizy Health validates Rx details before checkout and lets prescribers submit many patients through one cart across multiple 503A partners. Promise verifies in-house for Promise SKUs submitted one patient flow at a time.

Sources reviewed June 2026

  • Promise Pharmacy public website — provider, telehealth, and partner program pages (promisepharmacy.com/providers/), reviewed June 2026.
  • General 503A prescription verification practice.
  • Fizy Health platform capabilities reflect the live product.
Evaluate with real numbers

Hand off prescriptions the pharmacy can actually fill — in batch.

See how Fizy Health validates SIGs, licensure, and stock before checkout across your whole refill list. Free to start.

Start Ordering FreeFizy Health vs Promise Pharmacy