Order status and pharmacies

Use orders when a clinician asks about an existing order, pharmacy availability or price. Shopping is optional; it is not a routine prerequisite for prescribing.

orders

Fetch orders and available pharmacies without changing a record. Fetch one order by ID:

{ "id": "ord_existing" }

Or fetch submitted orders for a synced patient:

{
  "filter": {
    "patient": { "id": "pat_resolved" },
    "state": "SUBMITTED"
  },
  "limit": 10
}

The response contains an orders array, plus any warnings and review link. Select the intended order before requesting pharmacy options; don’t mix offers from different orders.

Compare pharmacies

Request options for the selected order, for example pickup near a postal code:

{
  "id": "ord_existing",
  "availablePharmacies": {
    "pharmacy": {
      "near": { "address": { "postalCode": "10001" } },
      "fulfillmentType": "PICK_UP"
    },
    "page": { "limit": 10, "offset": 0 }
  }
}

Input	Use
`id`	Exact order to read or shop.
`filter.patient.id`, `filter.state`	Narrow an order list.
`limit`	Maximum orders to return.
`availablePharmacies.pharmacy`	Optional pharmacy filters, such as `name`, `near` and `fulfillmentType`.
`availablePharmacies.page`	Pharmacy page `limit` and `offset`.

Read availablePharmacies.options and use nextOffset for the next page. Preserve sponsored and matching labels, price source and delivery estimates. A missing price is not zero, and an offer is not a guaranteed price. Without a pharmacy filter, results can include sponsored options. Order status can remain available when shopping is unavailable. Report the returned warning and keep the successful status result; don’t substitute another order’s offers or use a mutation to search for pharmacies.

Pharmacy changes

Use order only after the user explicitly chooses a destination for that order. Resolve the pharmacy ID from orders or another trusted source:

{
  "id": "ord_existing",
  "pharmacy": { "pharmacy": { "id": "phr_selected" } }
}

Send the pharmacy change separately from patient, prescription or submission changes. Clarify an ambiguous destination, but don’t ask for a pharmacy just because none was supplied. Omission keeps the existing assignment; pharmacy.none: true requests removal and should only be used when explicitly requested. Inspect applied and unapplied changes and the resulting pharmacy. Read the order again with orders to confirm the assignment. Photon decides whether the order can be routed or rerouted.

Explain the current status

Returned state	What it establishes
Prescription `signing.state: SIGNED`	The prescription is signed. It does not establish order submission.
Order `state: DRAFT`	The order has not been submitted.
Order `state: SUBMITTED`	Photon accepted submission. It does not establish pharmacy receipt.
`pharmacy`	The assigned destination, when present. Assignment alone does not confirm delivery.
`fulfillment`	Available fulfillment state, history, routability and exceptions. Use these to describe pharmacy progress.

If fulfillment is null or its history is empty, don’t claim the pharmacy received the prescription. Report the last confirmed milestone. Use webhooks when your integration needs ongoing updates.

Network

GraphQL

MCP

Webhooks

Order status and pharmacies

orders

Compare pharmacies

Pharmacy changes

Explain the current status

​orders

​Compare pharmacies

​Pharmacy changes

​Explain the current status

orders

Compare pharmacies

Pharmacy changes

Explain the current status