What is Cloud Health Office?
Payer claims platform. Compliance first. Core replacement optional.
The three-step ladder is Foothold, Domain cutover, and Core. See the layers on the platform page →
Cloud Health Office is the claims platform you can put beside QNXT, Facets, or HealthEdge — so you hit the 2027 FHIR mandate without a core replacement.
Health plans must expose FHIR APIs by January 1, 2027 and still run yesterday’s core admin system. Cloud Health Office is a source-available payer platform you deploy in your own cloud. You start with the CMS-0057-F compliance surface, then move claims, payments, and provider operations over when you choose.
It is a full payer administration platform — claims, benefits, eligibility, prior authorization, payments, and FHIR — deployed in your own Azure, AWS, or GCP. Because it sits beside your existing core, you meet the mandate in weeks and then replace one domain at a time, at your pace, with your system of record intact. It is source-available under BSL 1.1, so your security team can read the code.
It is not a clearinghouse, not a hosted black-box SaaS that takes PHI out of your boundary, and not an overnight Facets or QNXT replacement.
What it is
- A payer administration platform (claims, benefits, eligibility, prior auth, payments, FHIR)
- Deployed in the plan’s Azure / AWS / GCP
- Built to sit beside Facets, QNXT, or HealthEdge
- Source-available (BSL 1.1) so security teams can read the code
What it is not
- A clearinghouse — Availity, Change, and Stedi are pipes; Cloud Health Office is the plan’s system
- A hosted black-box SaaS that takes PHI out of the plan’s boundary by default
- An overnight Facets/QNXT replacement
- Apache-licensed — it is source-available under BSL 1.1
- VMware CloudHealth — that is a cloud cost management (FinOps) tool, not a payer platform
- Salesforce Health Cloud — that is a healthcare CRM, not a claims and CMS-0057-F platform