Live patient‑access demo by eHealth Exchange
eHealth Exchange demonstrated real‑world patient access—working with b.well and DaVita—to show individual patient queries and data retrieval across networks, a concrete step toward CMS interoperability goals. The demo was presented as evidence that standards‑based queries can support real production use cases rather than just spec compliance. (globenewswire.com)
A lot of “health data access” announcements are really software companies proving they can pass a test. This one was a live demo in Washington, with a real patient query moving through a real network from a consumer app to a kidney-care provider and back. (globenewswire.com) The setup was simple enough to picture: b.well Connected Health supplied the app, DaVita supplied the patient record, and eHealth Exchange handled the trust and routing between them. In the demo, a kidney patient used the app to request records from a DaVita location and retrieve them securely. (globenewswire.com) That sounds ordinary until you remember how most medical records still work in practice. A patient can see one hospital’s portal, one clinic’s portal, and one insurer’s portal, but those systems often behave like separate filing cabinets with different keys. (cms.gov) The federal push to fix that has been running for years. The Centers for Medicare and Medicaid Services used its 2020 Interoperability and Patient Access rule to require many insurers to make claims, encounter, and some clinical data available through a patient-facing application programming interface, which is a standard software doorway for apps to pull data with permission. (cms.gov) That push expanded again in January 2024. The Centers for Medicare and Medicaid Services said its Interoperability and Prior Authorization final rule added new application programming interface requirements and kept pressing payers to exchange data in more usable ways. (cms.gov) The hard part is not just building one doorway. The hard part is getting thousands of organizations to trust each other’s identity checks, security rules, and message formats so a patient’s app can ask one question and get a usable answer from somewhere else. (healthit.gov) That is where networks come in. The Trusted Exchange Framework and Common Agreement, a federal structure launched in 2022, is meant to create a nationwide “network of networks” so data can move across organizational boundaries instead of staying trapped inside one vendor or one health system. (healthit.gov) There is also a patient version of that idea. Under Individual Access Services, patients can use an app of their choice to retrieve copies of their records from participants in the Trusted Exchange Framework and Common Agreement, much like connecting a bank account to a budgeting app. (open.epic.com) eHealth Exchange did not present this week’s demo as a lab exercise. It said the point was to show that standards-based patient access can support individual patient queries in production-style conditions, using the Carequality framework as the trust layer between the app and the provider. (globenewswire.com) DaVita is a useful test case because kidney patients often have long, complicated treatment histories that span clinics, labs, hospitals, and insurers. A single patient with end-stage kidney disease may need regular dialysis, specialist visits, lab trends, and medication changes, which makes fragmented records more than a paperwork problem. (globenewswire.com) eHealth Exchange says its network supports more than 300 million patients and facilitates more than 25 billion data exchanges each year. If patient-directed queries start working across infrastructure at that scale, the story stops being “can the standard work” and becomes “which apps patients will actually want to use.” (ehealthexchange.org, briefglance.com)
