25 years in payer systems, turned into software you can inspect.
Mark Phillips — Founder & Solution Architect, Cloud Health Office
Most payer software is sold by people who have never had to make a legacy core-admin system pass an audit at 2 a.m. I have. I spent nearly two decades across QCSI, TriZetto, and Cognizant — the lineage that created and evolved QNXT — followed by five years at Invidasys, and I architected core systems on the payer side at Molina Healthcare. Cloud Health Office is that quarter-century of claims, authorizations, interoperability, and cloud experience turned into a platform you can inspect — not a sales deck.
A career spanning the companies that define payer technology
A rare combination in one practitioner
The value of a payer platform is only as real as the person who understands both the regulation and the plumbing. These are the areas I work in hands-on.
QNXT & legacy core-admin modernization
Nearly two decades across QCSI, TriZetto, and Cognizant — the lineage that created and evolved QNXT — including modernization leadership at Cognizant. I know these platforms and their Facets-class peers from the inside: how to modernize them without ripping them out, and exactly which decisions are safe to make and which aren't.
Azure & cloud-native delivery
Significant experience bringing payer workloads — including QNXT — into Azure subscriptions the plan actually controls. The combination of core-admin depth and cloud architecture is hard to find in one person.
Claims, authorizations & payment integrity
The full claims lifecycle: adjudication, prior authorization, edits, and the payment-integrity decisions that determine whether a plan pays correctly — the substance behind every screen on this platform.
Interoperability & CMS-0057-F
A working command of interoperability and the CMS-0057-F rule — not as a slide, but as deadlines, APIs, and data flows a plan has to stand behind. The compliance work on this site reflects it.
Vendor accountability
I've served as the technical check on large implementation vendors — challenging estimates that aren't sound and keeping delivery honest. That posture is baked into how this platform is built and documented: evidence you can inspect.
Stakeholders & knowledge transfer
Translating fluently between business owners, IT staff, and engineering teams — and training internal staff so capability stays with the organization, not locked in a contractor's head.
Why I built Cloud Health Office
I've spent my whole career in payer core administration — building QNXT across QCSI, TriZetto, and Cognizant, and architecting systems inside a health plan at Molina Healthcare. Everywhere I went, the pattern was the same: a capable platform that predates the regulations now being written for it, an urgent compliance deadline, and a gap in the middle that gets filled with consulting hours instead of software. I kept solving the same problems — eligibility, claims, prior authorization, interoperability — one engagement at a time.
Cloud Health Office is those solutions, made durable. It's the compliance and modernization layer for legacy payer systems — meet CMS-0057-F without replacing QNXT, Facets, or HealthEdge — and it's built the way I run an implementation: evidence first, no hand-waving, every claim inspectable. That's why the site leads with a million-claim benchmark you can audit instead of a marketing number you have to trust.
“The people who understand payer systems deeply are rarely the people building the software for them. Cloud Health Office closes that gap — the platform is built by the practitioner, with the evidence in the open.”
Talk to the person who built it
Whether you're planning a QNXT-on-Azure move, staring down a CMS-0057-F deadline, or just want a straight technical read on your options — you'll be talking to someone who has actually done the work.
Contact Sales → Connect on LinkedIn