Healthcare · Platforms & Architecture
Healthcare: platforms and architecture
What to know now
Each number links to the point's source. Points checked unless the point shows another date.
- CMS-0057-F, released January 17, 2024, gives impacted payers until primarily January 1, 2027 to meet its API requirements. CMS's page (last modified October 8, 2026) notes HIPAA enforcement discretion, announced February 28, 2024, for covered entities that use a FHIR-based Prior Authorization API without the X12 278 standard.1
- CMS proposed on April 14, 2026 to require electronic prior authorization for drugs, to require certain HL7 FHIR implementation guides that are now only recommended, to have payers report their API endpoints and usage, and to adopt FHIR as a HIPAA standard for some prior authorization transactions. Comments closed June 15, 2026.2
- ONC describes TEFCA as a nationwide network-of-networks. The first Qualified Health Information Networks were designated in December 2023. Its exchange purposes include treatment, payment, health care operations, public health, government benefits determination and individual access services.3
- The FY 2027 IPPS final rule, published August 4, 2026, delays removal of the two C-CDA referral loop measures to the CY 2029 reporting period. After that, hospitals meet the Promoting Interoperability exchange objective through the HIE Bi-Directional Exchange or Enabling Exchange Under TEFCA measure, plus the Electronic Prior Authorization measure or an exclusion from it. The same rule finalized ONC's proposal, first made in the April 2026 interoperability proposed rule, to adopt updated versions of the health IT standards in 45 CFR 170.215.4
- ONC's October 28, 2026 final rule keeps the HTI-4 certification criteria: three electronic prior authorization API criteria, a real-time prescription benefit criterion, a revised e-prescribing criterion and two modular API criteria. ONC says it will focus certification on FHIR-based APIs that improve automation, go beyond read-only access and widen the data available.5
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Sources
- Centers for Medicare & Medicaid Services. CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F). Checked .
- Centers for Medicare & Medicaid Services. Interoperability Standards and Prior Authorization for Drugs, 91 FR 19890 (proposed rule). Checked .
- Office of the National Coordinator for Health Information Technology. Trusted Exchange Framework and Common Agreement (TEFCA). Checked .
- Centers for Medicare & Medicaid Services. Medicare Program; Hospital Inpatient Prospective Payment Systems, FY 2027, 91 FR 49570 (final rule). Checked .
- Office of the National Coordinator for Health Information Technology. Health Data, Technology, and Interoperability: ONC Deregulatory Actions To Unleash Prosperity, 91 FR 67916 (final rule). Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the page where needed.
Looking Back
Week of May 11, 2026
Payer prior authorization APIs will only help the providers ready to call them
By January 2027, federal rules require health insurers to offer electronic doorways for prior authorization. Only health systems that have settled three things first will benefit: which system knocks on the door, whether the chart can answer, and who owns the request.
Week of October 13, 2025
Why Windows 10’s end of support split every hospital fleet in three
Windows 10 support ended and hospital computers split into three groups: those IT controls, those medical device makers control and those nobody clearly controls. Reporting them as one migration hid where the real risk sat, and only the first group had a simple answer.
Week of February 13, 2023
Why a file-transfer server belongs on the list of systems that hold PHI
The GoAnywhere breach reached patient data through file-transfer software that is easy to treat as mere plumbing. In fact it is a store of sensitive data with its own exposure, retention and accountability, and it deserves the care given to any core system.
Week of October 10, 2022
In a merged health system, the network decides which hospitals go to paper
Ransomware at CommonSpirit Health in 2022 sent some of its hospitals to paper for weeks while others carried on. In a merged health system, shared logins, shared networks and who can order a shutdown decide how far one attack spreads.
Week of June 13, 2022
Internet Explorer retired; its clinical applications did not
Internet Explorer was retired, but hospitals’ old clinical web applications were not. A compatibility mode in Edge kept them running, and the list it required became a ready-made map of legacy risk, best worked down by who could fix each site.
Week of September 27, 2021
Trust nobody owned: the expired root certificate and hospital legacy clients
On September 30, 2021, an older root certificate used by Let’s Encrypt expired. The websites were fine; the old software talking to them broke. In hospitals, the trouble hid in devices and integrations whose trust lists nobody owned or even knew about.
Week of August 30, 2021
Hurricane Ida and the IT dependencies that sit under the EHR
Hurricane Ida knocked out Louisiana’s grid and phone networks, and hospitals ran on generators for days. The week tested three layers hidden beneath the electronic health record, each owned by a different team: power, connectivity and hosting.
Week of January 20, 2020
Citrix gateways: the most exposed system in the hospital
The Citrix flaw exploited in January 2020 revealed that the gateway clinicians used to reach patient records from outside was a hospital’s most exposed system. Securing it took a clear owner, walls behind it and a search for intruders after every fix.
Week of November 11, 2019
Hospital price transparency began as a data lineage test
CMS’s November 2019 rule told hospitals to publish five kinds of standard charges for every item and service. The numbers lived in different systems, some only as contract formulas. Later rules show the hard part was tracing each figure to its source.
Week of October 14, 2019
Cybersecurity donations priced risk by the connection
HHS’s October 2019 proposals to let hospitals donate cybersecurity to nearby practices treated risk as a property of each connection. That gave hospitals three levers over outside parties: shape the link, strengthen the far end, or restrict it.
All 13 Looking Back articles in Healthcare and Platforms & Architecture
Explainers, checklists and data
Explainer · November 14, 2026
TEFCA and QHINs: how the nationwide exchange framework works, and what ONC’s October 2026 rule changed
TEFCA connects Qualified Health Information Networks under one Common Agreement, overseen by ONC and a Recognized Coordinating Entity. ONC’s rule of October 28, 2026 replaces “ASTP/ONC” with “ONC” throughout 45 CFR part 172, effective December 28, 2026.
Explainer · November 14, 2026
The CMS Interoperability and Prior Authorization rule (CMS-0057-F), explained
CMS-0057-F gave Medicare Advantage, Medicaid, CHIP and Exchange plans prior authorization deadlines and public metrics from 2026, and four FHIR APIs to build by 2027. Later rules in 2026 eased the provider measure and proposed adding drugs.
Checklist · November 14, 2026
Checklist: information blocking compliance for certified health IT developers and HINs/HIEs
Fourteen steps for the actors OIG can fine up to $1 million per violation: confirming actor status, the knows-or-should-know standard, building the exceptions into how requests, fees, licenses and downtime are handled, and the developer attestation.
Checklist · November 14, 2026
Checklist: what a cyber device’s premarket submission needs under section 524B and FDA’s February 2026 guidance
Thirteen steps for medical device makers assembling the cybersecurity content of a 510(k), PMA, De Novo, PDP or HDE, separating what section 524B requires from what FDA’s February 3, 2026 guidance recommends.
Checklist · November 14, 2026
Checklist: payers getting ready for the CMS-0057-F API and prior authorization dates
Twelve steps for Medicare Advantage organizations, Medicaid and CHIP programs and plans, and Exchange QHP issuers: the prior authorization rules in force since 2026, the March 31 reports, and the four APIs due in 2027.
Explainer · November 14, 2026
The 2024 42 CFR part 2 rule on substance use disorder records, explained
Compliance with HHS’s 2024 part 2 rule was due February 16, 2026. It lets patients give one consent for treatment, payment and health care operations, lets HIPAA entities redisclose under HIPAA, and applies HIPAA breach notification to part 2 programs, while keeping the bar on use against patients in proceedings.