Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document payer and claims data exchange while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
CMS-9115-F
CMS-9115-F requires specified payers to maintain FHIR-based Patient Access APIs for claims, encounter, cost, and maintained clinical data, and establishes other interoperability and provider-notification provisions. The rule created a durable payer API market while leaving data scope, patient authorization, app privacy, testing, operations, and implementation-guide choices as material implementation decisions.
CMS-0057-F
CMS-0057-F expands Patient Access API content and requires Provider Access, Payer-to-Payer, and Prior Authorization APIs for impacted payers, with associated privacy, opt-in or opt-out, metrics, and operational provisions. The rule makes versioned FHIR implementation, bulk data, member permission, endpoint discovery, data lineage, and production operations central payer interoperability requirements.
PDex 2.1.0
PDex profiles FHIR-based exchange of clinical, claims, encounter, and prior-authorization information among payers, patients, and providers and introduces bulk APIs for provider and payer-to-payer access. PDex is central to current payer data-exchange architecture, but buyers must track its US Core dependencies, API role, bulk behavior, member permission, and relationship to separate CARIN and Da Vinci guides.
CARIN Blue Button 2.2.0
CARIN Blue Button defines FHIR profiles for consumer-directed exchange of claims and encounter information using the Common Payer Consumer Data Set. The 2026 release creates a current version-control question for payer and app implementations; support must be stated by version rather than as a generic Blue Button claim.
Operating domains
Network coverage, routing, and discovery
Risk that a buyer mistakes network scale, participant counts, connector catalogs, or designation for a usable path to the needed organization, endpoint, data, exchange purpose, and response behavior.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should payer and claims data exchange produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
CMS refreshes interoperability API frequently asked questions — Readiness records should be separated by API, implementation guide, source system, responsible party, test status, production status, and exception process.
HL7 publishes CARIN Blue Button 2.2.0 — Payer API comparisons should identify the exact guide version and distinguish technical conformance from identity, authorization, source-data quality, and production operations.