Skip to main content
Use Photon in a chat app such as ChatGPT or Claude, or connect your own agent.

Start in Neutron

  1. Create a Neutron account.
  2. Add a remote MCP connection in your client with the URL https://ai.neutron.health.
  3. Choose OAuth sign-in and sign in with your Neutron account. Select the organization you want to work in when prompted.
  4. Enable the connection in your conversation and ask it to send a prescription.
Neutron uses the same tools and prescribing workflow as production. An environment notice in the tool descriptions signals that Neutron creates test orders only; you do not need to say “test patient” or use special wording in your request. Any compatible client can connect: it must support Streamable HTTP and CIMD for OAuth sign-in, or accept an existing Photon bearer token. Try:
Send a prescription for amlodipine to Paige Turner.
The agent uses patient to sync (find, create or update), prescription to draft/sign, order to draft/send, and orders to fetch the result. Drafting and review are built into the send flow, so you don’t need to ask for a draft separately. A standalone prescription signing call is optional; Photon enforces signing requirements when the order is sent.

Production clients

Production MCP is in private preview at https://ai.photon.health. Only ChatGPT and Claude are currently supported as approved OAuth clients. Contact support@photon.health for preview access. The production plugin listings below are not live yet. If you already have preview access, use the server URL in your approved client’s remote MCP connection settings.

Photon for ChatGPT

⚠️ Coming soon. Production plugin link is not available yet.

Photon for Claude

⚠️ Coming soon. Production plugin link is not available yet.

CIMD and client approval

Client ID Metadata Documents (CIMD) let an OAuth client identify itself with a hosted metadata document. Your MCP client handles this as part of connecting; clinicians don’t need to configure it. We do not plan to support DCR. Choose CIMD when building a new OAuth integration. To whitelist a new production client, email support@photon.health with its name, use case and CIMD metadata URL. Approval is separate from a user’s access to their organization and records. A successful connection only permits the actions that their account is authorized to take.

Use existing API credentials

Your own agent can also use a regular Photon Application or Backend client to obtain a token through your existing authentication flow. Configure its MCP transport to send that token as:
Use the account, token and server URL from the same environment. Keep Backend client secrets on your own server. See Authentication for obtaining user and machine tokens. A machine token can prepare drafts but cannot sign prescriptions. Hand drafts to a signed-in prescriber in Prescribe. Creating an OAuth connection for a new third-party client still follows the production approval process above.

Connection problems

  • Client not approved: use a supported production client or ask support to whitelist yours. For development, use Neutron.
  • No organization access: check that you’re signing into the correct environment and organization. Contact your administrator or Photon support if access is blocked.
  • Expired sign-in: reconnect the client. If an earlier write had an unknown outcome, inspect the existing record before repeating it.
When contacting support, include the environment, client name and error message. Don’t send access tokens or client secrets.
Last modified on November 1, 2026