We built this inside a health plan, not next to one.

Operating a Medicare Advantage plan means holding clinical, financial, network and regulatory questions in the same head at the same time. Nobody can. So the work gets split across vendors, and the splits become permanent — four extracts, four definitions, four renewal cycles, and a question that crosses domains becomes a project.

Two things changed that. Encoding deep domain expertise into software stopped being a multi-year rule-engine build. And every one of these regulated workflows turned out to be published, specified and auditable — which means an implementation built on one taxonomy can be more documented and more reproducible than the vendor product it replaces, not less.

So we built it. In production, for Florida Medicare Advantage and Dual Eligible plans, with real users who notice immediately when a number is wrong.

We ship against a real operation. Every capability on this site was built because somebody needed it that week, and corrected because somebody used it and it was wrong.

We state the boundary first. What we don’t replace is on the site, above the fold of its own section.

We build a taxonomy, not single-rule engines. Regulations change and sometimes reverse. A general model of the organization survives that; an engine built for one mechanic gets written off. We’ve watched that happen to vendors who guessed.

We don’t overstate the gap. Gross and net reported separately, never a number whose denominator we can’t name, and what is working shown next to what needs attention.

Within about two years of onboarding, a risk-bearing organization runs its network sufficiency and provider network analysis, risk adjustment and chart review, HEDIS measures, encounter integrity, payment integrity and fraud, waste and abuse, care-management analytics, member view and settlement work on one platform — keeping two or three vendor relationships, all of them attestation rather than computation.

The money that was buying ten frameworks goes to member benefit or to the platform. And the institutional knowledge lives in a taxonomy, instead of in a departing analyst’s head or a vendor’s black box.