<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Health Interoperability Review</title><id>https://healthinteropreview.com/</id><updated>2026-07-19T18:00:00.000Z</updated><link href="https://healthinteropreview.com/feed.xml" rel="self"/><entry><title>CMS interoperability FAQ refresh sharpens the 2027 API readiness checklist</title><id>https://healthinteropreview.com/news/cms-api-faq-readiness-clarifications/</id><link href="https://healthinteropreview.com/news/cms-api-faq-readiness-clarifications/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-07-16T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The living guidance adds implementation context for impacted payers preparing Provider Access, Payer-to-Payer, Prior Authorization, and expanded Patient Access APIs.</summary></entry><entry><title>ONC survey maps the public-health role of 76 regional exchange organizations</title><id>https://healthinteropreview.com/news/hio-public-health-capabilities-2026/</id><link href="https://healthinteropreview.com/news/hio-public-health-capabilities-2026/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-06-30T17:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The national brief shows broad public-health connectivity while documenting the operating services and remaining barriers hidden behind a simple connection count.</summary></entry><entry><title>2026 SVAP clears USCDI v6 for voluntary certification advancement</title><id>https://healthinteropreview.com/news/2026-svap-advances-uscdi-v6/</id><link href="https://healthinteropreview.com/news/2026-svap-advances-uscdi-v6/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-06-30T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The approval creates a newer voluntary path for certified health IT, but it does not replace the USCDI v3 baseline required under HTI-1.</summary></entry><entry><title>TEFCA passes one billion exchanged records as federal oversight increases</title><id>https://healthinteropreview.com/news/tefca-crosses-one-billion-records/</id><link href="https://healthinteropreview.com/news/tefca-crosses-one-billion-records/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-06-26T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The milestone establishes material network activity, while the accompanying oversight actions make participation quality and governance more important than raw volume.</summary></entry><entry><title>C-CDA 5.0 modernizes clinical-document guidance without becoming FHIR</title><id>https://healthinteropreview.com/news/ccda-5-published/</id><link href="https://healthinteropreview.com/news/ccda-5-published/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-06-13T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The release keeps document exchange current and underscores why enterprise programs must manage FHIR resources and CDA documents as different artifacts.</summary></entry><entry><title>US Core 9.0 arrives on FHIR R4 with a new implementation baseline to evaluate</title><id>https://healthinteropreview.com/news/us-core-9-published/</id><link href="https://healthinteropreview.com/news/us-core-9-published/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-05-31T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The guide advances U.S. profiles without changing the underlying fact that major domestic implementation remains anchored to FHIR R4.</summary></entry><entry><title>HTI-2's final scope centers TEFCA trust rules rather than its broader proposal</title><id>https://healthinteropreview.com/news/hti-2-final-tefca-governance/</id><link href="https://healthinteropreview.com/news/hti-2-final-tefca-governance/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-04-29T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The final rule establishes a federal TEFCA regulatory part while leaving unfinalized proposals withdrawn, a distinction current summaries must preserve.</summary></entry><entry><title>HTI-3 revises information-blocking exceptions around reproductive-health information</title><id>https://healthinteropreview.com/news/hti-3-information-blocking-exceptions/</id><link href="https://healthinteropreview.com/news/hti-3-information-blocking-exceptions/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-03-31T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The final rule changes the Privacy and Infeasibility Exceptions and adds a Protecting Care Access Exception, requiring policy and workflow review beyond technical exchange settings.</summary></entry><entry><title>CARIN Blue Button 2.2 updates the consumer claims-data implementation layer</title><id>https://healthinteropreview.com/news/carin-blue-button-2-2-published/</id><link href="https://healthinteropreview.com/news/carin-blue-button-2-2-published/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2026-03-27T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The current guide provides a sharper reference for consumer-directed claims exchange, while payer obligations and production readiness still require separate verification.</summary></entry><entry><title>HTI-5 remains a planning input, not a current certification requirement</title><id>https://healthinteropreview.com/news/hti-5-remains-proposed/</id><link href="https://healthinteropreview.com/news/hti-5-remains-proposed/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2025-12-22T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The proposed rule points toward further certification, API, and information-blocking changes, but its provisions cannot be scored as final obligations.</summary></entry><entry><title>Oracle joins the designated QHIN roster as TEFCA network choice expands</title><id>https://healthinteropreview.com/news/oracle-designated-qhin/</id><link href="https://healthinteropreview.com/news/oracle-designated-qhin/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2025-12-18T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The designation adds another national participation route, but buyers still need to verify exchange purposes, onboarding paths, ecosystem reach, and operating responsibilities.</summary></entry><entry><title>TEFCA QTF 2.1 resets the technical reference point for QHIN exchange</title><id>https://healthinteropreview.com/news/tefca-qtf-2-1-published/</id><link href="https://healthinteropreview.com/news/tefca-qtf-2-1-published/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2025-12-04T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The framework update makes version control, operating-procedure alignment, and participant impact assessment necessary parts of national-network diligence.</summary></entry><entry><title>Netsmart designation adds a behavioral-health and human-services route into TEFCA</title><id>https://healthinteropreview.com/news/netsmart-designated-qhin/</id><link href="https://healthinteropreview.com/news/netsmart-designated-qhin/"/><updated>2026-07-19T18:00:00.000Z</updated><published>2025-08-05T16:00:00.000Z</published><author><name>Health Interoperability Review Research Desk</name></author><summary>The QHIN entry broadens participation choices for care settings that have often sat outside hospital-centered exchange patterns.</summary></entry></feed>