US Health IT Chief Keane Sees AI Rivals Cracking EHR Oligopoly

The Next Era of Health Data: AI, Open APIs, and the End of the EHR Oligopoly — Julie Yoo, Colin Rom, Thomas Keane

Julie Yoo, Colin Rom, Thomas Keane

National Coordinator Tom Keane predicts artificial intelligence will yield a direct challenger to entrenched acute care record vendors within two years as federal regulators dismantle certification hurdles and penalize data hoarding.

AI-assisted summary of The Next Era of Health Data: AI, Open APIs, and the End of the EHR Oligopoly — original source. Check the original for full context.

Source published:

Key ideas

  • National Coordinator for Health IT Dr. Tom Keane predicts a viable new competitor will emerge to disrupt the entrenched acute-care EHR oligopoly within just one to two years, driven by generative AI and vibe coding. (31:25)
  • ONC is moving to eliminate its certified AI transparency 'model card' mandate after public filings revealed near-zero market adoption, with Oracle reporting roughly 2 queries per month and Epic around 50. (20:00)
  • TEFCA has scaled to approximately 1.7 billion cumulative transactions and is processing roughly 200 million transactions per month as a national public utility for health data exchange. (10:00)
  • ONC is partnering with the HHS Office of Inspector General, FTC, and DOJ to actively police whether incumbent data restrictions reflect legitimate security concerns or competitive moats masquerading as compliance. (25:00)

Detailed notes

## Background Published on RSS and the web on October 29, 2026, by Julie Yoo, Colin Rom, and National Coordinator for Health IT Dr. Tom Keane, this episode explores healthcare's shift from basic EHR digitization to data liquidity, patient access, and open competition. According to the show description, the conversation covers how data moves via APIs and TEFCA, how wearables and AI integrate into clinical workflows, and how privacy concerns can turn into competitive moats, culminating in Dr. Keane's prediction of a new EHR competitor within one to two years.

## TL;DR Dr. Tom Keane details the evolution of federal health IT policy, explaining how early HITECH incentives unintentionally fueled a closed hospital EHR oligopoly and how subsequent 21st Century Cures Act mandates aim to return data stewardship to patients. He highlights ONC's current shift toward acting as an open platform builder through standardized patient-facing APIs, the nationwide scaling of TEFCA, and the streamlining of rules like HTI-6, which scraps ineffective AI model card mandates to reduce compliance burdens for new entrants. Keane also details the specific diagnostic tests federal agencies use to police information blocking disguised as security concerns. Ultimately, he predicts that the combination of open APIs, vibe coding, and generative AI will give rise to a viable challenger against incumbent EHR giants within one to two years.

## Atmosphere & style The conversation strikes an engaging, collegial tone that seamlessly bridges deep federal policy wonkiness with startup-world technical optimism. Julie Yoo and Colin Rom bring seasoned venture insider perspectives, trading lighthearted banter with Dr. Keane about technology lore at UIUC alongside Marc Andreessen and the absurdities of health system HIPAA compliance. The narrative feels lucid, candid, and pragmatic, moving briskly from historical statutory reflections to concrete enforcement benchmarks, leaving listeners with an energized sense that healthcare's long-stagnant infrastructure is on the cusp of genuine disruption.

## Bulletin - `31:25` National Coordinator for Health IT Dr. Tom Keane predicts a viable new competitor will emerge to disrupt the entrenched acute-care EHR oligopoly within just one to two years, driven by generative AI and vibe coding. - `20:00` ONC is moving to eliminate its certified AI transparency 'model card' mandate after public filings revealed near-zero market adoption, with Oracle reporting roughly 2 queries per month and Epic around 50. - `10:00` TEFCA has scaled to approximately 1.7 billion cumulative transactions and is processing roughly 200 million transactions per month as a national public utility for health data exchange. - `25:00` ONC is partnering with the HHS Office of Inspector General, FTC, and DOJ to actively police whether incumbent data restrictions reflect legitimate security concerns or competitive moats masquerading as compliance.

## Key takeaways - `00:00` Healthcare has completed its digitization phase and entered an interoperability phase where data must follow the patient rather than stay siloed in hospital enterprise software. - `01:46` Dr. Tom Keane brings a multi-disciplinary perspective to ONC, having worked five years in engineering, fifteen years in clinical medicine, and crossed paths with Marc Andreessen at UIUC during the Mosaic launch. - `04:47` EHR adoption stalled between the 2004 Bush executive order and 2009 because, unlike digital PACS in radiology, general EHRs lacked organic financial and operational return on investment. - `04:47` The 2009 HITECH Act drove EHR adoption from 15% to over 90% via $30 billion in incentives, but accelerated market consolidation into an oligopoly tailored around hospital billing and coding rather than clinical usability. - `04:47` The 21st Century Cures Act established the principle of patient data sovereignty, prohibiting information blocking in healthcare in contrast to private data hoarding in search or real estate. - `07:22` The modernization of the banking sector via the SWIFT network in the late 1970s serves as an external precedent for federally guided interoperable infrastructure. - `10:00` ONC's core regulatory foundation rests on three pillars: standardized patient-facing APIs under the 2020 Cures Act rule, TEFCA exchange architecture, and codified information blocking enforcement. - `15:00` Healthcare's structural 'original sin'—where payers and providers change frequently while the patient remains the sole lifelong constant—demands autonomous software agents to manage longitudinal care. - `15:00` Upcoming HTI-6 rules will incorporate non-traditional clinical data such as consumer wearables and biometric readings into standardized observations for AI agents and clinicians. - `20:00` ONC is pivoting its certification strategy away from prescriptive feature mandates and toward interoperability, preventing burdensome compliance programs from blocking nimble startups. - `20:00` Mandated AI model cards failed due to rigid schemas, regulatory arbitrage where AI operated outside certified EHR modules, and preference for bilateral commercial NDAs. - `25:00` Federal regulators assess whether data frictions are anticompetitive by evaluating affiliate favoritism, fee transparency, bounded integration timelines, and parity across EHR vendors. - `25:00` Roughly 90% of reported integration frictions are non-malicious interoperability problems that ONC resolves collaboratively without resorting to inter-agency enforcement. - `30:00` ONC's six-month agenda centers on finalizing HTI-5 to lower market barriers, expanding TEFCA to 100% reliability, and coordinating enforcement with the OIG, FTC, and DOJ. - `31:25` The convergence of open APIs, reduced certification hurdles, and rapid AI development will yield a direct competitor to incumbent hospital EHRs within one to two years.

## Detailed walkthrough ### `00:00` Introduction: Moving from Digitization to Interoperability

Healthcare spent the last fifteen years and tens of billions of dollars migrating from physical paper charts to electronic health records. Now, the battleground has completely shifted: the objective is no longer merely digitizing records, but ensuring that clinical information moves fluidly to patients, third-party applications, and emerging artificial intelligence agents. As Dr. Tom Keane, the National Coordinator for Health IT, and the hosts outline at the opening of the discussion, constraints on how data is shared create profound friction around trust, scale, and security. In the absence of enforceable, standardized ground rules, organizations naturally default to hoarding information rather than leveraging its full potential. The ultimate regulatory and technological vision is to turn the patient into the primary steward of their own medical records, dismantling historical gatekeeping.

The stakes of this transition are heightened by an acute care market dominated by a deeply entrenched hospital software oligopoly. A central question facing the industry is whether modern developer tools, patient-facing application programming interfaces (APIs), the Trusted Exchange Framework and Common Agreement (TEFCA), and generative AI can crack that stronghold. When asked by Julie Yoo how soon the market might witness a viable contender emerge to dismantle the incumbent electronic health record (EHR) oligopoly, Dr. Keane offers an aggressive timeline: within one to two years. Reaching that point requires modernizing the Office of the National Coordinator for Health Information Technology (ONC) regulations, lowering compliance overhead for tech startups, and critically evaluating privacy and security arguments that incumbents often deploy as anticompetitive moats.

- **Regulatory Scope:** ONC is tasked with the direct federal oversight of health information technology standards and nationwide health information exchange. - **Core Policy Objective:** Mandating open, standardized, patient-facing APIs so clinical data follows the patient rather than staying locked inside hospital enterprise systems. - **The Competitive Horizon:** A forecast that generative AI and open data infrastructure will produce direct, viable competitors to dominant acute care EHR incumbents within one to two years.

---

`01:46` Dr. Tom Keane’s Path: Engineering, Medicine, and Marc Andreessen's Mosaic Code

Welcomed by Julie Yoo and Colin Rom, Dr. Keane reflects on an unconventional path that spans three distinct disciplines: engineering, clinical medicine, and federal policy. Julie introduces him as a rare "unicorn" across these domains, prompting Keane to jokingly shoot back: “And thank you for the implication that having done many things, I'm very old.” After completing an undergraduate engineering degree, Keane spent five years working in engineering before deciding to apply to medical school. He practiced clinical medicine for approximately fifteen years, experiencing firsthand the mounting operational headaches, clunky software interfaces, and structural administrative burdens that physicians navigate daily. Motivated by an ambition to reduce those frictions and advocate directly for physicians and patients, he joined the government, taking on roles within ONC before rising to lead the agency.

```mermaid flowchart LR accTitle: Dr. Tom Keane Career Trajectory accDescr: Flowchart tracing Dr. Tom Keane's career from engineering to medicine, government policy, and heading ONC. A["Engineering Graduate<br/>(5 Years in Industry)"] --> B["Clinical Medicine<br/>(15 Years in Practice)"] B --> C["Government Service<br/>(ONC Policy & Leadership)"] C --> D["National Coordinator<br/>for Health IT"] ```

The conversation takes a nostalgic detour into technology history when Julie notes that Dr. Keane attended the University of Illinois Urbana-Champaign at the exact same time as Netscape co-founder Marc Andreessen. Keane confirms that their tenures directly overlapped, with Andreessen graduating in 1993 and Keane in 1994. In March of 1993, Andreessen and Eric Bina publicly released the Mosaic web browser, transforming UIUC into ground zero for the modern commercial Internet. As an engineering student, Keane recalls walking over to inspect the physical boards where top students' names were posted to see who this suddenly famous creator was, and digging directly into the raw source code. Keane recalls looking through the original Mosaic codebase and noting that every single developer comment left by Andreessen was signed under the handle “Marca.” While he cannot recall if they ever crossed paths in the campus hallways, Keane remembers the electric atmosphere of the department, prompting Julie to remark that “there was something in the water.”

- **Career Path:** Transitioned from five years in engineering to fifteen years in clinical practice before entering public service at ONC. - **University of Illinois Overlap:** Attended UIUC alongside Marc Andreessen during the development and launch of the Mosaic web browser in March 1993. - **Historical Milestone:** Mosaic is remembered as the first commercially viable graphical web browser that ignited consumer adoption of the World Wide Web.

---

`04:47` The History of ONC: From Bush's 2004 Order to the Cures Act

To demystify ONC’s mandate, Dr. Keane traces its institutional trajectory over the past two decades. He notes with amusement that until a recent agency reorganization, his formal title was Assistant Secretary for Technology Policy / National Coordinator for Health IT, which gave him the single longest title in the entire federal government. ONC was originally established by executive order in 2004 under President George W. Bush with a 10-year goal to have every hospital in America operating on electronic health records. However, virtually zero meaningful adoption occurred between 2004 and 2010. Hospitals had readily adopted Picture Archiving and Communication Systems (PACS) for digital diagnostic imaging—starting with the first PACS system at the University of Maryland in 1989 and reaching near-universal hospital penetration by 2000—because digital radiology provided clear internal economic returns, natural clinical utility, and native interoperability. General EHRs lacked those commercial and operational tailwinds.

The stagnation ended abruptly in 2009 when President Barack Obama signed the Health Information Technology for Economic and Clinical Health (HITECH) Act, attaching $30 billion in direct financial adoption incentives alongside future regulatory penalties. Putting that scale in perspective, Keane observes: “And to give you an idea, back then, the total budget of the NIH was $30 billion. So, the incentives provided for EHR adoption were equal to the incentives for the United States.” The massive cash infusion worked: hospital and provider EHR adoption skyrocketed from roughly 15% in 2010 to over 90% by 2015. ONC served as the structural architect, managing program design and establishing a functional software certification floor to prevent providers from purchasing low-quality software just to capture incentive checks.

```mermaid flowchart TD accTitle: Federal Health IT Policy Evolution accDescr: Diagram showing the timeline of ONC policies from the 2004 Bush Executive Order through the HITECH Act, the Cures Act, to the modern platform builder era. subgraph S1["Digitization Phase (2004–2015)"] A["2004: Bush Executive Order<br/>(10-Year EHR Goal; Market Stalls)"] --> B["2009: HITECH Act<br/>($30B Incentives; 15% to 90% Adoption)"] end subgraph S2["Unintended Frictions (2015–2016)"] B --> C["CFO-Driven Purchasing<br/>(Billing/Coding Priority; Poor UX)"] B --> D["EHR Oligopoly<br/>(4-5 Vendors Lock Up 95% Market)"] end subgraph S3["Interoperability & Platform Phase (2016–Present)"] C & D --> E["2016: 21st Century Cures Act<br/>(Reduce Burden; Mandate Data Sharing)"] E --> F["Modern Mandate: ONC as Platform Builder<br/>(APIs, TEFCA, Patient Data Sovereignty)"] end ```

