Hyro's Epic Integration: Showroom Listed, But Which Workflows?

Through Epic's vendor programme interfaces, per the vendor. For scheduling, that means reading provider schedules, visit types and patient demographics and writing appointment bookings, changes and cancellations through the interfaces Epic exposes to Showroom vendors, subject to your organisation's approval of each. For MyChart password resets and account help, the agent works against MyChart's identity workflow, which means identity verification standards are your organisation's to set and Hyro's to enforce. For prescription requests, the write is usually a refill request routed to the appropriate in basket pool rather than a direct order.

The phrase "non-intrusive API" in the vendor's announcement is marketing for "we use Epic's published interfaces and do not require custom Epic build". That is good, and it is also the standard for a Showroom vendor. What it does not remove is your side: the interfaces still have to be approved, the Cadence decision trees still have to be respected by the agent's booking logic, and the identity rules for MyChart still have to be agreed. Our integration questions guide lists the questions to put to any Epic Showroom vendor.

Not published: the interface inventory per workflow, whether bookings are written directly or staff confirmed, and the Epic version floor. Ask for the technical specification your analyst will receive.

From the patient side, Hyro answers calls, web chats and texts, and completes scheduling tasks, MyChart account recovery, prescription refill requests, and routing to the right department, plus general questions about locations, hours and services. From the Epic side, the visible results are appointment changes in Cadence, MyChart account actions, and refill requests in the in basket. Call centre staff see transfers and context; clinicians see little, which is the intent.

The workflows differ in risk. Answering a question about parking is harmless. A MyChart password reset is an identity event and, done badly, an account takeover. A booking into the wrong visit type creates work and frustration. Stage them: information and routing first, confirmations and cancellations next, reschedules, then new bookings and identity workflows once your identity verification policy is agreed. Our AI phone agent use case page covers containment, abandonment and error metrics, and the patient scheduling use case covers the booking rules.

• The Showroom vendor client in your Epic instance, and each scheduling, demographic and MyChart interface it needs, raised through your integration request process.
• Cadence configuration review: which providers, departments and visit types the agent may book, and confirmation that decision trees are enforced.
• The MyChart identity verification policy the agent must follow before any account action.
• Security review and the business associate agreement, covering call and chat transcript retention, subprocessors and model training. The HIPAA and AI page lists what to insist on.
• Telephony and messaging: call recording consent by state, TCPA review for texts, and how transfers reach staff with context.
• A test plan per workflow and a change control slot for each go live.

The MyChart identity item is the one most often underestimated. It is a policy decision for your privacy officer, not a configuration setting, and it should be made before the workflow is switched on. Our governance and compliance service handles that design.

The first is transparency. Hyro's site blocks automated access, publishes no technical documentation for its Epic integration, and prices on request. That is common in the category but it means your diligence will be done through calls and documents under NDA rather than public material. Our Hyro pricing page sets out what buyers report.

The second is overlap with Epic's own tooling. MyChart self scheduling, Epic's Cheers contact centre features and Epic's own patient facing AI cover part of what Hyro does. Before buying a third party agent, ask your Epic account team what your existing licence already includes, because the comparison is often against something you have already paid for.

The third is the general voice agent risk of booking errors against complex Cadence rules. Insist on a staged rollout and on error metrics, not just containment. The AI phone agent comparison puts Hyro beside Assort Health, Notable and the other voice vendors.

• For each workflow, which Epic interfaces are used on our release, and are bookings written directly to Cadence or to a staff work queue?
• How does the agent verify identity before a MyChart action, and what is the measured failure rate?
• Which of the 20 plus Epic health systems run each workflow, and can we speak to one without the vendor present?
• Where are recordings and transcripts stored, for how long, and is any of it used to train shared models? Put it in the BAA.
• What is the price per call, per interaction or per month at our volume, the minimum term and the exit terms?
• What does the agent do when it is unsure, and how quickly does it hand off to a person with context?

Our vendor HIPAA question list covers the compliance side in more depth.

Hyro's Showroom listing and health system references make it a credible Epic option for patient access, and the decision is about which workflows to give it, how to stage them, and whether your existing Epic licence already covers some of the ground. An independent review works through the interface specification with your Epic team, designs the identity policy for MyChart workflows, sets the staging and the error metrics, and compares price and fit against the other voice vendors and against Epic's own tooling. We take no vendor commissions.

Our vendor selection service runs that comparison and our deployment roadmap sequences the workflows. Book a call with your call volumes, your Epic release and your MyChart adoption rate.