Skip to main content
MCP is open to every Neutron account. In production, it’s in private preview: see client approval or contact support@photon.health.
Your clinical agent reads the encounter, syncs the patient, searches medications and prepares draft prescriptions. A prescriber then opens the drafts in Prescribe to review, sign and submit the order.

1. Connect the agent

Point your agent’s MCP client at the Neutron server:
The agent authenticates like any other caller. A backend agent uses a machine token. An agent that runs in a prescriber’s MCP client, such as Claude or ChatGPT, signs in as that prescriber. See Connect a client.

2. Sync the patient and draft prescriptions

Use patient to sync the patient: find, create or update from the encounter context. Match an existing patient before creating a new record. Supply known allergies, medication history and diagnoses when available. Then call prescription with treatment.name and the resolved patient.id. Search before asking for missing dosage, directions or dispense details. If identity is unresolved, you can search without a patient and attach one later. Use returned choices and changes.unapplied to complete the draft. Keep any returned prescription ID and resend pending fields when resolving a choice. Show draft defaults and screening to the prescriber for review; don’t invent missing clinical details or treat a medication match as a complete screen. If the encounter changes, update the patient and prescription as needed, then obtain a fresh review. See Prescribing tools for input examples and continuation rules.

3. Hand the drafts to a prescriber

Pass the patient and the draft prescriptions to Prescribe. The prescriber sees each draft with its screening, signs, and sends.
To hand over a single ID, call the MCP order tool with the patient and prescription IDs, then open the returned order in Prescribe. The call may resume an existing draft, so review every prescription it returns.

Sending from the agent

An agent acting for a signed-in prescriber can use the same MCP tools for finalization after explicit review and approval. A separate prescription call can optionally sign reviewed content using its content hash. order with only id and state: "SUBMITTED" requests submission. Photon enforces authorization and signing requirements as part of sending; the user does not need to request a draft or a separate signing step. Don’t ask for a pharmacy unless the user explicitly requests a destination. Read back with orders and distinguish submission from pharmacy receipt. See Sign a reviewed prescription and Submit the reviewed order.
Last modified on November 1, 2026