Interoperability moves into practice

The U.S. is shifting interoperability from a policy goal to a working product: CMS launched the first wave of a new ‘health technology ecosystem’ to cut paper forms and streamline patient access, and eHealth Exchange demonstrated a real-world patient-access capability with partners b.well and DaVita. These moves signal buyers will soon expect concrete, user-facing access flows — not just a checkbox for standards — and vendors will need to show identity, query orchestration and reliable retrieval at scale. (hcinnovationgroup.com) (globenewswire.com)

The old promise in U.S. health care was “your data should follow you.” On April 9, the Centers for Medicare & Medicaid Services turned that into a product launch, showing patient apps, digital check-in tools, and a new Medicare App Library instead of another policy memo. (cms.gov) More than 700 organizations have now pledged support for the Centers for Medicare & Medicaid Services health technology ecosystem, and the agency said it showed tools from more than 50 companies at the first-wave event. The point was simple: fewer clipboards, fewer faxed forms, and more health information moving through a phone scan and an app. (cms.gov) (hcinnovationgroup.com) This is a bigger shift than it sounds because interoperability used to mean two hospitals technically speaking the same language somewhere in the background. The Centers for Medicare & Medicaid Services framework now says the test is whether a patient using an app of their choice can actually pull records from across the network without special status or extra portal credentials. (cms.gov) The agency’s blueprint is voluntary, not a new regulation, and it is built around shared rules for identity, security, and data exchange. The Centers for Medicare & Medicaid Services says it will supply public infrastructure like a National Provider Directory, modern identity on Medicare.gov, and expanded data-sharing capabilities, while private companies build the consumer-facing tools on top. (cms.gov 1) (cms.gov 2) One of the most concrete requirements sits in the identity layer. The framework says that if a patient shows a high-assurance digital credential through a Centers for Medicare & Medicaid Services-approved service, network nodes should return that patient’s electronic medical information without asking them to remember which hospital portal holds which record. (cms.gov) That is why “kill the clipboard” keeps showing up in the rollout. The Centers for Medicare & Medicaid Services is pushing providers and software vendors to accept inbound patient data through Quick Response codes, Smart Health Cards, or links built on Fast Healthcare Interoperability Resources bundles, so a waiting-room form works more like mobile boarding passes than like a stack of paper. (cms.gov 1) (cms.gov 2) The same day, eHealth Exchange showed what that looks like on a live network instead of on a slide. eHealth Exchange says it supports more than 300 million patients, facilitates 25 billion data exchanges a year, and stores zero patient data itself, which makes it more like a switching system than a giant central vault. (ehealthexchange.org) Its role here is the plumbing. eHealth Exchange provides a single application programming interface and trust framework so hospitals, health information exchanges, federal agencies, and payers can find and request records nationwide, and it also connects participants to Carequality and the Trusted Exchange Framework and Common Agreement, the federal on-ramp for nationwide exchange. (ehealthexchange.org 1) (ehealthexchange.org 2) (ehealthexchange.org 3) The demonstration with b.well and DaVita matters because DaVita runs roughly 90 percent of U.S. dialysis centers connected through eHealth Exchange’s network, and b.well is listed by the Centers for Medicare & Medicaid Services as one of the first-wave companies building patient-facing tools. That combination turns “access” from a standards checkbox into a real retrieval problem across a large, messy care footprint. (ehealthexchange.org) (cms.gov) The next pressure point is scale. Once buyers see a patient authenticate once, search across providers, and pull back usable records into one app, vendors will have to prove they can handle identity checks, patient matching, query routing, and reliable retrieval every day, not just pass a standards certification once a year. That is also why the Office of the National Coordinator for Health Information Technology said at the April 9 event that it plans to carry these innovations into certification and into the Trusted Exchange Framework and Common Agreement. (hcinnovationgroup.com) (ehealthexchange.org) In other words, the market is moving from “can your system speak Fast Healthcare Interoperability Resources” to “can a patient actually get their records on a Tuesday morning without calling the help desk.” The winners in this phase will not be the companies with the cleanest standards slide, but the ones that can make identity, consent, search, and retrieval feel boringly reliable. (cms.gov) (cms.gov)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.