Productized Consulting for CMS-0057-F Readiness

Tessara is opening a productized consulting practice. Fixed scope, fixed price, fixed timeline — built around the same drift-detection engine that powers the product.

Read full article →

The CMS-0057-F Compliance Countdown: What Payers Need Done by January 1, 2027

A month-by-month payer roadmap to the CMS-0057-F January 1, 2027 deadline. Concrete activities, real lead times, no enforcement theater.

Read full article →

A Payer's Self-Audit Checklist for FHIR API Conformance

25 concrete checks a payer engineering team can run this week to assess CMS-0057-F FHIR API conformance. Real items, no fluff, do it yourself.

Read full article →

Six Ways Your FHIR API Is Drifting From Spec Right Now

Real examples of the six canonical FHIR drift categories — Mandatory Element Removal, Type/Cardinality Change, Structural Extension, Auth Deviation, Endpoint Behavioral Change, Spec Version Mismatch.

Read full article →

What Auditors Actually Want from Your Patient Access API (And What They Don't)

Demystifying the CMS audit posture for FHIR Patient Access APIs under CMS-0057-F and CMS-9115-F. Before, during, and after — what auditors ask, what they accept, what they reject.

Read full article →

Why Application Logs Aren't Compliance Evidence

Auditors don't accept application logs as compliance evidence. Here's what they look for instead, and why signed Merkle-chained verdicts are a different category of artifact.

Read full article →

CMS-0057-F Enforcement: Preparing for the 2027 Deadline

An analysis of CMS enforcement patterns and the technical requirements healthcare payers must meet by the January 2027 compliance deadline.

Read full article →

How Tessara's Evidence Chain Works

Tessara produces cryptographic proof that a FHIR API was conformant at a specific moment — without ever touching a byte of patient data. Here is how the chain is constructed.

Read full article →

The 6 Categories of Specification Drift: How Tessara Classifies Non-Conformance

Tessara's 6-category drift taxonomy — the structural differences between a spec-anchored baseline and a live FHIR API, ranked by regulatory severity.

Read full article →