Product Line Context
The Portfolio Is the Moat
The competitive analysis on this page reads Cloud Health Office (CHO) against legacy EDI and core admin vendors. The differentiation thesis is structural: incumbents sell one thing; CHO ships four complementary product lines — Public Tools, Transactional Services, Managed Data Services, and Platform Engagement — off the same platform substrate.
Free fee-schedule lookups feed paid APIs; paid APIs validate the calculation engines that anchor per member per month (PMPM) payer relationships; subscription data services run the same ingestion pipelines that Platform Engagement deploys end-to-end. The competitive moat isn't any single capability. It's the portfolio.
See full pricing → · Canonical positioning →
Engineering Proof
Million Claim Challenge · Local Kubernetes validation
From Fast Runs to Inspectable Evidence
Cloud Health Office moved from repeatable throughput runs into broader edge-case scoring and operator-visible evidence:
expected pends are observed from persisted claim status, unsupported scenarios are separated from mismatches, and the Mass Adjudication console can inspect run summaries and claim-level evidence.
The latest published scale result is one million mixed claims through Azure Service Bus at 155.89 claims per second, plus a separate 100,000-claim raw X12 837P run at 199.42 end-to-end claims per second. Both are local Kubernetes validations on Docker Desktop, not production cloud benchmarks.
1,000,000
mixed claims eventually terminal through Service Bus
155.89/sec
asynchronous submission throughput at p96
0 / 0
active and dead-lettered Service Bus messages after drain
$0.00
payment variance across 19,982 compared claims
The asynchronous validator observed 999,878 claims within its 180-second windows and timed out on 122 observations clustered in two brief episodes. Post-run reconciliation found exactly one million terminal claims in MongoDB, with no dead letters, pod restarts, or error logs. The separate raw 837P run accepted and adjudicated all 100,000 transactions.
Local Docker Desktop Kubernetes benchmark, not a production cloud benchmark.
Read the methodology ·
Read Part 16 ·
Engineering series ·
Evidence archive →
Stedi Interoperability · Vendor-neutral gateway
The Clearinghouse Is Not the Payer Platform
Cloud Health Office is the claims operating system a health plan actually runs. Stedi is one of the networks it can speak.
Sequential PRs activated eligibility, 837, 277CA, 275, 276/277, 835, and a tenant-safe claim intelligence API — without letting a 277CA acceptance pretend to be payment, and without baking Stedi into the claim aggregate.
6
HIPAA transaction types on one gateway
837 → 835
submit, acknowledge, status, attach, remit
#1119
claim intelligence read model for CDO and portal
0
vendor names allowed in canonical models
Shipped code, contract-tested against Stedi's documented JSON APIs. Not a live ERA enrollment certificate.
Read the field note ·
Series ·
Gateway architecture →
Key Insights
1. Time to Value
Cloud Health Office is designed to enter through a focused compliance surface first, then expand by domain.
That lowers migration risk compared with a single big-bang replacement project.
2. Total Cost of Ownership
Platform Engagement pricing is PMPM and pilot-scoped, while public tools, transactional APIs,
and managed data services create lower-friction entry points before a payer-scale deployment.
3. Security Posture
Private endpoints everywhere, HSM-backed Key Vault, DCR-based PHI redaction, immutable audit logs.
Traditional vendors often expose public endpoints and lack modern security controls.
4. Vendor Lock-In Elimination
BSL 1.1 source-available with complete codebase transparency. No black-box vendor
dependency, community-driven development. Traditional vendors trap customers
in proprietary ecosystems.
5. Multi-Payer Scale
Multi-tenant by design with per-tenant query filtering. Traditional vendors charge
per payer or per connection, limiting growth and increasing costs.
