- 1 Intake
Health link and check-in - 2 Match
Find the network record - 3 Reconcile
Three sources, one list - 4 Test and treat
Document the visit - 5 Return
To the network and PCP
Callable by a patient's own AI agent experiment
Most large AI assistants can now read a patient's records, but none can act at an ordinary pharmacy. This page tests a thin MCP server that lets any MCP-capable agent see open slots, ask for a refill, and, with patient authorization, read dispense history.
Endpoint: https://rxgenie.us/mcp · MCP revision 2025-06-18 · Streamable HTTP, JSON responses.
For the patient's agent
- list_open_slots: public.
- request_refill: creates a Task. A pharmacist accepts or declines it below; nothing is dispensed automatically.
- get_dispense_history, get_fill_status: need a bearer token with purpose of use PATRQT. In production that token is bound to an IAL2-verified patient; here it is a demo client key.
For clinician and care-team agents
Read-only, Treatment token (purpose of use TREAT). This is the shape of an Epic Connector: Epic said in October 2026 that outside apps will reach its agents (Art for clinicians, Emmie for patients, and custom Agent Factory agents) through MCP, with each health system approving what a connector can read.
- get_pharmacist_visit_summary: tests, treatment and its kidney-dose basis, medication therapy problems, and whether the visit reached the network and the PCP.
- get_reconciled_medications: the pharmacist's decision and reason for each medication, its sources, and refill adherence.
- list_pharmacist_tasks: follow-up Tasks sent to the PCP and the closed-loop count.
Inputs are fixed choices, not free text, and every record is synthetic. Agents that don't send an x-demo-session header share one public demo session, which has no visit. To let an outside agent read this browser's visit, send x-demo-session: 76c0facb3e784f03bc15fb85c5408684.
Refill requests from agents
No requests yet.