Agentic Index
Hyro vs Luma Health (2026)
Both vendors last verified
Hyro puts specialized AI agents on a health system's patient calls and messages, while Luma Health runs the patient's whole path from referral to payment on one platform. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Both sell through a demo with no public price. Hyro's Care OnCue runs more than 20 agents, each owning one job from routing and scheduling to prescriptions and IT password resets. They answer only from a knowledge graph of sources the organization approves, so every answer can be traced to where it came from. Care Intelligence scores every conversation for adherence and hallucinations, and Outbound OnCue runs reminder and follow up campaigns. Luma Health covers access, outreach, intake and payments. Its Navigator answers and calls patients and remembers each of them across calls, texts and chats. Named agents for scheduling, referrals, eligibility and payments work together. Fax Transform turns incoming faxes into referrals and orders in the EHR, and staff review whatever falls below a confidence threshold. Choose Hyro for a contact center front door where every answer can be traced. Choose Luma to run the whole path from referral to payment, faxes included.
On the Agentic Index healthcare agent ranking, neither Hyro nor Luma Health clears the bar, which asks for all five chart loop capabilities documented in full. Hyro does not document security and identity governance in full, nor human oversight and guardrails; Luma Health does not document knowledge grounding and RAG in full. 4 of the 69 vendors in the lane clear it. See the healthcare agent ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Hyro and Luma Health are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,084 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
This comparison, as a video
Hyro vs Luma Health in 4 minutes
A short walkthrough of what each product does, how they are priced, where they overlap and when to choose each.
Choose Hyro if
- Every answer should come only from sources you approve, and be traceable to them.
- You want ready agents for patient access, revenue cycle and IT help desk calls in one place.
- The agents should fit into a contact center on Genesys, Five9, Cisco, NICE or Amazon Connect.
Choose Luma Health if
- Referrals and orders still arrive by fax and need to reach the EHR without manual entry.
- One platform should run access, outreach, intake, eligibility and payments.
- Agents should remember each patient across calls, texts and chats.
| Feature | H Hyro |
L Luma Health |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
HyroIntegrations & Tool Calling In Epic, agents book, reschedule and cancel inside Cadence, run order based scheduling and complete referrals, pull a patient's active prescriptions live from Willow, and send refill and renewal requests to the prescriber's In Basket. Outbound campaigns run against Epic Cheers segments, and Hyro is listed on Epic's AI Agent Showroom. Hyro also connects to Oracle Health, athenahealth (including athenaCommunicator), eClinicalWorks, MEDITECH and NextGen, to Salesforce and ServiceNow, to Genesys, Five9, Cisco, NICE, Avaya, RingCentral, Amazon Connect and Twilio, and to Microsoft Teams, Kyruus Health, symplr and Gozio Health. Sourcehyro.ai/integrationsread 2026-10-21 |
||
|
Luma HealthIntegrations & Tool Calling Bidirectional integration covers Epic, Oracle Health, MEDITECH, eClinicalWorks and athenahealth, with NextGen, Nextech, Greenway Health and PCC as native partners, and the EHR stays the source of truth. Navigator reads the patient's record before it talks and writes back, and Fax Transform creates referrals, updates Epic Health Maintenance and links open orders to incoming results. SourceLuma Health, lumahealth.io and /solutions/access/referrals-ordersread 2026-10-21 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
HyroWorkflow Orchestration Each Agent OnCue owns one workflow made of several healthcare tasks. ACE, the engine behind every agent, holds context across a multi step request and hands a caller to staff with the conversation attached. Hyro names no workflow builder, branching the customer configures or handoff from one agent to another. Sourcehyro.ai/platform/agentic-communication-engineread 2026-10-21 |
||
|
Luma HealthWorkflow Orchestration Agents work together on one patient's care. A concierge agent triages a request and hands it to a scheduling agent, and care, prep, intake and outreach agents carry a procedure from referral to completion. Teams set when, where and how agents run in the Workflow Builder and Agent Library, or name an outcome and let the agents work out the steps. SourceLuma Health, lumahealth.io/platform/agentic-orchestrationread 2026-10-21 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
HyroTriggers & Channel Coverage Inbound agents answer patient calls and chats around the clock, and no staff member has to start them. Outbound campaigns run on timing and status, such as an upcoming appointment, a prescription about to run out, a bill coming due or an open referral, across voice and digital channels. Sourcehyro.ai/platform/outbound-agents-oncueread 2026-10-21 |
||
|
Luma HealthTriggers & Channel Coverage Navigator answers inbound calls, chats and texts and places outbound calls and texts for care gaps and no shows. Arriving faxes start Fax Transform, which runs the next steps on its own, from eligibility checks to scheduling and requests for missing information. A patient left on a long hold can switch to text and carry on. SourceLuma Health, lumahealth.io/solutions/outreach/navigator and /solutions/access/referrals-ordersread 2026-10-21 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
HyroKnowledge Grounding & RAG ACE answers through retrieval over a knowledge graph of the sources the customer approves, covering providers, specialties, locations, services, scheduling logic and an internal knowledge base, with a healthcare policy layer on top. Teams update that content in Knowledge Studio without a development cycle. Agents answer only from approved sources, never from open ended generation. Sourcehyro.ai/platform/agentic-communication-engineread 2026-10-21 |
||
|
Luma HealthKnowledge Grounding & RAG Agents work from the patient's record, past documents and the customer's workflows, and the customer's team chooses which information sources each agent can draw from. Fax Transform reads every fax to the organization's own specifications. Luma names no knowledge base or retrieval layer the agents answer from. SourceLuma Health, lumahealth.io/platform/our-ai and /solutions/access/referrals-ordersread 2026-10-21 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
HyroMemory & State Persistence ACE keeps context through every turn of a conversation and across a multi step request, and a handoff to staff carries the conversation with it. A memory system is named among ACE's parts, but Hyro does not say what it keeps about a patient or for how long. Sourcehyro.ai/platform/agentic-communication-engineread 2026-10-21 |
||
|
Luma HealthMemory & State Persistence Navigator remembers each patient across calls, texts and chats, including how they prefer to be reached, and brings up missed follow ups, flagged results and refills coming due at the next contact, drawing on past conversations, the EHR and the rest of the platform. Luma does not say how long that memory lasts, and it states its AI products do not store data long term. SourceLuma Health, lumahealth.io/solutions/outreach/navigator and /platform/how-it-works/security-trustread 2026-10-21 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
HyroHuman Oversight & Guardrails Anything beyond the protocols a team sets goes to a person, and human in the loop and transfer are named escalation paths. Teams set response overrides and clinical protocols, and refill and renewal requests go to the prescriber's inbox in the EHR rather than being decided by the agent. Hyro names no step of its own where a person approves an agent action before it commits. Sourcehyro.ai/platform/healthcare-ai-guardrailsread 2026-10-21 |
||
|
Luma HealthHuman Oversight & Guardrails Staff confirm extracted referral data with one click before the referral is created in the EHR, and confidence thresholds the customer sets by document type decide which faxes need that review. The team defines which workflows, EHR actions, hours and sources each agent may use, and an agent that reaches one of those limits stops and hands the work to a person. Agents give no clinical advice and do not change medications. SourceLuma Health, lumahealth.io/solutions/access/referrals-orders, /platform/how-it-works/ai-trust-governance and the Spark press releaseread 2026-10-21 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
HyroSecurity, Identity & Governance Hyro holds SOC 2 Type II and states HIPAA, CCPA and GDPR compliance and WCAG 2.1 AA accessibility. Personal data is redacted, and patient data is processed under BAAs with zero retention terms. Identity rules decide who can act for a patient, such as a guardian or caregiver. Hyro names no SSO, roles or permission model for the customer's own staff. Sourcehyro.ai/platform/healthcare-ai-guardrailsread 2026-10-21 |
||
|
Luma HealthSecurity, Identity & Governance Luma holds HITRUST CSF r2 and HITRUST ai2, ISO 27001:2022, a SOC 2 Type II attestation and TX-RAMP Level 2, builds its AI products to ISO 42001, and takes part in the EU, UK and Swiss Data Privacy Frameworks. All access is role based under least privilege and needs management or system owner approval, SSO is required wherever possible, and entitlements are reviewed every 60 days. Customer data is not used to train models. SourceLuma Health, lumahealth.io/platform/how-it-works/security-trustread 2026-10-21 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
HyroObservability & Auditability Guardrails record conversation logs, the sources cited in each answer and performance metrics to the Care Intelligence dashboard, and the actions agents take are logged too. Staff can drill from a trend down to a single conversation and the logic behind each response. Care Intelligence also reports trending topics and the missing terms that point to knowledge gaps. Sourcehyro.ai/platform/healthcare-ai-guardrailsread 2026-10-21 |
||
|
Luma HealthObservability & Auditability For every engagement the team can read the full message history and every action the agent took, and changes to agent behavior are tracked. Reporting shows the model and vendor used and the channel for each engagement, and Fax Transform's dashboard reports accuracy by type of information. SourceLuma Health, lumahealth.io/platform/how-it-works/ai-trust-governance and /platform/our-airead 2026-10-21 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
HyroDeployment & Data Residency Every data processing subcontractor is in the United States, including Azure, Snowflake, MongoDB, Twilio and Datadog, and support comes from Hyro's affiliate in Israel. Data processing stays in that single region. Hyro names no region choice, customer environment or on premises option. Sourcehyro.ai/hyro-subcontractorsread 2026-10-21 |
||
|
Luma HealthDeployment & Data Residency Infrastructure runs across multiple AWS availability zones with a 99.9% uptime target. Luma serves customers in the United States, Canada and the United Kingdom and builds its software to meet GDPR, but names no hosting region, region choice, customer environment or on premises option. SourceLuma Health, lumahealth.io/platform/international and /platform/how-it-works/security-trustread 2026-10-21 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
HyroPrebuilt Agents, Templates & Packs More than 20 Agents OnCue each own one job, among them Routing, Answers, Providers, Appointments, Registration, Scheduling, Prescriptions, Referrals, Billing, Coverage, Passwords and Tickets, and they deploy into the systems the customer already runs. Outbound OnCue adds ready campaigns for reminders, overdue care, open referrals and billing. Sourcehyro.ai/platform/inbound-agents-oncueread 2026-10-21 |
||
|
Luma HealthPrebuilt Agents, Templates & Packs Named agents each do their own job: Navigator and the Conversational Agent for calls and messages, and the Scheduling, Referral, Intake, Eligibility, Payment, Care and Post-procedure Agents, with Fax Transform for incoming documents. The Agent Library holds them alongside ready workflows for recalls, care gap closure, no show follow up and broadcast outreach. SourceLuma Health, lumahealth.io and /platform/agentic-orchestrationread 2026-10-21 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
HyroModel Flexibility & Routing ACE runs a small language model of Hyro's own, trained on patient access language, to read intent first, then draws on large language models for understanding and phrasing. Hyro picks the models, with Azure AI services and Anthropic's Claude web search among its subprocessors, and the customer does not choose them. Sourcehyro.ai/platform/agentic-communication-engineread 2026-10-21 |
||
|
Luma HealthModel Flexibility & Routing Luma picks models from OpenAI, Anthropic and ElevenLabs, matching each model to the task, and swaps in better ones as they arrive. It controls each model's permissions and handoffs, and the customer does not choose the models. SourceLuma Health, lumahealth.io/platform/our-airead 2026-10-21 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
HyroAPIs, SDKs & MCP Extensibility Hyro connects to telephony over SIP, vXML and PSTN and syncs both ways with EHR, CRM and contact center systems. Hyro names no API, SDK or MCP server for building on it. Sourcehyro.ai/integrationsread 2026-10-21 |
||
|
Luma HealthAPIs, SDKs & MCP Extensibility Headless AI workflows connect Claude, Microsoft Copilot or ChatGPT to the Luma platform through an MCP server. Luma publishes no endpoint, sign in method or tool list for that server, and names no API or SDK. SourceLuma Health, lumahealth.io/platform/our-airead 2026-10-21 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
HyroTesting, Debugging & Optimization Every interaction is scored and flagged for quality concerns, including adherence to the team's protocols, hallucinations, harm and patient sentiment, and responses are checked for clinical bias. Teams see where conversations went off track and can update the knowledge behind them in Knowledge Studio. Sourcehyro.ai/platform/healthcare-ai-guardrailsread 2026-10-21 |
||
|
Luma HealthTesting, Debugging & Optimization Each release is tested against more than 500 conversational test cases covering accuracy, expected behavior and edge cases, and an evaluation team signs off before it reaches customers. After release, every live engagement is reviewed automatically to raise accuracy and cut transfers, and the team reviews hundreds of live engagements by hand each month. SourceLuma Health, lumahealth.io/platform/how-it-works/ai-trust-governance and /platform/our-airead 2026-10-21 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
HyroBrowser & Computer Use Agents act through EHR, contact center and CRM integrations. Hyro names no browser, desktop or computer control. Sourcehyro.ai/platformread 2026-10-21 |
||
|
Luma HealthBrowser & Computer Use Agents work through bidirectional EHR integration, phone, text and chat, and outbound faxes. Luma names no browser, desktop or computer control. SourceLuma Health, lumahealth.io/platform/our-airead 2026-10-21 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | H Hyro |
L Luma Health |
|---|---|---|
|
Entry price Lowest public entry point |
Contact sales | Contact sales |
|
Pricing confidence How public the numbers are |
Contact only | Contact only |
|
Billing Primary billing axis |
— | — |
|
Variable cost Workload / overage exposure |
Medium variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
No free tier
|
|
Buying motion Self-serve vs sales call |
Sales call | Sales call |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Hyro
-
· Integrations
Hyro partnered with ServiceNow to integrate its healthcare-specific AI agents directly into the ServiceNow platform.
Source
Luma Health
-
· Agent capability
Luma Health launched its Summer 2026 release, introducing new Operational AI features that connect pre-visit preparation to in-clinic workflows.
Source
Neither publishes pricing. Both sell through a demo.
More comparisons with Hyro or Luma Health
Other matchups in healthcare agents
Not the pairing you were after? These compare a different set of healthcare agents on the same 14 capabilities.