Skip to main content
MCP is available to every Neutron account for testing. Production MCP is in private preview and currently supports ChatGPT and Claude. Contact support@photon.health for access or to request approval for another client.
Send prescriptions with Photon from ChatGPT, Claude or your own agent. Ask for the prescription you want to send. Drafting and review are built into the flow; you do not need to request them separately. You can complete the flow in the conversation or continue in Prescribe. Start with what you know:
Send a prescription for amlodipine to Paige Turner.
Patient sync, medication search and order preparation are steps within that prescribing flow. The agent searches before asking for missing dosage, instructions or quantity, then gathers the details needed for the prescriber to review and approve.

Four tools

The three singular tools can change records. orders is read-only. Standalone signing through prescription is optional; Photon enforces signing requirements when you send the order. Search and ordinary draft edits do not send a prescription.

Connect

Use an MCP client with Streamable HTTP support. See Connect a client for sign-in, client approval and the upcoming production plugins.

How the workflow fits together

  1. patient → sync. Find, create or update the patient using known identity and clinical context. Match an existing patient before creating a new one.
  2. prescription → draft/sign. Start with a drug name. Include the synced patient when available so Photon has recorded allergies, medication history and benefits for the prescribing workflow. Drafting and review are built in; confirm or correct any defaults. A separate signing call is optional. You can search without a patient and attach one later.
  3. order → draft/send. Assemble the prescriptions and review the entire returned order, including screening and unapplied changes. Send with an explicit submission call after the prescriber approves.
  4. orders → fetch. Fetch the order to confirm its current state. Submission, pharmacy assignment and pharmacy receipt are separate milestones.
Don’t ask for a pharmacy as a routine prescribing step. Only include a destination on order when the user explicitly specifies one. Photon handles the fulfillment link and any fallback to a saved preference. Photon enforces permissions for every action. For an agent running on your backend, use your existing API credentials to prepare drafts, then hand them to a prescriber in Prescribe. Machine tokens cannot sign prescriptions. The agent retains the conversation and carries returned record IDs between calls. Photon stores the records. If a call returns choices or unapplied fields, resolve them and send those fields again with the appropriate ID.
Last modified on November 1, 2026