FHIR Service Migration
Azure API for FHIR retirement needs cutover proof
Microsoft says Azure API for FHIR retires September 30, 2026. The deadline calls for tested migration and rollback evidence—not assumed successor equivalence.
Coverage desk
FHIR & APIs
Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.
FHIR Infrastructure
Firely Server provides FHIR infrastructure—but a running endpoint is not conformance
Firely presents server, API, validation, and conformance tooling for FHIR implementations. An endpoint can accept and return resources while still missing required profiles, terminology, search behavior, authorization, provenance, or production workflow semantics.
Certification & APIs
HTI-4 puts electronic prior authorization in certified health IT—not clinical decision authority
ASTP/ONC's HTI-4 final rule adds and updates health IT certification criteria for electronic prior authorization alongside electronic prescribing, real-time prescription benefit, and related APIs. Certification evidence addresses defined technology capabilities; it does not make the software the clinical or coverage decision-maker.
FHIR infrastructure
FHIR R5 is a release—not a production migration verdict
The current published specification gives architects a version to assess, but adoption still depends on implementation-guide dependencies, partner support, artifact maturity, and conformance evidence.
FHIR infrastructure
PDex 2.1 makes payer data exchange a provenance test
HL7's current PDex guide maps payer clinical, claims, encounter, and prior-authorization data into FHIR exchange. Trust depends on preserving source mappings, versions, provenance, and reconciliation.
FHIR infrastructure
FHIR Bulk Data 3.0 turns export into an asynchronous job
HL7's current published guide separates export kickoff, status polling, completion manifest, files, and errors. A working endpoint is only the start; buyers need the whole job and its authorization boundary.
FHIR infrastructure
SMART App Launch 2.2 makes authorization part of the API
HL7 lists SMART App Launch 2.2 as the current published authorization guide. A FHIR endpoint still needs scoped access, token controls, and operating evidence.