Mapping the ACCESS Model APIs: What the FHIR Infrastructure Tells Us
Mapping the ACCESS Model APIs: What the FHIR Infrastructure Tells
Summary
CMS published an API architecture for the ACCESS Model, which includes four FHIR operations ($check-eligibility, $align, $report-data, $unalign) to track care episode lifecycles. The author argues that while the technical design is sound, the true challenge lies not in the APIs themselves but in establishing necessary partnership structures.
Details
CMS released the FHIR R4 Implementation Guide (v0.9.1) for the ACCESS Model, which governs beneficiary alignment, clinical data reporting, and care episode lifecycle starting July 5, 2026. The guide specifies four API operations, seven subscription event types, six code systems, and twelve FHIR profiles. Technically, all four operations follow a consistent pattern: POSTing a Parameters resource to the operation endpoint, receiving HTTP 202 Accepted for asynchronous processing, and polling until completion. Authentication uses OAuth 2.0 client credentials over TLS 1.3. The author praises the technical design—calling it clean and well-considered—but argues that the infrastructure alone is insufficient. The true opportunity of the ACCESS Model lies not in individual participants or direct marketing to beneficiaries, but in establishing complex partnership structures involving 'referring entities,' 'co-management partners,' and 'clinical networks.' This suggests that for a specialty practice to succeed, it must function as part of a broader value-based network, coordinating with multiple upstream partners and sharing the operational surface area, rather than operating independently.
Technology Note
FHIR（Fast Healthcare Interoperability Resources）は医療データ交換の国際標準。このエントリの関連技術: FHIR
Original content copyright by respective publishers