By 2015 and 2016, two severe structural market failures emerged from that rapid rollout. Because systems were procured by hospital chief executive officers and chief financial officers rather than bedside clinicians, software vendors tailored their products almost exclusively to revenue cycle management, billing, and coding rather than clinical ergonomics or patient utility. Concurrently, the market consolidated into an oligopoly where four to five dominant EHR vendors controlled 90% to 95% of the sector, locking proprietary customer data inside closed silos. In response, Congress passed the 21st Century Cures Act in 2016 with near-unanimous bipartisan support. The Cures Act established two clear legal mandates: drastically reduce administrative documentation burdens on clinicians, and outlaw information blocking by requiring data sharing. Dr. Keane highlights how unique this standard is across the broader economy:

> “When a company like Google acquires data from prior searches, they're under no obligation to share that. When a real estate company acquires data about what units are renting for and what units are selling for, they are not under any obligation to share that freely. They can sell that information and it can be leveraged by their customers for competitive advantage. The same is not true in healthcare. Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient.”

Under Dr. Keane's tenure, ONC's focus has evolved from certifying closed EHR modules into acting as an open platform builder. The mandate is to establish transparent regulatory rails so clinical information flows freely, empowering patients and enabling third-party developers to lower systemic costs, improve clinical outcomes, and build thousands of novel healthcare applications.

- **2004 Mandate:** Executive order under President George W. Bush set a 10-year timeline for universal hospital EHR adoption, but stalled due to misaligned financial incentives. - **The PACS Contrast:** The first Picture Archiving and Communication System deployed at the University of Maryland in 1989; by 2000, market adoption was near 100% without federal funding because diagnostic imaging offered inherent financial and clinical returns. - **The HITECH Juggernaut (2009):** Injected $30 billion—matching the total annual budget of the National Institutes of Health at the time—propelling electronic records adoption from 15% to 90% between 2010 and 2015. - **Market Failures:** Accelerated purchasing created an entrenched oligopoly of 4 to 5 vendors covering 90% to 95% of the acute care hospital landscape, heavily biased toward enterprise billing and coding. - **The 21st Century Cures Act (2016):** Bipartisan legislation legally prohibiting data blocking, directing the reduction of physician administrative burden, and codifying patient data ownership.

---

`07:22` A Precedent for Mandated Interoperability: Financial Networks

Julie Yoo reflects on launching her first health tech startup right as the HITECH Act was rolling out nationwide, recalling how surreal it felt to see an entire, historically sluggish industry flip almost overnight from paper files to digital records. She asks whether ONC or federal policymakers looked to any historical precedents outside of healthcare when structuring a program that explicitly tied billions of taxpayer dollars to the adoption of a specific technological architecture. While such top-down federal technology mandates are exceptionally rare in the private sector, Dr. Keane points to the modernization of the financial sector as a historical analog. In the late 1970s, government authorities actively pushed for the adoption and maturation of the Society for Worldwide Interbank Financial Telecommunication (SWIFT) network. The goal was to ensure disparate banking institutions could securely exchange transaction data across standardized networks, establishing an interoperable backbone for the global economy.

- **Historical Precedents:** Direct federal subsidies tied to specific private software implementations are essentially unprecedented in American commercial industry. - **Financial Analog:** Dr. Keane cites the late-1970s push for the SWIFT banking network as a comparable instance where public policy helped drive private financial institutions onto a standardized, interoperable communications infrastructure.

`10:00` The Core Mandates of ONC: Patient APIs, TEFCA, and Information Blocking

The discussion begins by examining the government's role in standardizing infrastructure at national scale, comparing health IT to sectors like air traffic control. The unique aspect of the healthcare transition was the deployment of federal financial incentives under President Barack Obama, Jonathan Gruber, and administration officials, driven by the belief that digitizing healthcare would lower costs and improve system management. However, as medical records moved onto digital rails, intense lobbying emerged across stakeholders who believed data belongs to the patient and must move freely rather than being monopolized by a handful of well-intentioned electronic health record (EHR) vendors.

When asked about the most underrated accomplishments of the Office of the National Coordinator for Health Information Technology (ONC) that empower today's builders, Dr. Tom Keane jokes that none of his agency's accomplishments are underrated, before outlining three foundational pillars:

```mermaid flowchart TD accTitle: ONC Interoperability and Governance Pillars accDescr: Three pillars enacted by ONC to free healthcare data from EHR vendor lock-in.

subgraph Pillars["ONC Policy Foundations"] A["2020 Cures Act Final Rule<br>Standardized Patient-Facing APIs"] B["TEFCA & QHIN Technical Framework<br>Nationwide Exchange Infrastructure"] C["Information Blocking Rules<br>Legal Deterrents & Codified Exceptions"] end

subgraph Impact["Ecosystem Impact"] D["Secure Patient-Permissioned<br>Third-Party App Access"] E["1.7B Transactions Handled<br>(~200M per Month)"] F["Elimination of Anti-Competitive<br>Data Hoarding"] end

A --> D B --> E C --> F ```

First, under the 2020 Cures Act final rule, ONC mandated that every certified EHR expose a standardized, patient-facing application programming interface (API). This established strict security postures and standardized protocols, giving third-party applications the right to retrieve patient data with verified patient identity and permission. Second, ONC operationalized the Trusted Exchange Framework and Common Agreement (TEFCA), which was originally mandated in the 21st Century Cures Act of 2016. Keane highlights that healthcare operates under extreme constraints regarding trust, liability, and the risk of patient harm—illustrating this with the absurd reality that major health systems routinely call ONC for clarification on whether sending a simple bereavement card to a deceased patient's family constitutes a HIPAA violation. To solve the friction of disparate legal agreements, privacy safeguards, and "minimum necessary" payment rules, TEFCA establishes a unified national baseline:

> “By standing up TEFCA, we've tried to address this under a common agreement. We've tried to say here's one agreement, one set of protocols, one stand, you know, QHIN technical framework, we call it, to allow for the exchange of information.”

Third, Keane cites the codification and federal enforcement of information blocking rules. By laying out clear exceptions where withholding data is justified for privacy and security—while making anti-competitive data hoarding illegal across health systems and technology vendors—ONC established clear ground rules for market conduct.

- TEFCA currently operates at a volume of approximately 1.7 billion cumulative transactions, scaling at roughly 200 million transactions per month. - ONC's goal for TEFCA is to establish a 100% reliable, robust national public utility for data liquidity. - Enforcement of information blocking operates across inter-agency partnerships within the federal government to ensure strict market compliance.

---

`15:00` Expanding Beyond EHRs: Wearables, HTI-6, and AI Agents

Julie Yoo reflects on how unusual healthcare is compared to other industries, noting that it benefits from federal regulation actively mandating modern technological primitives like APIs that empower software builders. However, she points out a looming regulatory boundary: existing rules target traditional EHRs, acute care hospitals, and outpatient clinics. Today's explosive growth in health data happens outside traditional clinical and billing workflows—through continuous consumer wearables, patient chat platforms, and direct-to-consumer biomarkers. Yoo warns that founders risk stalling if they fear future rules might penalize their current data practices, and asks how ONC intends to address this frontier.

Keane responds by confirming that ONC has formally accounted for this migration in its upcoming HTI-6 (Health Data, Technology, and Interoperability) rule, published in the federal Unified Agenda. He ties this evolution directly to resolving what Yoo has previously characterized as healthcare's "original sin"—the structural reality that healthcare providers and payers who invest in keeping a patient healthy rarely capture the financial return, because patients constantly switch employers, insurers, and hospital networks.

Keane argues that the only lifelong constant is the patient themselves, supported by autonomous software and clinicians:

> “Our vision is that the patient will be the ultimate steward of their information and that in a really well-functioning market, you'll have an agent, whether it's a piece of software or some piece of software in collaboration with a doctor that will longitudinally be responsible for that patient and be able to benefit from that patient being taken care of.”

To make this vision real, ONC is focusing on standardizing device data into structured, clinically reliable observations that flow bidirectionally between traditional EHRs and external consumer applications. Keane highlights the present reliability challenge: wearing two different smartwatches on opposite wrists often yields conflicting biometric readings. Addressing this requires robust data standards so that traditional clinical systems trust external signals, while artificial intelligence agents—and synthetic intelligence (SI)—can access rich clinical histories to safely execute actions on behalf of patients.

`20:00` HTI-6, Vibe Coding, and Why ONC Is Scrapping AI Model Cards

Dr. Tom Keane outlines the upcoming regulatory priorities at ONC, noting that the agency is aiming to release the HTI-6 (Health Data, Technology, and Interoperability) proposed rule in the fall. The primary objective is establishing provenance, auditability, and execution traces for autonomous AI actions in clinical settings to support post-market surveillance against AI model drift. Addressing Julie Yoo’s observation that the very definition of an electronic health record (EHR) is fundamentally changing as care and data move beyond hospital walls, Dr. Keane explains that ONC is pivoting: instead of mandating basic in-system clinical and billing features, the agency is substantially dialing back its certification program to focus almost exclusively on interoperability and lowering barriers to entry.

```mermaid flowchart TD accTitle: Failures of Mandated AI Model Cards Under Health IT Certification accDescr: Diagram illustrating the five core reasons why ONC proposed eliminating the certified model card requirement.

subgraph CertificationIssues["Structural Flaws of Model Card Mandates"] A["Static Requirement<br/>(Rigid 31 source attributes)"] --> F["Policy Flaws"] B["Narrow Scope<br/>(Applied only to certified EHRs;<br/>apps simply migrated outside)"] --> F C["Near-Zero Adoption<br/>(Oracle: ~2 queries/month;<br/>Epic: ~50 queries/month)"] --> F D["False Assurance<br/>(No audit backing or verification;<br/>empty 'Good Housekeeping' seal)"] --> F E["Bilateral Alternatives<br/>(Commercial buyers prefer<br/>proprietary NDAs for secret sauce)"] --> F end

F --> G["HTI-6 Deregulation:<br/>Drop Model Card Requirement &<br/>Slash Costs for New EHR Entrants"] ```

Dr. Keane illustrates this deregulatory push by discussing the decision to eliminate the AI transparency "model card" requirement that took effect on January 1, 2025. Practical market feedback demonstrated that the mandate was fundamentally not fit for purpose: - **Commercial reality and IP protections:** Enterprise buyers and physicians do not rely on generic public model cards; if a model's capabilities or data are proprietary, vendors prefer disclosing their "secret sauce" directly under non-disclosure agreements (NDAs). - **Inflexible data schemas:** ONC mandated 31 static source attributes, which industry participants immediately criticized as either the wrong attributes or vastly too complex compared to a practical five-attribute standard. - **Regulatory arbitrage:** Because certification requirements only govern certified health IT modules, vendors merely unbundled their software, running standalone AI tools outside the EHR architecture to evade compliance entirely. - **Dismal market utilization:** Certified EHR vendors reported virtually no engagement. Public comment filings revealed Oracle received only approximately 2 queries per month, while Epic reported roughly 50 queries per month across their entire client footprints. - **Lack of authentic verification:** From a physician's perspective, Dr. Keane stresses that the cards functioned as an unvetted facade: “It had the purpose of serving as a good housekeeping seal of approval that didn't actually have any audit or backing or assurance behind it, so that's why we proposed removing it.”

Reflecting on the pace of modern software development, Dr. Keane notes that burdensome federal certification cannot be allowed to freeze out nimble founders. As he puts it: “In the days of vibe coding, you can create a new electronic health record or a company that is a system of record or a company that performs many of the functions that a system of record would, you can create that quickly, probably in a year or two with vibe coding. And we did not want to be standing in the way with a costly, burdensome certification program.”

---

`25:00` Identifying "Competitive Moats Masquerading as Privacy and Security Concerns"

Julie Yoo brings up the inherent friction between incumbent health IT vendors and new tech entrants. While incumbents routinely justify data restrictions on the grounds of patient privacy, cybersecurity, and risk aversion, entrants view these obstacles as deliberate anti-competitive walls. Yoo observes that while it is easily 100 times easier for a digital health founder to integrate with an EHR today than it was 15 years ago, substantial friction persists. Dr. Keane agrees that the balance is an evolving target: advances in identity, authentication, and authorization elevate baseline expectations, while external risks like quantum computing and sophisticated AI create genuine security vulnerabilities.

```mermaid flowchart LR accTitle: Diagnostic Tests for Distinguishing Legitimate Security from Information Blocking accDescr: Flowchart showing criteria used by ONC, OIG, FTC, and DOJ to determine whether vendor data frictions are anticompetitive.

A["Vendor Restricts Data Access"] --> B{"Diagnostic Tests"}

subgraph Tests["Evaluating Friction Legitimacy"] B --> C["Affiliate Favoritism<br/>(Easier access for internal partners?)"] B --> D["Commercial Terms<br/>(Are API fees & terms public & at market rates?)"] B --> E["Timeline Delivery<br/>(Do development milestones have concrete ends?)"] B --> F["Vendor Outlier Status<br/>(Works with 3 vendors, blocked by 2?)"] end

C & D & E & F --> G{"Adjudication"} G -->|"Legitimate risk"| H["Work with ONC on standards"] G -->|"Bad-faith barrier"| I["OIG / FTC / DOJ<br/>Enforcement Action"] ```

