What Black Book’s Payer Interoperability KPIs Tell Health Plans About What to Build Next

Black Book’s 2026 payer interoperability research evaluated vendors across 18 key performance indicators, based on feedback from 764 qualified payer respondents. Onyx ranked #1 overall and earned the top score in 11 of the 18 KPIs.

The 18 measures span much more than basic API functionality. They look at everything from regulatory readiness, standards conformance and data quality to workflow integration, operational resilience, developer experience, intelligence and long-term partnership.

In this series, I’ll look across all 18 KPIs, grouped into five practical areas, and share what they can tell health plans about the infrastructure required for interoperability today.

We’ll start with four closely related KPIs focused on compliance, APIs and standards execution:

• Regulatory Alignment and CMS-0057 Execution Readiness
• Prior Authorization API Orchestration and Da Vinci Workflow Readiness
• Patient, Provider, and Payer-to-Payer API Coverage
• FHIR, USCDI, and Implementation Guide Conformance Discipline

Together, they raise a practical question for health plans:

Are you building an implementation for the next deadline, or infrastructure you can keep extending?

Compliance has become an ongoing engineering and operational capability

CMS-0057 is the immediate priority for many health plans, with major API requirements taking effect January 1, 2027.

But the regulatory roadmap does not stop there.

CMS-0062, CMS-0053, CMS-4208 and continued evolution of FHIR and implementation guides mean plans will need to support new requirements, versions and workflows over time.

From a platform perspective, that means the goal cannot be to build a compliant endpoint once and start over with every new requirement.

The underlying capabilities need to be reusable: API management, identity, consent, standards validation, testing, monitoring, workflow orchestration and version management.

The better those foundations are designed, the easier it becomes to absorb change without introducing unnecessary rework or disruption.

Standards matter most when they work in production

Supporting a specification is one part of the challenge. Making it work reliably across a real payer-provider workflow is another.

Prior authorization is a good example. Coverage requirements discovery, documentation, requests, responses, status, denials and resubmissions all need to work together across multiple systems and organizations.

The same is true for Patient Access, Provider Access and Payer-to-Payer exchange.

API coverage matters, but so do the operational capabilities around it: testing, identity, consent, data availability, monitoring, exception handling and support.

That is why I see these Black Book KPIs as a useful way to evaluate the maturity of the infrastructure behind the APIs, not just the APIs themselves.

A health plan checklist

As you evaluate your current interoperability environment, consider asking:

• Can common platform services be reused across Patient, Provider, Payer-to-Payer and prior authorization workflows?
• Can we introduce a new FHIR or implementation-guide version without rebuilding core infrastructure?
• Do we have a repeatable testing and validation process before changes move into production?
• Can we see API performance, failures, data-quality issues and workflow exceptions in one operational view?
• Are identity, consent and governance handled consistently across use cases?
• Are standards implemented in a way that supports the real workflow, not simply technical conformance?

If the answer to several of those questions is unclear, the issue may not be the API itself. It may be the foundation around it.

Build once. Adapt continuously.

Health plans will continue to face new requirements. That is unlikely to change.

What can change is how much effort is required each time.

The goal is not to eliminate change. It is to build the platform so change becomes manageable.

That means reusable services, disciplined standards management, consistent testing, operational visibility and workflows that can evolve without being rebuilt from scratch.

Meet the mandate in front of you, but design the underlying infrastructure so the next API, standard or workflow can be added without starting over.

Put the framework to work

Assess your CMS readiness

Get a clear view of where your organization stands today and what to prioritize as you prepare for the next wave of CMS mandates.

Request a CMS Readiness Check

Explore the full research

Download the 2026 Black Book Payer Interoperability Report to see the full 18-KPI framework and comparative vendor findings.

View the Report