Source-available · FHIR-native · Your cloud or ours
Sovereign, interoperable health plan administration.
Your data, under your control, connected to every partner you choose. Cloud Health Office runs alongside QNXT, Facets or HealthEdge, in your own cloud or operated for you, with no core replacement required.
- CMS-0057-F FHIR APIs
- Prior authorization
- Claims & repricing
- Appeals & grievances
- Enrollment & billing
- Provider data
- Source-availableInspect every line under BSL 1.1
- Million Claim Challenge1M synthetic claims, published artifacts
- Limitations publishedImplemented vs. planned, stated plainly
- HIPAA roles definedBAA executed where required
Why sovereignty
Plans pay to modernize. Too often, the vendor keeps what gets built.
Integrations, interoperability and data pipelines built inside a BPaaS or SI platform rarely leave with you, so each project can deepen the dependency. Cloud Health Office is designed to turn modernization spend into assets your plan keeps.
Data sovereignty
Member, claims and provider data stays in a tenant dedicated to your plan: the foundation for an AI strategy your plan controls.
AI-ready architecture →Integration sovereignty
The interfaces you pay to build run in your environment, so changing a vendor need not mean rebuilding every connection.
Technical architecture →Modernize at your pace
Start beside your existing core with a bounded workload. Expand into core administration only when the evidence supports it.
Read why sovereignty matters →Deployment choice
Your cloud or ours. Your data either way.
Some plans have their own cloud and engineering teams. Many don't. Sovereignty means the platform and the data are dedicated to your plan, wherever it runs.
In your cloud
For plans with their own Azure, AWS or GCP and an engineering team. You own the infrastructure and operate the platform, with our support.
Payer-controlled deployment →In your cloud, operated by us
For plans with cloud infrastructure but no team to run it. The platform stays in your environment; Aurelianware operates it under an agreed scope.
Discuss managed operation →Hosted by Cloud Health Office
For plans without cloud infrastructure or engineering teams: a tenant dedicated to your plan, operated by Aurelianware. Not offered today. Tell us if it would fit your plan.
Register interest →Every option runs the same source-available software, so the choice you make today need not be permanent. Compare operating models.
Interoperability
Interoperability without giving up control.
Connect once, in an environment you own. Every new partner plugs into the same plan-owned front door.
Plan-owned
Your Cloud Health OfficeOne FHIR R4 front door, X12 ↔ FHIR translation and an audit trail, in a tenant dedicated to your plan.
Adapters for specific core systems and clearinghouses are scoped per implementation, because versions and configuration differ by plan. Each one's status is documented in the claims guide and the capability ledger.
CMS-0057-F
Meet CMS-0057-F on infrastructure you keep.
CMS-0057-F is the federal rule that requires Medicare Advantage, Medicaid, CHIP, and some exchange plans to offer FHIR APIs for patient access, provider access, payer-to-payer exchange, and prior authorization by January 1, 2027.
Cloud Health Office implements those FHIR APIs in your tenant, alongside the vendors you already use.
30-minute readiness review
Walk through your core system, current vendors and API gaps with an architect who has led QNXT implementations at health plans across the country.
Book a readiness reviewA practical progression
Transformation doesn't have to start with replacing your core.
Foothold
Start with a bounded workload, such as CMS-0057-F APIs or appeals, beside your existing core.
Domain Cutover
Move one domain at a time after parallel operation, reconciliation and agreed acceptance criteria.
Core Modernization
Expand into enrollment, billing, claims and provider administration with rollback planning at every step.
For payer architects and engineers
Evaluate it yourself. Then make the case.
Run the quickstart, browse the FHIR API specifications, and configure benefits, fee schedules and prior authorization with step-by-step guides. When you're convinced, take the business case kit to your leadership.
# Get the public source git clone https://github.com/aurelianware/cloudhealthoffice # Browse the Patient Access API specification https://cloudhealthoffice.com/api-explorer
For forward-thinking plans
Help Define the Next Generation of Health Plan Administration.
The Founding Transformation Partnership is a structured evaluation of one bounded modernization workload: its evidence, its acceptance criteria and the operating model needed to support it. It is an invitation to scope that work together, not a commitment of terms.
What is dependency costing your plan?
Model infrastructure, support, staffing, integration, transition and exit costs with your own assumptions.
Model your administration economics →
Who's behind it
Built by someone who has spent 25 years inside payer core systems.
Mark Phillips is the founder and chief architect of Cloud Health Office. He co-invented the MyQNXT patent, served as QNXT Solution Owner at Cognizant, and led QNXT implementations at plans including L.A. Care, Denver Health and Molina.
Software and expertise
Software, deployment flexibility, and payer expertise.
Professional Services helps payer teams assess, deploy and integrate the platform, with independent architecture advice when another path fits better.
Next step
Plan the work with your team.
Tell us who you are and we'll route you to the right conversation: a readiness review, an integration discussion, a partner call or investor materials. Please don't include member or patient information.