However, Dr. Keane makes clear that federal regulators actively evaluate whether these frictions are legitimate technical hurdles or bad-faith anticompetitive behavior: “There are certain ways that we can evaluate whether the frictions that somebody in the market are experiencing are legitimate privacy and security concerns or whether they are competitive moats masquerading as privacy and security concerns.” To police this boundary, ONC coordinates with the HHS Office of Inspector General (OIG), the Federal Trade Commission (FTC), and the Department of Justice (DOJ), evaluating friction using concrete benchmarks: - **Affiliate disparity:** Inspecting whether a health data holder grants its own corporate affiliates or preferred commercial partners faster onboarding, lower development hurdles, and easier data access than outside third parties. - **Transparency of commercial terms:** Checking whether API documentation, onboarding timelines, and access fees are published openly and set at fair, standard market rates. - **Bounded integration timelines:** Verifying that vendor integration timelines have explicit, realistic completion dates rather than open-ended, indefinite delays. - **Cross-vendor parity:** Checking if an application functions smoothly across multiple peer EHR vendors while being uniquely stalled by one or two outliers failing their information-blocking statutory obligations.

Dr. Keane directly solicits input from digital health founders and technology developers, pointing out that 90% of observed frictions stem from standard market friction or interoperability gaps that can be resolved via technical coordination. Emphasizing that “the C in my name is Coordinator—we are there to coordinate with the healthcare market,” he urges startups to report friction directly to ONC or via the official information blocking portal. When problems are flagged with specific potential solutions, ONC can often prompt incumbents to alter their behavior collaboratively; only when deliberate noncompliance persists does the agency transition to an aggressive enforcement posture alongside its regulatory partners.

`30:00` Agency Priorities: HTI-5, TEFCA Expansion, and Inter-Agency Enforcement

Dr. Tom Keane lays out the immediate operational and regulatory roadmap for the National Coordinator's office, stressing that active industry engagement is central to the agency's mission. He encourages health tech founders and organizations to work directly with his team and participate in initiatives like CMS’s health tech ecosystem, which currently convenes around 1,700 participants to shape both policy and shared technical solutions. Outlining goals for the immediate six months ahead, Keane highlights the finalization of the HTI-5 rule (Health Data, Technology, and Interoperability) to lower barriers to market entry, alongside ongoing refinements to federal information blocking regulations.

At the same time, the agency plans to ramp up investments in the Trusted Exchange Framework and Common Agreement (TEFCA) national infrastructure. The goal is to ensure TEFCA achieves 100 percent reliability, expands its active use cases, and solidifies its standing as an indispensable, ubiquitous rail for health data exchange. Crucially, Keane makes clear that facilitation will be paired with an assertive enforcement posture, coordinating across federal bodies to hold bad actors accountable under congressional mandates.

```mermaid flowchart TD accTitle: Health IT Interoperability and Enforcement Framework accDescr: Diagram illustrating the policy initiatives and joint enforcement agencies overseen by the National Coordinator.

subgraph Policy ["Immediate Policy & Infrastructure (Next 6 Months)"] A["Finalize HTI-5 Rule"] --> D["Lower Market Entry Barriers"] B["Refine Information Blocking Rules"] --> E["Eliminate Anti-Competitive Lock-In"] C["Scale TEFCA National Rails"] --> F["Expand Use Cases & Ensure 100% Reliability"] end

subgraph Enforcement ["Coordinated Enforcement Posture"] G["Congressional Mandate"] --> H["National Coordinator / ASTP"] G --> I["HHS Office of Inspector General (OIG)"] G --> J["Federal Trade Commission (FTC)"] G --> K["Department of Justice (DOJ)"] H & I & J & K --> L["Strong, Unified Market Signal"] end ```

- In describing the open-door ethos of his agency, Dr. Tom Keane emphasizes: “We will engage with everybody. It is the main purpose of our organization of the agency is to coordinate.” - Addressing compliance and market expectations, Keane asserts: “We believe that we've been given a charge by Congress with laws to make sure that these laws are complied with. And between us, the OIG, the FTC, and the DOJ, we believe that we will send a strong signal to the market in a way that everybody can be agreeable to.” - All major updates—finalizing HTI-5, clarifying information blocking boundaries, and fortifying TEFCA—are slated for rollout within the upcoming six months.

---

`31:25` A "Spicy Question": Predicting the Fall of the EHR Oligopoly

Julie Yoo closes the interview with a provocative question targeting the consolidated acute care electronic health record (EHR) market. Given federal efforts to promote open APIs, liquid data, and competition, she asks Keane directly: when will the market finally see a genuine new contender challenge the dominant hospital EHR oligopoly—in two years, five years, or ten years? Keane reflects on the broader history of computing, comparing the current artificial intelligence revolution to witnessing the birth of the personal computer and the advent of the internet.

Keane argues that the capabilities unlocked by AI are so profoundly transformative that market structures will inevitably shift. While existing systems of record recognize these shifts and are attempting to adapt to find their place, Keane delivers a surprisingly aggressive timeline: he expects a serious competitive contender to enter the field within just one to two years. Welcoming the forecast, Yoo and Colin Rom promise to bring him back onto the podcast at the two-year mark to assess how new EHR CEOs are performing on the playing field.

- Asking for a concrete forecast, Julie Yoo challenges: “When do you think we will see a contender enter the playing field to break that oligopoly? Is it another two years? Is it another five years? Is it another 10 years?” - Placing the current technological wave in perspective, Keane notes: “Of all the things I've gotten to see in my life develop from the personal computer I'm old enough to remember when those came online to the internet SI is truly transformative.” - Delivering his exact forecast, Keane declares: “So to be more concrete one to two years.” - Setting up the future reunion, Keane jokes: “Invite me back in two years and in addition to telling me I've gotten two years older you can and then we can see how some of the CEOs of the companies that are in the new playing field of the future EHR.”

## Notable quotes > `04:47` Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient. — Dr. Tom Keane

> `25:00` There are certain ways that we can evaluate whether the frictions that somebody in the market are experiencing are legitimate privacy and security concerns or whether they are competitive moats masquerading as privacy and security concerns. — Dr. Tom Keane

## Mentioned Dr. Tom Keane, Julie Yoo, Colin Rom, Marc Andreessen, Eric Bina, George W. Bush, Barack Obama, Jonathan Gruber, ONC (Office of the National Coordinator for Health Information Technology), ASTP (Assistant Secretary for Technology Policy), TEFCA (Trusted Exchange Framework and Common Agreement), HITECH Act, 21st Century Cures Act, HTI-5, HTI-6, PACS (Picture Archiving and Communication System), Mosaic, University of Illinois Urbana-Champaign, University of Maryland, NIH (National Institutes of Health), CMS (Centers for Medicare & Medicaid Services), HHS Office of Inspector General (OIG), Federal Trade Commission (FTC), Department of Justice (DOJ), SWIFT, Epic, Oracle, Google, a16z

## Video description Healthcare spent the last 15 years digitizing medical records. Now the challenge is making that data useful to patients, AI agents, and new health technology companies. National Coordinator for Health IT Dr. Tom Keane says the next phase is about interoperability, patient access, and lowering barriers for new entrants. Tom joins a16z’s Julie Yoo and Colin Rom to discuss how healthcare data can move more easily through APIs and TEFCA, how wearables and AI-generated data fit in, and where privacy and security concerns can become competitive moats. And when Julie asks when AI might produce a serious new competitor to today’s dominant electronic health record companies, Tom predicts: within one to two years.

