Agentic Index
CombineHealth vs XpertDox (2026)
Both vendors last verified
CombineHealth and XpertDox both automate revenue cycle work through sales, with no public price. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
CombineHealth sells an AI workforce of named employees for coding (Amy), billing (Mark), A/R and denials (Adam), appeals (Rachel) and analytics (Taylor), with review thresholds the customer configures and a line by line rationale for each decision. XpertDox sells XpertCoding, an autonomous coding engine for ambulatory and outpatient groups that codes encounters and submits claims, about 94 percent without human intervention and most within 24 hours, connecting to EHRs by API, FHIR, HL7 and screen automation. CombineHealth lets customers review, approve or override each exception and backs that with strict role based access and a SOC 2 Type 2 report, while XpertDox drives EHR screens where no API exists. Choose CombineHealth to cover the whole revenue cycle with review you configure. Choose XpertDox for coding throughput in an ambulatory group.
On the Agentic Index healthcare agent ranking, CombineHealth clears the bar and XpertDox does not. CombineHealth documents all five chart loop capabilities in full; XpertDox documents two of the five 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. CombineHealth and XpertDox 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
Choose CombineHealth if
- You want coding, billing, denials, appeals and analytics covered by named AI employees.
- Your team should set the review thresholds that decide what a human checks.
- Every decision should carry a line by line rationale.
Choose XpertDox if
- You are an ambulatory or outpatient group and coding throughput is the priority.
- Your EHR has no usable API, so the engine must work through its screens.
- You buy through a billing company partner.
| Feature | C CombineHealth |
X XpertDox |
|---|---|---|
| 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. |
||
|
CombineHealthIntegrations & Tool Calling The AI employees check eligibility, automate 95%+ of claim submission work, check every claim status and follow up with payers, with EHR integration through APIs, HL7 and custom interfaces. The EHRs appear as logos and are not named in text. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxIntegrations & Tool Calling XpertCoding connects to NextGen, eClinicalWorks, athenahealth, Experity, ModMed, Epic and custom EHRs by API, SMART on FHIR, HL7 ADT messaging and RPA. It is listed on the athenahealth Marketplace and submits claims with any EHR, and connecting a major EHR takes 1 to 4 weeks. Sourcexpertdox.com/ehr-connectionsread 2026-09-29 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
CombineHealthWorkflow Orchestration Named AI employees (coder, biller, A/R specialist, appeal specialist, analyst) work within workflow logic, payer rules and confidence thresholds the customer configures, and payer outcomes and appeal learnings are fed back into eligibility, coding and claims. Sourcecombinehealth.airead 2026-09-29 |
||
|
XpertDoxWorkflow Orchestration Each encounter runs from data extraction through code assignment to claim submission. One condition splits the flow. About 94 percent of claims complete without human intervention, and the rest go to manual review, which the BI platform monitors. XpertDox says the result lets a practice shrink its coding and billing team by as much as 90%. SourceXpertDox, xpertdox.com/xpertcoding and xpertdox.comread 2026-10-06 |
||
|
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. |
||
|
CombineHealthTriggers & Channel Coverage Adam instantly checks every claim status, categorizes denials as they appear and works a prioritized A/R follow-up queue, so work reaches the agents without staff starting each item. Sourcecombinehealth.ai/adam-ai-denial-management-softwareread 2026-09-29 |
||
|
XpertDoxTriggers & Channel Coverage Encounters arrive through HL7 ADT messaging, FHIR, API or RPA feeds and are coded and submitted as their data arrives, without anyone initiating each one, most within 24 hours. Sourcexpertdox.com/ehr-connectionsread 2026-09-29 |
||
| 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. |
||
|
CombineHealthKnowledge Grounding & RAG Payer policy logic is kept continuously updated with the latest payer rules, policies and coding edits, a policy review agent maintains it, appeal packets are drafted with documentation and payer policy context, and the organization's own coding grid and guidelines are loaded. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxKnowledge Grounding & RAG The engine reads each encounter's documentation with natural language processing and analytics and applies payor guidelines. XpertDox names no maintained knowledge structure over the customer's records or payer rules and does not say whether the engine adapts to evolving coding standards. SourceXpertDox, xpertdox.com/xpertcoding and xpertdox.comread 2026-10-06 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
CombineHealthMemory & State Persistence Learning from payer behavior, claim outcomes and coder feedback is how the product improves, not a memory store, and customizable coding grids are settings. There is no memory layer with a scope or lifetime. Sourcecombinehealth.ai/ai-medical-coding-softwareread 2026-09-29 |
||
|
XpertDoxMemory & State Persistence Each encounter is coded from its own documentation, and XpertDox names no memory the engine keeps. SourceXpertDox, xpertdox.com/xpertcodingread 2026-10-06 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
CombineHealthHuman Oversight & Guardrails Customers configure confidence thresholds for human review and can review, approve, override and track exceptions. Amy flags uncertain or complex charts for coders, who make the final determination before the code commits. Sourcecombinehealth.airead 2026-09-29 |
||
|
XpertDoxHuman Oversight & Guardrails People review only the exceptions. About 94 percent of claims are coded and submitted without human intervention and the remainder go to manual review, with no approval step before automated claims commit. Sourcexpertdox.com/blog/computer-assisted-coding-vs-autonomous-medical-coding-airead 2026-09-29 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
CombineHealthSecurity, Identity & Governance CombineHealth reports SOC 2 compliance with a SOC 2 Type 2 report available on request, and has strict role-based access controls, encryption in transit and at rest, audit trails of data access and third party penetration testing. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxSecurity, Identity & Governance XpertDox holds SOC 2 Type 2, ISO/IEC 27001 and ISO/IEC 22301 and states HIPAA compliance. Its enterprise security features control who can access, modify or delete data, access to critical systems is reviewed periodically, and the network and servers get quarterly penetration tests. XpertDox names no SSO, roles or permissions that customers operate. SourceXpertDox, xpertdox.com/securityandcomplianceread 2026-10-06 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
CombineHealthObservability & Auditability Every coding decision carries line-by-line rationale and evidence, the platform shows the rationale behind AI actions, recommendations and exceptions, Adam records payer calls with summaries and shows which denial codes triggered which actions, and audit trails log data access and modifications. Sourcecombinehealth.ai/ai-medical-coding-softwareread 2026-09-29 |
||
|
XpertDoxObservability & Auditability The BI platform shows every claim XpertCoding coded on one screen, and its audit trail tracks all modifications the engine makes, with manual review monitoring and daily reports. Risk adjustment (HCC) and quality measures dashboards sit alongside, so each claim's changes can be traced. SourceXpertDox, xpertdox.com/xpertcodingread 2026-10-06 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
CombineHealthDeployment & Data Residency There is no hosting region, region choice, customer environment or on premises option. CombineHealth's security answers cover its own data centers and network controls. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxDeployment & Data Residency No hosting provider or region is published, and XpertDox names no residency choice or customer environment option. SourceXpertDox, xpertdox.com/securityandcomplianceread 2026-10-06 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
CombineHealthPrebuilt Agents, Templates & Packs Named prebuilt AI employees each do a separate job and have their own pages. Amy is the medical coder, Mark the biller, Adam covers A/R and denials, Rachel handles appeals and Taylor is the RCM analyst, while Penny (policy review) and Jessica (scribe) have pages too. Sourcecombinehealth.airead 2026-09-29 |
||
|
XpertDoxPrebuilt Agents, Templates & Packs One coding engine comes with a companion BI platform. The urgent care, primary care and pediatric offerings are specialty segments of that engine, not separate packaged agents. Customers include Stanford University, Bon Secours Mercy Health, FastMed Urgent Care, PM Pediatrics, NAO Medical and Lone Star Circle of Care. SourceXpertDox, xpertdox.com and /xpertcodingread 2026-10-06 |
||
| 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. |
||
|
CombineHealthModel Flexibility & Routing The technologies are named as classes (NLP, machine learning, deep learning, agentic AI and RPA). No model provider is named, and the customer has no model choice. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxModel Flexibility & Routing XpertCoding runs on what XpertDox calls hybrid AI, combining ensemble models, neural networks and symbolic reasoning with payor guidelines, alongside natural language processing and advanced data analytics. XpertDox names no model provider and offers no customer choice of model. SourceXpertDox, xpertdox.com and /xpertcodingread 2026-10-06 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
CombineHealthAPIs, SDKs & MCP Extensibility There is no API, SDK or MCP server for the CombineHealth platform. The APIs named in the FAQs are how it connects to the customer's EHR, the opposite direction. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxAPIs, SDKs & MCP Extensibility Developers get no published API, SDK or documentation for XpertCoding. Its API integrations are XpertDox's connections out to EHRs. Sourcexpertdox.com/sitemap.xmlread 2026-09-29 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
CombineHealthTesting, Debugging & Optimization Coders review flagged cases and their feedback flows back to the AI for continuous learning, a loop after deployment whose mechanism and measured results are not stated. The head to head study against expert coders is CombineHealth's own benchmark. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxTesting, Debugging & Optimization Outcome figures include over 99 percent coding accuracy and over 94 percent of claims within 24 hours, and NAO Medical reports 15% more charge capture and 60% more quality code capture. CDI feedback goes to providers about their documentation, not to the engine. XpertDox names no evaluation harness, test cases or learning loop. SourceXpertDox, xpertdox.com and /xpertcodingread 2026-10-06 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
CombineHealthBrowser & Computer Use RPA is named among the technologies automating repetitive revenue cycle tasks and the agents act in payer workflows, but there are no bots driving an application interface. Adam's IVR navigation on payer calls works a telephone menu, not a screen. Sourcecombinehealth.ai/faqsread 2026-09-29 |
||
|
XpertDoxBrowser & Computer Use XpertDox's RPA bots work the EHR on the front end, with no backend integration, to retrieve the fields XpertCoding needs and post processed codes back, because most EHRs lack an API for posting claim data. Sourcexpertdox.com/blog/rpa-improves-ehr-interoperabilityread 2026-09-29 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | C CombineHealth |
X XpertDox |
|---|---|---|
|
Entry price Lowest public entry point |
Contact sales. No pricing is published. | 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 |
XpertDox's automation rate is its own figure.
More comparisons with CombineHealth or XpertDox
Other matchups in healthcare agents
Not the pairing you were after? These compare a different set of healthcare agents on the same 14 capabilities.