The hospital, not Epic, decides what a patient can ask an AI.

When a vendor sells to hospitals, the patient is a user, not a customer, and that distinction is now the only thing that matters about "patient-facing" AI. Epic's customer is the hospital. The hospital decides which MyChart capabilities ship, including the brand new "Emmie" patient agent. The hospital also pays the token meter every time Emmie answers. That is the actual control surface for patient AI in U.S. healthcare, and it sits one rung above the patient and one rung below the vendor.

Millenson's column in Forbes makes the structure legible by listing what the hospital gates: the feature flag, the billing model, and the very fact of whether a patient can ask an AI a question grounded in their own chart. TechTarget's separate writeup of "Ask Emmie" confirms the agent handoff pattern: when a chat becomes clinical, the hospital route takes over, and the transcript can be hidden from the care team. The patient gets the conversational surface. The hospital keeps the rails.

A vendor's incentive tracks its customer. Epic's revenue per token follows the hospital's decisions, so the feature roadmap bends toward whatever the CIO will turn on, not whatever the patient wants answered. The repeatable mechanism is plain: in B2B2C software, the "consumer" feature is a product the enterprise customer controls, and the per-use meter is the cleanest tell of where the incentive actually lives. Watch the meter. That is where the strategy shows up before the press release does.