[Source](https://mgln.ai/e/1344/afp-848985-injected.calisto.simplecastaudio.com/d1df597a-30d8-4cae-bb4c-22a8ec496e6d/episodes/744c6b9f-a3a1-4ac3-89f6-80ea9336212c/audio/128/default.mp3?aid=rss_feed&awCollectionId=d1df597a-30d8-4cae-bb4c-22a8ec496e6d&awEpisodeId=744c6b9f-a3a1-4ac3-89f6-80ea9336212c&feed=BXDamaKF)

中文简报

美卫生IT主管基恩称AI对手有望打破电子病历寡头垄断 国家协调员汤姆·基恩预测,随着联邦监管机构破除认证壁垒并对数据囤积行为施加处罚,人工智能将在两年内催生能够直接挑战根深蒂固的急救护理电子病历供应商的竞争者。 汤姆·基恩博士详细阐述了联邦健康IT政策的演变,解释了早期的《高科技法案》(HITECH)激励措施如何无意中助长了封闭的医院电子病历(EHR)寡头垄断,以及随后的《21世纪治愈法案》相关法规如何旨在将数据管理权交还给患者。他强调了国家卫生信息技术协调员办公室(ONC)当前的转变,即通过标准化的面向患者API、在全国范围内推广TEFCA,以及简化如废除无效AI模型卡要求以减轻新进入者合规负担的HTI-6等规则,来充当开放平台的构建者。基恩还详细介绍了联邦机构用于监管伪装成安全考量的信息阻碍行为的具体诊断测试手段。最终,他预测开放API、氛围编程(vibe coding)与生成式AI的结合,将在短短一到两年内催生足以抗衡在位EHR巨头的可行挑战者。 国家卫生信息技术协调员汤姆·基恩博士预测,在生成式AI和氛围编程(vibe coding)的推动下,短短一到两年内就会出现一个有活力的新竞争对手,打破根深蒂固的急救护理EHR寡头垄断局面。 (31:25) 在公开文件显示市场采用率几乎为零(甲骨文报告每月约2次查询,Epic约50次)后,ONC正提议取消认证AI透明度“模型卡”的要求。 (20:00) TEFCA作为健康数据交换的国家公共事业网络,累计交易量已扩大到约17亿次,目前每月处理约2亿次交易。 (10:00) ONC正与美国卫生与公众服务部监察长办公室、联邦贸易委员会及司法部合作,积极监管在位企业的数据限制举措究竟是合理的安全关切,还是伪装成合规要求的竞争壁垒。 (25:00)

Reading summary

The Office of the National Coordinator for Health IT is shifting focus from subsidizing electronic health record adoption to dismantling incumbent data monopolies through open APIs, nationwide exchange rails, and streamlined rules. National Coordinator Dr. Tom Keane forecasts that these regulatory tailwinds and generative AI will produce direct competitors to entrenched EHR incumbents within one to two years. From Subsidized Digitization to Market Consolidation (4:47) Federal health IT policy began with a 2004 executive order setting a 10-year EHR adoption target, but hospital uptake languished around 15% through 2010. By contrast, Picture Archiving and Communication Systems (PACS) reached near-universal penetration between 1989 and 2000 without subsidies because digital imaging offered organic clinical utility and economic returns. Widespread EHR adoption occurred only after the 2009 HITECH Act injected $30 billion in incentives, pushing hospital adoption past 90% by 2015. Keane notes that this rapid transition created major structural failures. Purchasing decisions were directed by hospital executives focused on billing, coding, and revenue cycle management rather than clinical usability. Consequently, an oligopoly of four to five vendors captured 90% to 95% of the acute care hospital landscape, siloing proprietary data. In response, Congress passed the bipartisan 21st Century Cures Act of 2016 to outlaw information blocking and mandate that clinical data follow the patient. Standardized Rails: APIs, TEFCA, and Anti-Hoarding (10:00) To transition from certifying closed software modules to operating as an open platform builder, ONC established three core pillars. Under the 2020 Cures Act final rule, certified EHRs must expose standardized, patient-facing APIs, enabling third-party applications to extract clinical records with verified patient permission. The agency also operationalized the Trusted Exchange Framework and Common Agreement (TEFCA), establishing a single technical framework and legal agreement to replace fragmented institutional contracts. TEFCA processes roughly 200 million transactions monthly, with cumulative volume reaching 1.7 billion. These technical frameworks are reinforced by enforceable information blocking rules that penalize anticompetitive data hoarding. While commercial firms in other sectors can monetize proprietary data for competitive advantage, Keane stresses that healthcare information legally belongs to the patient and must move at their direction. Analogous to the late-1970s push for the SWIFT banking network, public policy is being deployed to drive private healthcare institutions onto common interoperable rails. Deregulation and Retiring Ineffective AI Mandates (20:00) As health data expands into continuous wearables, patient portals, and direct-to-consumer biomarkers, ONC is updating its frameworks in upcoming rules like HTI-6. Keane argues that the patient is the only lifelong constant across fragmented payer and provider networks. The agency plans to standardize external device data into clinical observations that artificial intelligence agents can query, while establishing execution traces to monitor post-market AI model drift. Concurrently, ONC is dialing back certification requirements to lower barriers for startups utilizing modern software development practices. A key deregulatory example is the proposed removal of the certified AI transparency 'model card' requirement that took effect in January 2025. Keane explains the mandate failed in practice: enterprise buyers preferred private NDAs to protect proprietary IP; rigid requirements for 31 source attributes proved impractical; developers evaded rules by hosting standalone tools outside certified EHR boundaries; cards lacked authentic audit backing; and actual EHR market utilization was negligible, with Oracle receiving roughly 2 queries per month and Epic around 50. Policing Anticompetitive Moats and Market Timelines (25:00) While incumbent health IT vendors often cite patient privacy, cybersecurity, and liability concerns to restrict third-party data exchange, Keane asserts regulators actively distinguish legitimate security issues from competitive moats masquerading as safety protocols. Working with the HHS Office of Inspector General, the Federal Trade Commission, and the Department of Justice, ONC screens for bad-faith friction using objective criteria: whether vendors grant favorable onboarding to internal corporate affiliates, publish transparent API terms and market-rate pricing, commit to bounded integration timelines, and maintain parity across multi-vendor implementations. Over the next six months, the agency plans to finalize its HTI-5 rule to reduce market entry friction, refine information blocking definitions, and scale TEFCA reliability. Supported by open infrastructure and generative AI tools that accelerate software development, Keane predicts that a viable market contender capable of challenging the dominant acute care EHR oligopoly will emerge within one to two years. While ONC aims to dismantle incumbent moats through deregulation, API mandates, and inter-agency enforcement, the projection that a viable acute care EHR challenger will emerge within one to two years remains an ambitious forecast, subject to whether health systems are willing to abandon deeply embedded enterprise software.

精炼阅读摘要

美国国家卫生信息技术协调员Tom Keane博士指出,随着生成式人工智能和开放API的成熟,医疗数据的主导权正从医院封闭系统转向以患者为核心。监管机构正通过削减认证负担和严打信息屏蔽,推动市场在未来一到两年内出现挑战传统电子健康档案(EHR)寡头的新进入者。 从全面数字化到打破EHR寡头壁垒 (0:00) 过去十五年间,医疗行业投入数百亿美元完成了从纸质病历向电子化的过渡。在2004年布什总统签署行政令后,EHR的普及一度陷入停滞;直到2009年奥巴马签署《HITECH法案》注入300亿美元直接补贴,医院采纳率才从2010年的约15%飙升至2015年的90%以上。然而,这一轮由医院高管主导的采购潮带来了严重的结构性失衡:软件过度倾斜于计费与编码,并迅速形成了4到5家巨头控制90%至95%急诊医疗市场的寡头格局。 针对数据孤岛和临床负担,美国国会于2016年通过了《21世纪治愈法案》,确立了禁止信息屏蔽和促进数据流动的法定要求。Keane博士强调,与谷歌或房地产企业拥有搜索或租售数据不同,医疗信息在法律上属于患者,必须依照患者意愿自由流动。ONC的角色也由最初设定软件合格线,转变为搭建开放监管平台的建设者,通过开放API和国家级交换框架,确保临床数据能跟随患者进入第三方应用及新兴的人工智能代理。 全国互操作基础设施:API与TEFCA (10:00) 为了消除机构间的数据壁垒,ONC推行了三大核心政策支柱。首先,根据2020年治愈法案最终规则,所有经认证的EHR必须开放标准化的面向患者API,允许第三方应用程序在患者授权与身份验证下安全调取数据。其次,ONC落地了《可信交换框架与通用协议》(TEFCA),通过单一的国家技术框架和协议基准,解决此前因各机构对HIPAA责任和隐私过度担忧而产生的法律摩擦;目前TEFCA已累计处理约17亿笔交易,每月处理量约2亿笔。 第三项支柱是信息屏蔽规则的法定化与执行。监管部门通过明确保留数据的合理豁免场景,界定并禁止反竞争性质的恶意囤积数据行为。这套基础设施不仅保障了传统医疗记录的流转,也为可穿戴设备和生物标志物等非传统健康数据的双向交互铺平了道路,以解决患者因频繁更换保险或雇主而导致的数据断层与健康投资失衡。 监管松绑与废除AI模型卡 (20:00) 面对软件开发范式转向“氛围编码”(vibe coding)的现状,Keane博士指出,初创团队有望在短短一到两年内开发出具备记录系统功能的新型应用,过时的繁琐认证可能扼杀创新。因此,ONC正在重新评估并缩减认证项目范围,拟于秋季发布的HTI-6规则将聚焦于互操作性,同时重点建立临床自主AI操作的溯源、审计与执行追踪机制,以防范模型漂移。 作为监管松绑的典型例证,ONC提议废除自2025年1月1日起强制执行的AI透明度“模型卡”要求。市场实践显示该政策存在严重设计缺陷:商业买家更倾向于通过双边保密协议核验核心技术;强制的31项静态属性过于繁琐;开发者只需将AI模块置于认证系统之外即可绕开监管;实际使用量极度低迷(如Epic全客户每月仅约50次查询,Oracle仅约2次);且这些模型卡缺乏实际审查与审计支持,沦为毫无保障的形式化标签。 识破以安全为名的壁垒与跨部门执法 (25:00) 在推动开放集成的过程中,现有巨头常以保护患者隐私和网络安全为由限制数据访问。Keane博士明确表示,监管机构已设立多项具体基准,用于甄别这些阻力究竟是合理的技术安全诉求,还是伪装成合规考量的反竞争护城河。核查指标包括:数据持有方是否给予内部关联公司更低的接入门槛或更快的对接进度;商业API的条款与收费是否透明且符合公允市场标准;对接开发周期是否具备明确的截止节点;以及第三方软件是否在多数系统运行顺畅却唯独被少数厂商无限期拖延。 Keane指出,市场上约90%的接入摩擦属于可通过技术协调解决的常规问题,ONC正保持开放沟通以促成改进。但对于持续的恶意拖延,ONC正与卫生与公众服务部监察长办公室(OIG)、联邦贸易委员会(FTC)及司法部(DOJ)展开多部门联合执法,以确保国会立法的严肃执行,并在未来六个月内完成HTI-5规则的最终敲定及信息屏蔽规则的细化。 基于人工智能与开放数据基础架构的飞速演进,Keane博士给出了一个激进的市场预测:现有的急诊EHR寡头格局将在短短一到两年内迎来具备实质竞争力的挑战者。然而,这一预测能否实现,仍高度取决于监管机构能否在联合执法中彻底破除传统厂商的信息屏障,以及新生代技术方案在面临复杂医疗安全风险时的实际可靠性。

Detailed notes — zh

## Background 本期内容由 a16z 投资人 Julie Yoo 与 Colin Rom 联合主持,发布于播客平台(2026年10月29日上线,时长 34 分 22 秒)。节目邀请到美国国家卫生信息技术协调员(National Coordinator for Health IT)Tom Keane 博士,围绕医疗行业经历 15 年病历数字化后的新阶段展开讨论,重点聚焦开放 API、TEFCA 互操作性网络、AI 与可穿戴数据融合,以及降低新入局者准入门槛等议题。 ## TL;DR 对话深入探讨了美国医疗 IT 底层逻辑的深刻演变:行业重心已从最初依靠数十亿美元财政补贴强推的“病历数字化”,转向全面打破数据孤岛与推进互操作性。面对传统 EHR 巨头形成的“计费系统”寡头垄断,监管部门正通过强制开放面向患者的 API、扩建 TEFCA 全国交换网络以及严查信息阻碍(Information Blocking)来赋能患者与创新应用。针对 AI 时代的到来,ONC 积极调整监管策略,提议废除脱离实际的“模型卡”认证负担,并加速推进 HTI 新规以整合院外可穿戴设备数据。针对急诊与住院 EHR 市场的破局点,Tom Keane 大胆断言,在生成式 AI 与高效率开发工具驱动下,市场将在 1 至 2 年内迎来真正颠覆传统巨头的新一代竞争者。 ## Atmosphere & style 整场对话兼具专业严谨的政策深度与硅谷科技对话的前沿锐气,节奏明快且信息密度极高。Tom Keane 凭借其工程师、一线执业医生与联邦高官的罕见跨界背景,在阐述复杂的法规机制时表现得务实而幽默,不仅生动回顾了 UIUC 早期研读 Mosaic 源码的往事,还毫不避讳地直击传统巨头以隐私为名构筑竞争壁垒的现实痛点。主持团队与嘉宾之间展现出强烈的行业共鸣与投融圈的敏锐互动,尤其在对谈尾声针对“何时打破 EHR 寡头”抛出犀利提问时,嘉宾果断给出 1 到 2 年的激进预测,将全场务实探讨推向充满期待的高潮。 ## Bulletin - `31:18` 美国国家卫生信息技术协调员 Tom Keane 预测,在 AI 与“氛围编程”(Vibe Coding)工具的驱动下,全美急重症电子病历(EHR)市场将在 1 至 2 年内迎来打破现有寡头垄断的新兴竞争者。 - `10:00` 全美医疗数据基础设施 TEFCA(可信赖交换框架与通用协议)累计交易量已突破 17 亿笔,当前月处理量达 2 亿笔,正朝着 100% 可用性的国家级骨干网络演进。 - `21:18` ONC 提议废除原定于 2025 年强制生效的 AI 模型卡(Model Cards)要求,指出其静态指标缺乏实地审计、使用率极低(Epic 月均仅约 50 次查询,Oracle 仅约 2 次)且易产生虚假安全感。 - `15:00` 即将出台的 HTI-6 规则将监管重心从医院内部临床记录扩展至消费级穿戴设备与院外非临床数据,旨在确立患者为自身数据的终极管理者,并建立 AI 与传统 EHR 之间的双向通信通路。 ## Key takeaways - `00:00` 全美医疗信息化历经数十年和数百亿美元投入完成数字化后,当前核心瓶颈已转向信息流动的信任与规模化问题,监管重心全面转向开放 API 与互操作性。 - `04:20` 相比依靠临床与降本内生需求在十年内自发普及的 PACS 影像系统,早期电子病历推进极其迟缓,直至 2009 年《高科技法案》(HITECH)注入 300 亿美元补贴才驱动医院普及率在 2015 年跃升至 90%。 - `06:40` 早期 EHR 采购由医院行政与财务高层主导,导致产品被设计为高度偏向计费与编码的工具,不仅加重了临床医生负担,更由四至五家巨头瓜分并形成了封闭的数据孤岛。 - `06:40` 医疗数据不同于商业搜索或地产数据,它在法律与伦理上均归患者所有,必须依照患者本人的意愿流动,并为了患者的直接健康利益服务。 - `10:00` ONC 奠定了推动数据互联的三大支柱:强制要求 EHR 提供面向患者的标准开放 API、建立 TEFCA 全国交换网络,以及严厉落地反信息阻碍(Information Blocking)规则。 - `10:00` 医疗行业长期因极度担忧触犯 HIPAA 等合规风险而过度防范协作,TEFCA 借助单一全国性法律协议和 QHIN 架构从制度上化解了信任缺失和阻断痛点。 - `15:00` 由于患者频繁更换雇主与医保,传统体系存在改善患者健康者无法享受长期回报的激励错位;唯有确立患者自身作为全生命周期健康数据的管理者,才能彻底解决这一痛点。 - `15:00` 医疗监管规则正主动适应数据向院外迁移的现实,未来的关键是解决穿戴设备数据的不一致性,并打通系统智能(SI)与传统临床 EHR 之间的双向赋能管道。 - `20:00` ONC 正在定稿的互操作性新规开启了重大政策转向:将监管重点从 EHR 繁重的“基础功能认证”全面移向“互联互通性”,为新兴技术产品大幅减负。 - `21:18` 强制 AI 模型卡机制被叫停,主要因其在商业采购中可被保密协议替代、静态 31 项指标备受争议、导致应用脱离 EHR 以规避监管,且从未经过真实审计。 - `21:18` 在“氛围编程”(Vibe Coding)时代,开发者仅需一到两年便能搭建出新系统,监管团队正致力于打破昂贵的合规认证门槛,防止繁冗政策扼杀潜在竞争者。 - `24:45` 针对老牌 EHR 巨头将安全和隐私作为竞争护城河的现象,ONC 联合 OIG、FTC 和 DOJ 设立了严格的审查机制,重点排查关联方优待、不合理的接口收费与刻意拖延接入排期。 - `27:10` 行业内 90% 的数据流通摩擦属于技术标准未统一或正常流程磨合,Tom Keane 呼吁创业者通过信息阻断门户反馈痛点,监管机构将优先作为“协调员”推动厂商主动修正。 - `30:00` 未来半年的监管工作重点包括正式敲定 HTI-5 规则、细化反信息屏蔽执法规章,并持续扩大 TEFCA 网络的应用场景与可靠性。 - `31:18` Tom Keane 大胆预测,在人工智能与系统智能浪潮的冲击下,急重症医疗 EHR 领域根深蒂固的寡头垄断格局将在未来 1 至 2 年内迎来实质性的新生挑战者。 ## Detailed walkthrough ### `00:00` 医疗数据的下一阶段:从电子病历普及走向互操作性与 AI 竞争 在全美医疗系统花费数十年与数十亿美元完成病历数字化之后,整个行业正迎来关键转折点。本期节目由 a16z 合伙人 Julie Yoo 和 Colin Rom 主持,邀请到美国国家卫生信息技术协调员(National Coordinator for Health IT)Tom Keane 博士,深入探讨全美医疗技术底层的架构演变,以及为何当前的核心任务已从“数字化”转向“数据流通与互操作性”。 Keane 明确指出医疗数据流动中面临的现实瓶颈:“Constraints around how information is shared create real problems with trust, with scale, with security.”(围绕信息共享方式的各种限制,在信任度、规模化以及安全性方面造成了极为真实的痛点。)他进一步警告称,缺乏明晰的规则会导致大家因顾虑而裹足不前,无法充分释放数据的全部潜能。因此,美国国家卫生信息技术协调员办公室(ONC)正致力于推广面向患者的开放 API 与 TEFCA 等框架,推动患者真正掌控自己的健康信息。 对谈中,Julie 抛出了一个核心行业痛点:当今急症护理(acute care)电子病历(EHR)市场被少数寡头牢牢占据,AI 技术究竟何时才能孕育出有力的挑战者来打破这种垄断局面?针对这一问题,Keane 给出断言:“Tom's prediction, within one to two years.”(Tom 预测,就在一到两年之内。) ### `02:18` 跨界工程师的轨迹:从伊利诺伊大学的 Mosaic 源码到执掌 ONC Julie 介绍了 Keane 兼具工程师、一线临床医生与资深政府官员的复合背景,戏称他为医疗科技圈罕见的“独角兽”。Keane 幽默回应称,这段丰富履历往往容易让人觉得自己“年纪很大”。大学工科毕业后,他当了五年工程师,才下定决心报考医学院。在完成临床医学训练并执业长达 15 年之后,他在一线深切体会到医疗实践中的繁琐阻碍与系统性摩擦,因而决定投身公共服务,代表医生与患者发声,并最终接掌 ONC。 谈及早年在伊利诺伊大学厄巴纳-香槟分校(UIUC)的工程学院求学经历,Keane 确认自己与 Netscape 联合创始人 Marc Andreessen 是校友——Andreessen 于 1993 年毕业,他于 1994 年毕业。1993 年 3 月,Andreessen 与 Eric Bina 发布了 Mosaic 网页浏览器,并在校内一鸣惊人。Keane 回忆自己曾特意前去查看公布的名单,并研读了最早的 Mosaic 源代码,看到 Andreessen 在每一处代码注释下方署名“Marca”。他直言,当年身处那座诞生了首个商用可行浏览器的工程学院,空气中确实弥漫着一种技术变革的气息。 ```mermaid flowchart TD accTitle: Tom Keane 职业转型历程 accDescr: 展示 Tom Keane 从工程背景到临床医生再到公共卫生技术决策者的演进路径 subgraph Phase1 ["早期工程阶段"] A["工科学位 (UIUC 1994)"] --> B["从事工程工作 5 年"] end subgraph Phase2 ["临床医学实践"] B --> C["考入医学院并获医学学位"] C --> D["一线行医 15 年<br/>(深感系统摩擦与流程负担)"] end subgraph Phase3 ["政府公共服务"] D --> E["加入 ONC 代表医患发声"] E --> F["出任国家卫生信息技术协调员<br/>(National Coordinator)"] end ``` ### `04:20` ONC 的起源与演进:从布什时期的行政令到 300 亿美元的 HITECH 法案 谈及 ONC 的职责与沿革,Keane 解释其全称为技术政策助理部长兼国家卫生信息技术协调员,这曾让他享有“全联邦政府最长头衔”的称号,直到后续组织架构重组才予以精简。ONC 的核心职责在于统筹全美的卫生信息技术与健康信息交换。 该机构最早由布什总统于 2004 年通过行政命令设立,当时设定的宏伟蓝图是让全美所有医院在 10 年内普及电子病历。然而在 2004 至 2010 年间,由于缺乏经济激励,全美 EHR 的采纳进展极其缓慢。Keane 将其与医疗影像存储与传输系统(PACS)的成功普及做了鲜明对照: - **PACS 系统的市场化普及**:1989 年马里兰大学率先采用第一套 PACS 系统,没有任何政府补贴或强制法令,仅仅依靠医院对利润提升、流程互通与诊疗改进的内生需求,到 2000 年全美医院便几乎实现了 100% 的普及。 - **EHR 推进的制度困境**:电子病历在早期缺乏类似的内生动力,导致布什政府时期的前六年收效甚微。 转折发生在 2009 年。奥巴马总统签署了《高科技法案》(HITECH Act),不仅强制医院采用电子病历,还设立了高达 300 亿美元的专项激励资金。Keane 强调,当时美国国立卫生研究院(NIH)的全年总预算也仅为 300 亿美元,足见联邦政府对 EHR 扶持力度之大。在法案的强力驱动下,全美医院和医疗机构的 EHR 普及率在 2010 至 2015 年间从约 15% 激增至 90%。在此期间,ONC 的核心使命是规范资金用途、架构推行方案,并为技术产品确立质量底线,防止劣质系统滥竽充数。 ### `06:40` 市场失灵催生《21 世纪治愈法案》:从“计费孤岛”到患者数据赋能 伴随 EHR 的爆炸式增长,市场在 2015 至 2016 年左右暴露出了两大严重扭曲: 1. **产品定位严重偏向计费**:购买系统的主导者是医院的 CEO 和 CFO,导致产品核心设计围绕账单出具和代码计费(billing and coding)展开,极不注重用户体验,不仅未给一线临床医生减负,也没有给患者带来实质获益。 2. **寡头垄断与数据孤岛**:全美 90% 到 95% 的市场被四至五家主要 EHR 巨头瓜分,这些厂商将所有临床数据牢牢锁死在各自的封闭系统内。 为扭转这一局面,美国国会在 2016 年以压倒性多数通过了《21 世纪治愈法案》(Cures Act),明确了两大硬性目标:切实减轻临床医护人员的系统操作负担,以及强制推行数据共享。Keane 对此阐述了医疗数据不同于商业数据的特殊本质: - 商业巨头(如 Google)收集用户的搜索历史,没有任何义务向外部公开共享,可以作为自身商业变现的护城河。 - 地产公司掌握房屋租售价格数据,同样可以将其作为独家资产出售并建立竞争壁垒。 - “Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient.”(信息属于患者本人,必须在患者的授意下流动,并为了患者的利益而流动。) Keane 指出,自 2016 年至今的阶段,ONC 的核心任务就是推动互操作性。他希望在自己的任期内将 ONC 定位为一个“平台构建者”(platform builder),让医疗数据流动起来,驱动成本降低并改善诊疗结果,营造一个能孕育出上千种优质应用、让患者赋能技术百花齐放的创新生态。对谈最后,Julie 提问政府当年采取天价财政补贴来推广特定单一软件类别是否有历史先例;Keane 回顾道,这在现代商业中极不寻常,但勉强可以类比 1970 年代末联邦政府为了推动银行业高效交换数据而主导确立的 SWIFT 金融结算系统。 ### `10:00` 从打破数据寡头到确立规则:ONC 推动医疗互联的三大支柱 医疗数字化的开端不仅是一场技术演进,更是一场深刻的制度重塑。早期的国家级系统(如空中交通管制)往往依赖政府制定标准以达成全国规模,但医疗信息化的独特性在于政府配套了庞大的财政激励措施以推动普及。在奥巴马总统及其经济顾问乔纳森·格鲁伯(Jonathan Gruber)等政府官员的构想中,医疗数字化能让系统得到更好的管理,从而降低成本并提高医疗质量。然而,行业随后达成了另一个至关重要的共识:数据必须能够流动与共享。大量的医疗利益相关方强烈主张,医疗数据最终归患者所有,必须为了患者的利益而流动。这促成了国会层面的密集游说,明确反对少数几家技术过硬且初衷良好的领军企业形成事实上的寡头垄断;行业共识认为,任何机构都不应扣押患者数据,否则将对患者造成实质性伤害。 面对主持人关于国家卫生信息技术协调员办公室(ONC)有哪些常被低估的成就的提问,汤姆(Tom Keane)风趣地回应称:“我倒觉得我们的成就没一项是被低估的,至少我的不是(Well, I'd like to think none of our accomplishments are underrated. At least mine's not.)。”他系统性地阐述了 ONC 为初创企业、建设者和患者奠定的三大支柱: 第一是《21世纪治愈法案》最终规则(2020 Cures Act final rule)中强制要求所有电子健康档案(EHR)必须开放面向患者的应用程序编程接口(API)。该规则确立了严格的技术标准与安全态势,明确只要获得患者的有效授权与身份核验,任何合规应用都可以接入并调取患者的数据。 第二是建立名为 TEFCA(可信赖交换框架与通用协议)的全国性网络。在医疗行业,信任与避免伤害是所有从业者的核心底线,甚至导致许多过度防范的怪象。例如,在肿瘤等科室,医护人员向离世患者家属寄送慰问卡本是通行的人文关怀,但一些顶尖的大型医疗系统因极度担忧触犯 HIPAA 隐私条款,竟专门向监管机构致电请求书面澄清是否可以寄卡。此外,在向保险公司提供账单数据以获取赔付时,也存在“最小必要”(minimum necessary)的标准限制。这种由于信任不足、隐私担忧和合规风险造成的壁垒,严重阻碍了市场的规模化协作。为了打破这种割裂,ONC 依据 2016 年法案的授权,通过单一全国性法律协议和 QHIN(合格健康信息网络)技术框架,搭建起统一的交换机制。 第三是全面落地反信息阻碍(Information Blocking)规则及法定例外。ONC 既划定了禁止恶意阻断数据流动的红线,又明确了确保隐私与网络安全的正当例外情形,并联合其他政府监管部门展开实质性执法,向整个市场确立了清晰的合规预期。 ```mermaid flowchart TD accTitle: ONC推动医疗数据互联互通的核心支柱 accDescr: 展示ONC通过开放API、TEFCA网络和反信息阻碍规则打破EHR寡头并连接患者与创新应用的架构。 subgraph Regulation["政策与法规基石"] CA["21世纪治愈法案与最终规则"] IB["反信息阻碍规则与合规例外"] end subgraph Infrastructure["国家级互联互通体系"] API["标准化面向患者开放 API"] TEFCA["TEFCA 全国网络 (QHIN 框架)"] end subgraph Beneficiaries["数据流动终端"] Patients["患者与第三方应用生态"] Providers["医疗机构与保险支付网络"] end CA --> API CA --> TEFCA IB --> Providers API --> Patients TEFCA --> Providers Providers <-->|"双向合规调阅"| Patients ``` - **TEFCA 交易规模**:截至当前,TEFCA 网络已累计处理约 17 亿笔交易,每月处理量稳定在约 2 亿笔,目标是建设成为可用性达到 100% 的坚固国家级基础设施。 - **患者数据所有权**:汤姆特别引述当时游说国会的核心论点指出:“这不能变成由少数几家虽说出于善意且表现成功的公司所把持的寡头垄断(look, this cannot be an oligopoly of a handful of truthfully well-intentioned and successful companies)。” --- ### `15:00` 突破传统 EHR 边界:穿戴设备、HTI-6 规则与双向流动的 AI 医疗新生态 针对当前的技术生态,朱莉(Julie Yoo)指出,医疗实际上是极少数通过明确监管规则来积极支持技术和 AI 健康发展的行业。监管机构强制推行开放 API 和 MCP(模型上下文协议)等能力,为技术创业者提供了巨大的制度红利,证明了监管正在紧跟技术发展的步伐。然而,当前的监管焦点仍局限于传统急救与门诊机构的临床 EHR 记录。与此同时,消费者可穿戴设备、聊天健康记录、新型生物标志物检测等大量院外非临床支付轨道的数据正迎来爆发式增长。如果在该领域缺乏明确的数据规范,创业者可能会因为害怕未来的追溯性监管而不敢放开手脚,甚至可能在投入巨资后遭遇推倒重来的合规打击。 汤姆对此正面回应,确认 ONC 正在制定的 HTI-6 规则已列入联邦统一议程(Unified Agenda),其核心目标正是打破传统“认证卫生 IT”与 EHR 的狭隘边界,主动适应患者护理与健康数据向院外大规模迁移的现实。汤姆非常赞同朱莉此前发表的一篇观点文章,该文深刻探讨了医疗体系中“谁改善了患者健康,谁却往往享受不到长期经济回报”这一激励错位的“原罪”——因为患者会频繁更换雇主、医保计划与就诊医院。 汤姆强调,要化解这种错位,唯一的路径是确立患者自身作为其全生命周期健康数据的“终极管理者”(ultimate steward)。不论患者更换哪家雇主或医保方案,由患者主导的软件或其与私人医生绑定的纵向智能工具,都将长期对患者的健康负责并直接受益。为了支撑这一愿景,未来的监管框架必须覆盖消费级穿戴设备与院外数据: 1. **数据标准化与一致性**:解决穿戴设备数据口径混乱的现状。正如汤姆指出的现实困境,用户在左右手腕分别佩戴两款不同手环时,测出的生理指标往往并不一致,因此必须将其标准化为可被医疗系统理解的结构化观测值(structured observations)。 2. **AI 与传统系统的双向互动(Two-Way Communication)**:未来的医疗 AI(以及系统智能 SI)绝不能是单向调取数据的寄生工具。当 AI 发现患者健康恶化或给出关键照护指导时,必须有标准通路将这些结论反哺回传统临床 EHR 系统;反之,EHR 的深厚临床数据也将让 AI 具备更强的洞察力。 3. **AI 充当患者代理人(Agent)**:随着 AI 演进为真正代表患者自主行事的数字代理人,两套系统之间的数据壁垒必须在法律与技术层面被彻底打通。 在谈到这种共生架构时,汤姆明确断言:“当系统智能被传统医疗系统产生的数据所赋能时,它会变得更加强大;同样地,随着数据从系统智能流向传统医疗系统,传统医疗系统也将获得同等程度的赋能(SI is more powerful when it's empowered with data that is generated by the traditional healthcare system. And the traditional healthcare system will be empowered similarly by that data moving from SI into the traditional healthcare system)。” ### `20:00` 重新定义电子病历:从基础功能认证转向互联互通 国家卫生信息技术协调员(National Coordinator for Health IT)Tom Keane 博士首先阐述了监管机构在应对医疗人工智能发展时的核心思路:必须建立某种机制来追踪 AI 行为的溯源(Provenance)、进行行为审计,并在上市后开展持续监控(Post-market monitoring),以防止算法发生模型漂移(Drift)。这一系列构想正在融入即将推出的后续规则制定工作中,他们希望在今年秋季正式推出新的 HTI(Health and Human Services Interoperability)规则。Tom 坦言,此前医疗行业面临的层层摩擦是医疗数据发展的“原罪”,而监管机构正在通过标准建设和政策制定来推动解决这一痛点。 Julie Yoo 随即从创业者的视角切入,指出当下的行业认知正在发生根本性转移。过去,电子病历(EHR)被狭隘地定义为医院和诊所内部记录临床数据与处理计费功能的“记录系统”(System of Record)。然而,随着数据重心以及患者体验大规模向医院和诊所的高墙之外转移,EHR 的基本概念正在被彻底重塑。针对这一演变,Tom 透露正在定稿的 HTI 新规做出了重大政策转向:监管重点正从电子病历的“基础功能”全面转向“互联互通性”(Interoperability),并大幅缩减现有的技术认证计划。 --- ### `21:18` 废除 AI“模型卡”要求:监管减负与“Vibe Coding”时代的市场准入 在解释认证项目的大幅松绑时,Tom 详述了他们提议取消 AI 透明度“模型卡”(Model Cards)强制要求的全过程。这项原定于 2025 年 1 月 1 日开始强制执行的规定,在落地后迅速收到反馈,暴露出脱离实际的多重弊端。Tom Keane 明确解释了废除该规定的核心原因:“我们发现,这项实际上于2025年1月1日生效执法的提案,其实并不能很好地契合实际目的。” ```mermaid flowchart TD accTitle: AI模型卡监管失效原因 accDescr: 分析强制AI模型卡在医疗实践中失效的四大核心原因及监管应对 subgraph Problems["模型卡机制的现实缺陷"] P1["信息获取冗余:医院采购可签署NDA,无需公开模型卡"] P2["静态31项指标不符实情:业界对字段数量争议巨大"] P3["监管盲区:第三方AI应用移出EHR以规避认证管辖"] P4["极度缺乏使用:Oracle仅2次/月,Epic约50次/月"] end subgraph Risk["最大的临床隐患"] R1["缺乏真实审计机制:沦为毫无背书的“虚假合格标签”"] end subgraph Solution["监管转向"] S1["提议彻底废除强制模型卡"] S2["大幅降低认证负担,鼓励Vibe Coding新玩家入局"] end Problems --> Risk Risk --> Solution ``` Tom 从医生和监管者的双重视角逐条剖析了模型卡的失败原因: 1. **商业采购已有成熟替代方案**:如果医院医生要采购 AI,若相关参数属于非公开的专有算法或核心商业机密(Secret sauce),双方完全可以在保密协议(NDA)下进行披露,无需挂在公共模型卡上供所有人查阅。 2. **静态指标死板且备受争议**:官方最初规定的 31 项数据来源属性(Source attributes)属于静态数据集,规则刚推出就引来强烈反弹,业界普遍抱怨选错了这 31 项,或者认为只需保留 5 项核心指标。 3. **催生监管套利行为**:该规则仅适用于“已认证的健康 IT 系统”。如果开发者直接在 EHR 之外启动独立的独立应用程序,监管机构便无权管辖,这导致大量创新 AI 应用为了避开繁琐监管,主动选择脱离 EHR 体系。 4. **实际使用率极低**:在公开的意见征集信中,Oracle 透露其系统每月关于模型卡的查询仅有大约 2 次;而 Epic 方面的反馈显示,全系统每月也仅有大约 50 次查询。 5. **带来虚假的安全感**:Tom Keane 强调:“作为一名医生,最令我担忧的是它带来了一种虚假的安全感。”官方从未对模型卡上声称的内容进行实地审计,系统本身也不具备审计功能,这使得模型卡沦为了一个缺乏实质背书与保证的“合规贴纸”。 鉴于此,监管团队提议将其移除。Tom 指出,这一系列调整的终极目标是降低市场准入门槛。在如今人人都谈论“氛围编程”(Vibe Coding)的人工智能时代,开发者依靠高效工具只需一到两年就能搭建出一套新的电子病历或核心记录系统,监管机构绝不能用昂贵沉重的认证程序扼杀潜在竞争。听到这一立场,Julie Yoo 由衷赞同并感叹:“为更多竞争和去监管喝彩。” --- ### `24:45` 数据防线还是竞争护城河?信息阻碍与既得利益者的博弈 Julie Yoo 进一步把话题引向传统老牌巨头与新入局者之间的摩擦。在数据互联互通领域,新创业公司经常抱怨获取底层数据面临重重关卡;而老牌厂商(如 Epic、Oracle 等)则坚称,自己对保障患者数据安全和隐私负有重大责任,因此在开放数据访问权限时必须保持谨慎保守的姿态。尽管 Julie 承认,如今创业者调取 EHR 数据的难度已经比她 15 年前创业时“容易了一百倍”,但这种摩擦依然真切存在。 面对这种拉锯,Tom 指出这永远是一个动态平衡的过程——随着技术发展,身份认证、鉴权与安全标准会提升,但量子计算和复杂 AI 也会带来新的隐私与安全风险。然而在实际执法中,监管机构绝不容忍巨头以此为托词阻碍竞争。Tom Keane 直言,监管核心在于:“评估市场参与者所遇到的阻碍,究竟是出于正当的隐私和安全顾虑,还是披着隐私与安全外衣的竞争护城河。” 为了识别这种伪装,ONC 与监察长办公室(OIG)、联邦贸易委员会(FTC)以及司法部(DOJ)共同制定了一套严密的内部测试标准: - **关联方待遇审查**:数据持有方是否优待其关联实体(Affiliates)?关联方是否能以更低的开发成本、更快地获取健康数据?信息阻断(Information Blocking)法规的核心就是建立公平竞争的赛场。 - **条款与收费合理性**:记录系统是否公开了统一透明的数据访问条款?其收取的接口与服务费用是否符合正常市场价格水平? - **开发周期的明确性**:针对新接入方的技术对接流程是否有明确的截止期限?排期是否符合行业惯例? - **多方对比测试**:某个第三方应用如果已经顺利对接了三家主流厂商,唯独在另外两家厂商处遭遇无限拖延,这往往意味着这两家厂商没有履行其在信息阻断法下的法定义务。 --- ### `27:10` 监管者的协调角色与未来展望 Tom Keane 向所有遭遇数据壁垒的技术开发者发出了明确呼吁:请把你们在市场中经历的所有阻力直接反馈给监管机构。他澄清道,在行业遭遇的各种数据摩擦中,其实有 90% 只是技术标准尚未统一或正常市场运作流程中的磨合问题,并不涉及恶意封锁。 开发者既可以通过官方的“信息阻断门户”(Information Blocking Portal)提交投诉,也可以直接与他本人联系。Tom 幽默地强调了自己职务的真正含义:“我头衔中的‘C’代表协调员(Coordinator),我们的职责就是与医疗健康市场进行协调。”他在实践中发现,当监管部门介入并在各方之间建立对话通道时,许多传统系统厂商往往会坦言自己此前并未意识到这会带来如此大的困扰,并迅速主动改正行为;只有在确认存在明知故犯的违法违规行为时,监管机构才会采取强硬的执法姿态。因此,他希望创业者在反馈摩擦时,尽量提供尽可能详尽的细节,并且最好同步提出可行的技术或流程解决方案。 Colin Rom 对此表示高度赞赏,并指出 a16z 生态系统内的创始人与投资人对模型卡松绑和互联互通改革感到无比兴奋。随着这届任期即将迈入第二年,Colin 询问 Tom Keane 团队在未来 12 到 18 个月内的最优先事项,以及初创公司创始人该如何更高效地与政策制定者对接互动。 ### `30:00` 监管路线图与多部门执法:降低准入门槛并扩展 TEFCA 谈及机构与整个行业的互动方式时,Tom Keane 博士指出,机构的核心使命就是沟通与协调,他们乐于同各类市场参与者深入交流以探寻问题的解决方案。除了直接与他们对接外,行业从业者还可以参与 CMS 的医疗科技生态系统(Health Tech Ecosystem),目前该平台已聚集了大约 1,700 名参与者,是医疗科技界同行相互交流、共同塑造政策导向以及达成共识解决方案的绝佳平台。 在谈到未来近期的明确目标时,Tom Keane 列举了将在未来六个月内落地的多项关键举措:首先是敲定并出台 HTI-5(健康数据、技术与互操作性规则)以切实降低行业准入门槛;其次是继续完善和细化针对信息屏蔽(Information Blocking)行为的监管规定。与此同时,官方将持续投资于 TEFCA(可信交换框架与通用协议)的全国性基础设施建设,致力于扩大其网络规模、拓展更多实际应用场景,确保其具备 100% 的可靠性,从而成为全行业获取健康信息的切实可行选择。此外,监管部门还将继续保持严格的执法态势。正如 Tom Keane 所强调的那样: > “And between us, the OIG, the FTC, and the DOJ, we believe that we will send a strong signal to the market in a way that everybody can be agreeable to.” ```mermaid flowchart TD accTitle: ONC与跨部门监管推进路径 accDescr: 展示降低准入门槛、基础设施扩展及跨部门联合执法的未来工作布局。 subgraph Policy ["政策与规则制定"] A["敲定 HTI-5 规则<br/>降低新入局者门槛"] --> B["完善信息屏蔽<br/>(Information Blocking) 规章"] end subgraph Infra ["国家基础设施"] C["扩展 TEFCA 网络规模"] --> D["丰富应用场景并<br/>保障 100% 可靠性"] end subgraph Enforcement ["跨部门联合执法网络"] E["ASTP / ONC"] --- F["监察长办公室 (OIG)"] F --- G["联邦贸易委员会 (FTC)"] G --- H["司法部 (DOJ)"] end Policy -.-> Enforcement Infra -.-> Enforcement ``` - **CMS 医疗科技生态网络规模**:已汇聚约 1,700 位行业参与者,共同参与政策探讨与共享解决方案的制定。 - **6 个月近期工作重点**:敲定 HTI-5 规则、持续细化信息屏蔽法规、投资推进 TEFCA 基础设施建设。 - **跨部门协同监管**:与 HHS 监察长办公室(OIG)、联邦贸易委员会(FTC)以及司法部(DOJ)建立协同执法机制,坚决执行国会赋予的法定职责。 --- ### `31:18` 犀利提问:何时能打破急诊与住院 EHR 的寡头垄断? 对谈进入尾声时,Julie Yoo 抛出了一个“犀利的加分问题”(Bonus spicy question)。她指出,Tom 已经详细描绘了如何为创新者敞开大门、促进竞争、推进互操作性与实现流动数据,同时也点出了当前急重症医疗(Acute Care)电子病历(EHR)市场根深蒂固的寡头垄断格局。Julie 追问道:究竟还要多久,市场上才会真正出现能够打破这一寡头垄断的有力竞争者?是 2 年、5 年,还是 10 年?究竟需要满足什么样的前提条件,才能让更多的选手站上 EHR 这一竞技场? 面对这一尖锐问题,Tom Keane 表现得既务实又乐观。他提到自己有机会与市场上所有的参与者保持对话,这其中也包括那些现存的核心记录系统(Systems of Record)厂商。他回顾了自己亲历的技术浪潮:从个人电脑的兴起(他笑称自己经历过那个时代),到互联网的爆发,再到如今人工智能(AI)的演进。在他看来,技术的发展具有颠覆性,而记录系统厂商本身也清楚地意识到了行业地壳的变动。当被要求给出一个具体的时间框架时,Tom Keane 做出了大胆而明确的预测: > “Everybody in the world believes that AI is going to, SI is going to transform the world, and it probably will.” 随后他斩钉截铁地补充道: > “So to be more concrete, one to two years.” 这一预测令 Julie 感到十分惊喜并高度赞同,她表示这一时间节点正是大家最期盼的可能情形。Tom Keane 随即幽默地约定,欢迎节目组在两年后再次邀请他返场,届时大家不仅可以调侃他又老了两岁,更可以一同见证并检验未来全新 EHR 竞技场上那些新兴公司的 CEO 们所取得的突破与成果。 --- ### `33:30` 结语与合规声明 在播客节目的最后,Julie Yoo 代表主持团队向 Tom Keane 博士表达了由衷的感谢,盛赞他在公共服务领域、医疗健康生态构建以及推动 AI 与前沿技术在医疗场景落地中所作出的卓越贡献。Tom Keane 也向两位主持人和听众致谢。 随后播客播送了 standard outro 与免责声明:本期节目属于 a16z 旗下《Raising Health》播客系列,相关内容仅供信息参考,不构成任何法律、商业、税务或投资建议,亦不得用于评估任何投资或证券;内容不对 a16z 旗下任何基金的投资者或潜在投资者定向发布;a16z 及其关联方可能会持有本期节目中所讨论公司的投资头寸。 ## Notable quotes > `06:40` Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient. — Tom Keane > `00:00` Constraints around how information is shared create real problems with trust, with scale, with security. — Tom Keane > `27:10` 我头衔中的‘C’代表协调员(Coordinator),我们的职责就是与医疗健康市场进行协调。 — Tom Keane ## Mentioned Tom Keane, Julie Yoo, Colin Rom, Marc Andreessen, Eric Bina, Jonathan Gruber, George W. Bush, Barack Obama, a16z, ONC, CMS, NIH, HHS OIG, FTC, DOJ, UIUC, Mosaic, Netscape, PACS, HITECH Act, 21st Century Cures Act, TEFCA, QHIN, HIPAA, HTI-5, HTI-6, Oracle, Epic, SWIFT, Raising Health ## Video description Healthcare spent the last 15 years digitizing medical records. Now the challenge is making that data useful to patients, AI agents, and new health technology companies. National Coordinator for Health IT Dr. Tom Keane says the next phase is about interoperability, patient access, and lowering barriers for new entrants. Tom joins a16z’s Julie Yoo and Colin Rom to discuss how healthcare data can move more easily through APIs and TEFCA, how wearables and AI-generated data fit in, and where privacy and security concerns can become competitive moats. And when Julie asks when AI might produce a serious new competitor to today’s dominant electronic health record companies, Tom predicts: within one to two years. [Source](https://mgln.ai/e/1344/afp-848985-injected.calisto.simplecastaudio.com/d1df597a-30d8-4cae-bb4c-22a8ec496e6d/episodes/744c6b9f-a3a1-4ac3-89f6-80ea9336212c/audio/128/default.mp3?aid=rss_feed&awCollectionId=d1df597a-30d8-4cae-bb4c-22a8ec496e6d&awEpisodeId=744c6b9f-a3a1-4ac3-89f6-80ea9336212c&feed=BXDamaKF)

Source quotes

[6:40] Tom Keane: Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient. [0:00] Tom Keane: Constraints around how information is shared create real problems with trust, with scale, with security. [27:10] Tom Keane: 我头衔中的‘C’代表协调员(Coordinator),我们的职责就是与医疗健康市场进行协调。

Source quotes

[4:47] Dr. Tom Keane: Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient. [25:00] Dr. Tom Keane: There are certain ways that we can evaluate whether the frictions that somebody in the market are experiencing are legitimate privacy and security concerns or whether they are competitive moats masquerading as privacy and security concerns.

Original transcript

[0:00] ONC's job is to oversee health information technology and health information exchange. Constraints around how information is shared create real problems with trust, with scale, with security. The risk is in the absence of clear rules about how that data gets treated. There's perhaps a risk that people hold back from leveraging that data to its full extent. to expose a patient-facing application programming interface. Our vision is that the patient will be the ultimate steward of their information and to be able to transform healthcare. You also referred to the oligopoly that exists today in our acute care EHR market. When do you think we will see... a contender enter the playing field to break that oligopoly. Healthcare spent billions of dollars moving from paper to electronic health records. The next challenge is making all of that data actually move. In this episode, A16Z's Julie Yu and Colin Rahm sit down with Dr. Tom Keen, National Coordinator for Health IT, to talk about the infrastructure behind the next era of healthcare technology. Tom explains how the and why the focus has now shifted from digitization to interoperability. That means giving patients greater control of their data, making it easier for new applications and AI agents to interact with healthcare systems, and reducing regulatory barriers for new entrants. They also get into how wearables and AI-generated data should flow back into the traditional healthcare system, why ONC is reconsidering regulations that aren't working as intended, and how the government thinks about privacy and security arguments that can sometimes double as competitive moats. And finally, Julie asks when AI might help produce a serious new competitor to today's dominant electronic health record companies. Tom's prediction, within one to two years. We are so glad to be here with Dr. Tom Keen, National Coordinator for Healthcare IT in the Office of the National Coordinator ONC, and my partner Colin Rahm here as well. And we're going to have a wide sweeping conversation about the state of health tech in America. Let's actually start with your story, Tom. You are a bit of a unicorn. You are an engineer, a clinician, and have spent a significant time in the government. Tell us about your life story and how it came to be that you are sitting in the seat here today. Well, first of all, thank you for having me and thank you for inviting me to do this. And thank you for the implication that having done many things, I'm very old. You're a youthful wife. Yes. So I started out after I graduated from college as an engineer and had considered going to medical school, but never really got around to applying. And after five years of working as an engineer, I decided to apply to medical school, ended up liking it, practiced medicine. And then after about a decade and a half of practicing medicine, saw that there was an opportunity to go into government. There were a lot of frictions and challenges to practicing medicine. And I thought it might be good to get into government to try to reduce those, represent for physicians and patients in the government, and had the opportunity to work at ONC and now had the opportunity to lead it. the way, fun fact, I think you overlocked with Mark Andreessen at U of I. I absolutely do. He graduated in 93 and I graduated in 94. And I remember it was in March of 93 that he and Eric Bina released the Mosaic web browser. And I was in the engineering college at the time. I will confess, he became very famous very quickly. So I walked to the place where they post the names of people smart guy. And I actually looked at the original Mosaic code and on all of his comments, when he would comment, he would comment under the name Marca, M-A-R-C-A. And so, yeah, so I remember going through the code and looking at the capabilities that were enabled. I think it was the first or the third web browser, but the really first commercially viable web browser. So yeah, we did overlap. I don't know if I ever met him or knew him on campus, but yeah, I remember it was a good place to be at the time. Yeah. There was something in the water. Well, I would argue that you've also played an equally consequential role in the history of technology for healthcare, specifically for, I mean, the ONC is, I think, one of the most underappreciated organizations in our healthcare ecosystem, based on the work that it's done to really bring healthcare into the modern era of using technology and software. Can you actually just educate the audience on what is ONC, what was the origin story of this department, and what is the mandate for what you do? office, it was actually called the Assistant Secretary for Technology Policy/National Coordinator for Health IT, which technically gave me the longest title in all of government. We did a reorganization and sent out on the National Coordinator for Health IT. [5:00] health IT. So, ONC's job is to oversee information technology and health information exchange. And the organization was started by executive order under President Bush in 2004 with the vision of getting all hospitals to use electronic health records within 10 years. Between 2004 and 2010, to be perfectly frank, a lot didn't happen because there were very few incentives for hospitals to that enables diagnostic imaging. This was adopted without any government incentives or mandates because there was a profit motive and a interoperability motive and a care motive that all the hospitals were exposed to. So the first PAC system was in 1989 at the University of Maryland. And by the year 2000, adoption of PAC systems was near universal in hospitals. The same thing did not happen between 2004 and 2010, the first six years in which President that ONC would allow for health IT adoption. So, in 2009, President Obama passed the HITECH Act, which mandated that hospitals had to adopt electronic health records and also provided $30 billion in incentives. And to give you an idea, back then, the total budget of the NIH was $30 billion. So, the incentives provided for EHR adoption were equal to the incentives for the United States. Between 2010 and 2015, the nation went from approximately 15% of hospitals and providers having electronic health records to 90%. And ONC's role in this was to facilitate the use of those funds, was to architect the programs under which the EHRs were adopted, and were also to guarantee a certain floor of functionality so that people are not just adopting PrEP, so that adopted. Around 2015, 2016, two frictions were identified in the market from the rapid adoption of electronic health records. The first was because they were tended to be purchased by hospital CFOs and CEOs. They tended to focus on billing and coding, something that would be an immediate return for the hospitals. They were not particularly user-friendly and were not particularly useful tools for clinicians or tools that would benefit patients. Similarly, Enolagopoly developed in which there were more or less four or five major EHR vendors that covered 90 to 95 percent of the market. And these EHR vendors held all of the in their electronic health records. So in 2016, President Obama proposed and the Senate passed, I think, near unanimously the Cures Act, which mandated two outcomes. The first is that burden on physicians and clinicians had to be reduced. And the second was that data had to be shared. And this is a very unique aspect of the health care system. When a company like Google acquires data from prior searches, they're under no obligation to share that. When a real estate company acquires data about what units are renting for and what units are selling for, they are not under any obligation to share that freely. They can sell that information and it can be leveraged by their customers for competitive advantage. The same is not true in healthcare. Information belongs to the patient and has to move for the benefit of the patient at the direction of the patient. So that's really the 2016 to current phase in which we really focused on which I hope to instantiate under my tenure, is the ONC as a platform builder. We want health data and health technology to be able to empower patients and to be able to transform healthcare, reduce costs, improve outcomes, and to have an ecosystem in which a thousand great use cases, applications, and patient-empowering technology blooms. Absolutely. And by the way, I started my first healthcare company in the during exactly that time of the HITECH Act being implemented. And it was so remarkable to see nearly overnight, I mean, seemingly overnight, the entire industry flip from paper to digitized EHR records. I mean, I'm making it sound very trivial. It was obviously a huge effort on the part of the providers implementing these things. But to your point, you made the example of Google doesn't have to do this or other industries don't have to do this. Was there any precedent that was looked at to actually inform the design of this program? Or how was this idea concocted? about the nature of it and the fact that you were literally incentivizing with a significant amount of money the adoption of a very specific technology, which I don't know that I've seen in any other industry, so I don't know if there's any other example of that. That's a good question. I don't really know. Actually, I think the development of the SWIFT system in banking was something that the government drove in the late 70s. They wanted banks to be able to interchange data efficiently and they [10:00] came up with the standards for that to happen. And obviously things like air traffic control and other things that needed to be standardized for national scale were standardized by the government. But what was unique was the financial incentives to encourage adoption. And I think that was President Obama, Jonathan Gruber, and others in the administration who said that if we digitize healthcare, we will be able to better manage it and be able to drive down costs and improve of the healthcare industry, namely that data has to be shared. I believe that came to be because there were so many stakeholders in the healthcare system that felt that this data really belonged to the patient and really should move for the benefit of the patient, that there was an intensive lobbying effort before Congress to say, look, this cannot be an oligopoly of a handful of truthfully well-intentioned and successful companies. They should not be able to hold holding it would actually harm patients. So we talked a lot about the history of ONC, how involved it's been in the modernization of the healthcare system. What are some of the underrated sort of successes of ONC and what have they done to really allow for patients or startups or builders to really flourish today in a way that they couldn't have five, 10 years ago? Well, I'd like to think none of our accomplishments are underrated. At least mine's not. 2020 Cures Act final rule, we mandated that all electronic health records had to expose a patient facing application programming interface that would allow patients to get and use their data according to certain standards and that the security posture of the APIs would have to be well defined and that any app that wanted to connect and grab the patient's data with the patient's proper permission, patient's proper identity validation would be able to expose that Additionally, we've stood up a nationwide network called TEFCA. This is really a role that I think the government had to play. Healthcare is a unique industry in that trust and harm are top of mind to the individual healthcare providers. to the families of patients who are deceased. Now, to be perfectly frank, ever since I've been in medicine, we've sent bereavement cards to patients and their families in the event that they passed away. And in some fields like oncology, that's very common. But there are actually large, prestigious healthcare systems out there that are concerned that this may be a violation of HIPAA. So, they've actually called and asked for clarification to say that it's okay to send And people just want to share the most basic information like, I'm sorry for your loss, with a patient's family. You also want to make sure that a patient isn't being exploited by sharing their information. Certainly sharing the information to an insurance company is useful because it allows the patient's care to be paid for. But as you know, there's a standard for minimum necessary. You only want to share that information that's absolutely necessary for the payment of the claim. Um... These constraints around how information is shared and how around actors in the market can interact with each other create real problems with trust, with scale, with security, with privacy. And by standing up TEFCA, we've tried to address this under a common agreement. We've tried to say here's one agreement, one set of protocols, one stand, you know, QHIN technical framework, we call it, to allow for the exchange of information. And we've stood this up. It was originally mandated in the 2016 Cures Act. And just as of now, we're at about 1.7 billion transactions, about 200 million transactions a month. Now, we're learning as we grow it. But we want it to be a completely reliable, robust national infrastructure that has 100% reliability. But those are two things, the exposed APIs. I guess the third thing I could call out is the instantiation of the information blocking. healthcare industry. And the fact that we were able to codify them, codify appropriate exceptions so that information wasn't being shared willy-nilly, but was being shared with the proper privacy and security protections, standing that up and then actually working with other agencies in government to make sure that they're enforced and to make sure that the market understands what's expected of them. That's, I'd say, a third accomplishment along with Tefk and the APIs. Another remarkable thing that I think people underappreciate, Tom, is the [15:00] I always say that healthcare is actually the one industry where we have regulation that supports the use of technology and AI in productive ways. Like the fact that we actually have a national rule that mandates APIs and MCPs and other such capabilities is unbelievable, like good for entrepreneurs and builders. And it's an indication of the fact that you are keeping up with the world moving around you in very fluid ways. of that that relates to the data piece that you're speaking to is the actual scope, like definition of like what makes for a medical record and a patient record. Today, most of the rules focus on traditional EHRs, largely in the acute care and outpatient setting with very traditional providers, in-person care, et cetera. And yet, as we all know, you know, one of the biggest areas of growth right now is, you know, consumer wearables, consumer chat data, biomarker as well. So, you know, somewhat outside of the traditional both clinical care and payment rails. How does ONC look at that universe? And do you consider that part of the scope of what you ultimately would, you know, have commentary on? And how should builders think about it? Because, you know, the risk is in the absence of clear rules about how that data gets treated, there's perhaps a risk that people hold back from leveraging that data to its full extent, you know, out of down later and define some rules that are counter to the way that it's been being used, that it could set them back. And so how do you think about this and what advice do you give to founders on how to think about that, the leading edge of data these days? That's an excellent question. And I believe our HTI6 rule has been published in the Unified Agenda so I can talk about it. One of the things that makes it so exciting to work at ONC is that we try to keep up with the cutting edge of technology. And we understand that there has been a migration of patient care and patient data outside of the traditional certified health IT, which is to say traditionally electronic health records. So we are taking into account that fact in our future rulemaking. So I believe you wrote a wonderful article in which you talked about the original sin of healthcare being that people who improve a patient's health oftentimes don't get to benefit from plan to plan or employer to employer or from hospital system to hospital system. So there's a misaligned incentive in keeping the patient healthy. One of the many original sins I've written about, I guess. Well, that is the one that is top of mind for me because, you know, our vision is that the patient will be the ultimate steward of their information and that in a really well-functioning piece of software or some piece of software in collaboration with a doctor that will longitudinally be responsible for that patient and be able to benefit from that patient being taken care of. Ideally, the patient is the most incentivized to take care of themselves. And if they're empowered with the right tools, they'll be able to do it. And it won't matter who their employer is, what their health plan is, and the like. So we're trying to empower that vision. And as part of that, data. We want to make sure that that data is reliable, that it is interpretable as structured observations, that it can be incorporated and integrated into traditional electronic health care systems or electronic health records, and that it can be leveraged by the health care system, which is to say the doctors and everybody in the system. We want to make sure that AI can interact with the electronic health care records and that the sharing of information is two-way. for guiding a patient's care, there should be a way for that to be communicated back to the traditional healthcare system and vice versa. And we believe that the incentives are there. AI, I should say SI now, SI is more powerful when it's empowered with data that is generated by the traditional healthcare system. And the traditional healthcare system will be empowered similarly by that data moving from SI into the traditional healthcare system. So we look at to allow for this information to be exchanged. And this can include things like MCP, data or standards about how you collect data from consumer wearables. Because as you know, right now, two wearables might actually give different data. You can wear one on one wrist, another on another wrist, and they may actually generate different data. So we need to make sure that it's somehow standardized and reliable. And then further, as we look to AI being an agent that acts on the patient's behalf, there has to be [20:00] some way to check the provenance of that AI acting, some way to audit it, some way to do a trace to know what did the AI do so that post-market monitoring can be made to make sure that there's no drift. And we're thinking about all of this as we do our future rulemaking. We're hoping to get it out this fall, the HTI6 rule this fall. But yeah, the vision that, the friction that you spoke of, the original sin of healthcare, is one that we've tried to build a vision around and try to build our standards and regulatory work to help cure. It's interesting because a lot of the way that I think entrepreneurs are thinking about this current moment is that the very notion of an EHR is evolving, right? I mean, we have a very specific definition of it today of like the system of record with clinical data and use for billing functions and things of that sort. But as a center of gravity of data moves or just the patient experience, frankly, moves outside of the walls of the hospital and the clinic, I think the very notion of what an EHR is is being redefined as we speak. So it'll be interesting to see how you all follow that. Well I know that our HTI rule it currently undergoing finalization But one of the things that we attempted to do with that is to move from a focus on basic functionality in the electronic health record towards a focus in HTI6 on interoperability So we proposed to scale back our certification program rather substantially. And I can speak to, for example, one of the requirements that we proposed to remove, and that was for the model cards that are used for transparency in AI. We were able to get pretty quick feedback on how this was working, and we found that the proposal, which actually went into enforcement January 1st, 2025, was not really a good fit for purpose. First of all, the information that the model cards were required to display are readily available. If I'm a physician at a hospital and I want to buy an AI, I can get that information. I'm just not going to buy your product. And if that information is part of a secret sauce or it's proprietary or it's intellectual property, you can expose that to me rather than a public model card. You can disclose that to me under an NDA. And we felt that that was a better fit for purpose. Secondly the information the 31 source attributes that we specified are a static data set We started hearing almost immediately that we specified the wrong 31 attributes or it should be a different 31 or it should only be five So that was another challenge with the regulation The third is this only applies to certified health IT. So, if you launch a SI application from the electronic health record that isn't integrated in it, I can't regulate that, and I can't make that requirement. So we started to see a migration of SI applications outside of the electronic health record so that they could escape the regulation. You know, these are fourth that just really wasn't being used very much. I think in the Oracle comment letter, which is public, they said that they had about two queries a month into the model cards. We were able to speak with Epic and they said they were getting about 50 queries per month. So it really wasn't being leveraged. I think what was most concerning to me as a physician is that it gave this sort of false assurance. We didn't actually audit what was represented in the model cards and there was no auditing function. So it had the purpose of serving as a good housekeeping seal of approval that didn actually have any audit or backing or assurance behind it So that why we proposed removing it And we certainly received public comments which anybody can read because they all public on it But the overall purpose of HTI-5 is to lower the costs of entry into the market. I mean, in the days of vibe coding, you can create a new electronic health record or a company that is a system of record or a company that performs many of the functions that a system of record would, you can create that quickly, probably in a year or two with Vibe coding. And we did not want to be standing in the way with a costly, burdensome certification program. So that's one of the reasons we proposed it. Amen to more competition and deregulation. Two things, again, that are remarkable to hear about coming from you. I'm curious, you mentioned Oracle. I mean, I think when you think about interoperability, there is a little bit of the incumbent versus new entrant dynamic, just initially, and a perception that perhaps there is more friction than needs to be in place when new entrants are trying to gain access to the underpaying data that you described earlier. And yet, the incumbents, I think, what they would claim is that they do have a responsibility, [25:00] to be secure and maintain privacy and perhaps be a little bit more on the conservative end of the stick with respect to how and to whom they enable access to these data sets in real life. And so how do you think about that balance? And is that... a moving target as well? Or, you know, how is that evolving in the landscape today, especially now that I feel like we have a flywheel, you know, spinning of real use cases where certainly I can say today, the way that I see our entrepreneurs getting access to EHRs and EHR data is a hundred times easier than when I was an entrepreneur, you know, 15 years ago. So something is clearly working, but, you know, we still have some of these frictions. So how should we think about that? Well, it will always be a moving target because as a technology, evolves, the technology can actually make systems more secure, better standards for a you know, identity, authentication, authorization, security can evolve. And as those evolve, we want to make sure that they're adopted and we want to make sure that information is shared in accordance with those. But of course, as something like quantum commuting comes online, or as AI becomes more sophisticated, you're exposed to more risk in the privacy and security realm. So we want to make sure that our program keeps consistent with that. But there are certain evaluate whether the frictions that somebody in the market are experiencing our legitimate privacy and security concerns or whether they are competitive moats masquerading as privacy and security concerns. One is, are affiliates and non-affiliates treated differently? So, if somebody has an affiliate relationship with a holder of health data, are they able to get that data more easily? Are they able to get it with less development The purpose of the information blocking regulations is to make sure that it's a level playing field. Our terms published for access to data within a system of record are fees in line with the market. Do development timelines actually have an end and are they reasonable and are they in keeping with what's going on in the market? Is the app working with three vendors and there's maybe two that it's not working with because those two vendors are reasonable. you know, are not really keeping up with their obligations under the information blocking regulation law. So there's many ways that we can test this and, you know, We... the Office of Inspector General, the Federal Trade Commission, the Department of Justice, have really worked out internally. What? what we think are appropriate tests for whether somebody is raising legitimate privacy and security concerns or whether they are attempting to leverage those for competitive advantage. What I would say to any developer out there is please bring to us the frictions that you're having. The frictions, to be honest, 90% of them are frictions to do with standards or to do with the normal operations of the market. programs. But we want to hear what are the frictions that you're having. And you can report them through the information blocking portal or you can reach out to us directly. The C in my name is coordinator. We are we're there to coordinate with the health care market. And importantly, in addition to telling us what those frictions are, tell us what the solutions are. What we've generally found is that when we communicate among the different actors in the market, realize that this was such an issue, we can change our behavior. When we feel that there is noncompliance with the law, that's when we start taking an enforcement posture. But we want to hear from people and we want to hear not only about the frictions, but also the potential solutions. And the more detailed, the better. Tom, that's great to hear. I know a lot of the portfolio companies and founders in our ecosystem and certainly investors have been really excited about all the work that you guys have been doing. So really appreciative of that. Certainly around the model cards, we're very excited around that space and also interoperability. So one piece that's been really top of mind for us, we're closing in on year two. There's been so much action. What does the next 12 to 18 months look like for you guys? What's top of mind? What are the biggest priorities? And how can the portfolio company founders and our ecosystem and across the space reach out to you and understand how to engage? What's the easiest way to go about that? made sure to engage with [30:00] to see if we could solve the problem. We will engage with everybody. It is the main purpose of our organization of the agency is to coordinate. People can also engage with CMS's health tech ecosystem. I think now they have 1,700 participants. That is a good opportunity for people to talk with other participants in the health tech world and shape the direction not only of policy, but of shared solutions. What are our immediate goals? We'd like to finalize HTI 5 and lower the barriers to entry. We will probably continue to refine the regulations around information blocking. You can expect that really in the next, honestly, you can expect all of this in the next six months. And we're going to continue to invest in TEFCA's national infrastructure. We want it to continue to grow. We want it to be an option for people. And we want to make sure that its reliability is 100 and that its use cases continue to expand and that it becomes a viable option for people who need to get health information Additionally you can expect us to continue to pursue an enforcement posture. We believe that we've been given a charge by Congress with laws to make sure that these laws are complied with. And between us, the OIG, the FTC, and the DOJ, we believe that we will send a strong signal to the market in a way that everybody can be agreeable to. Amazing. Bonus spicy question. Sure, spicy question. You've now spoken about all the ways that you're opening the doors to innovators, competition, interoperability, liquid data, etc. And you also referred to the oligopoly that exists today in our acute care EHR market. When do you think we will see a contender enter the playing field to break that oligopoly? Is it another two years? Is it another five years? Is it another 10 years? And then we're going to have you back on our podcast in whatever time period that is to see if we were right or wrong What would need to be true for there to be more players on the playing field in that EHR space You know I have the privilege of talking with everybody in the market including the systems of record themselves Everybody in the world believes that AI is going to, SI is going to transform the world, and it probably will. I mean, the technology is truly remarkable. of all the things I've gotten to see in my life develop from the personal computer I'm old enough to remember when those came online to the internet SI is truly transformative SI and the capabilities that empowers will transform the market and I actually think systems of record will be able to keep up and be able to find a place in that but I think at least if you talk to the vendors of the systems of record they recognize that the landscape is changing so to be more concrete one to two years wow okay I think it's the best possible yes absolutely I would have said the same invite me back in two years and in addition to telling me I've gotten two years older you can and then we can see how some of the CEOs of the companies that are in the new playing field of the future EHR amazing well thank you so much Tom This was excellent Thank you so much for your service to the country to the healthcare ecosystem to the future of SI in healthcare Okay, thank you. Thanks, Tom. Thanks for listening to this episode of Raising Health. If you liked this episode, be sure to like, comment, subscribe, leave us a rating or review, and share it with your friends and family. Follow us on X at A16Z and subscribe for our Substack at a16z.substack.com. Thanks again for listening, and I'll see you in the next episode. As a reminder, the content here is for informational purposes only. It should not be taken as legal, business, tax, or investment advice, or be used to evaluate any investment or security, and is not directed at any investors or potential investors in any A16Z fund. Please note that A16Z and its affiliates may also maintain investments in the companies discussed in this podcast. For more details, including a link to our investments, please see a16z.com forward slash disclosures.