325M+ patients have a current electronic record in Epic.

Epic also held 43.7% of the U.S. acute-care hospital EHR market at the end of 2025, up from 42.3% a year earlier. More than 3,700 hospitals use Epic globally.

Now add another development.

On September 1, 2026, OpenAI launched an Epic integration for ChatGPT for Healthcare, together with a Healthcare Public Data plugin that connects ChatGPT to official medical and healthcare datasets.

For me, this is not another integration announcement.

It changes the build-vs-buy equation for clinical AI.

A hospital that previously bought a separate application to:

• summarize charts
• retrieve history
• surface recent labs
• search evidence
• review medications
• prepare for a visit

can increasingly ask:

“Why should I add another application if AI inside my existing clinical environment can already do part of this?”

That does not mean clinical AI startups disappear.

It means the basis of differentiation changes.

First, what OpenAI actually launched

There are two distinct capabilities.

1. Epic context inside ChatGPT

Authorized healthcare users can bring permitted Epic patient-chart information into ChatGPT for Healthcare.

OpenAI says this can support questions such as:

• what changed since the last visit?
• which labs need review?
• were medications changed?
• what follow-ups remain unresolved?

The integration is read-only, requires organizational setup of the Epic FHIR endpoint and OAuth client, and respects the user's existing Epic permissions.

There is also an important second mode: supported deployments can put ChatGPT inside the EHR workflow, so the clinician does not necessarily need to leave the patient chart.

That is strategically significant.

The competitive threat is not only:

another AI model.

It is:

AI + chart context + workflow position.

325M does not mean OpenAI has 325M patient records

This distinction is essential.

Epic says more than 325 million patients currently have an electronic record in Epic.

That number describes Epic's footprint.

It does not mean those 325 million records are automatically available to OpenAI.

An individual healthcare organization must configure the integration, users must authenticate, and access remains governed by their organizational and chart-level permissions. The plugin is read-only.

I would therefore write the headline as:

“325M+ patients sit inside the Epic ecosystem.”

Not:

“OpenAI now has access to 325M patient records.”

The latter would materially overstate what was announced.

The second change may be almost as important: trusted evidence is moving into the same interface

OpenAI's Healthcare Public Data plugin supports nine official sources:

PubMed

ClinicalTrials.gov

DailyMed

RxNorm

openFDA

CMS Coverage

CMS Open Data

Medicare Care Compare

NPI Registry.

This means the same environment can increasingly combine:

PATIENT CONTEXT + MEDICAL EVIDENCE + PUBLIC HEALTHCARE DATA

That compresses several workflows that historically required different products or browser tabs.

My five-layer framework

I would analyse the market through five layers.

1. EXPERIENCE

Where does the clinician actually interact with AI?

Think:

pre-visit preparation

→ chart summary

→ lab review

→ evidence search

→ clinical review

→ patient communication

→ handoff

The closer AI gets to the clinical interface clinicians already use, the harder it becomes to justify a separate destination application.

This puts the most pressure on products whose primary proposition is:

“Come to our application and ask a clinical question.”

2. APPLICATION

This is where the startup market becomes much more interesting.

Capabilities include:

documentation

medical-history retrieval

imaging insights

medication review

patient communication

clinical decision support

and:

specialty copilots.

Some of these can become platform features.

Others can remain substantial businesses.

The distinction is usually:

GENERIC TASK vs SPECIALTY WORKFLOW

“Summarize this chart” is relatively generic.

“Identify radiological deterioration, trigger the appropriate stroke workflow, route the case and track intervention time” is much deeper.

3. ORCHESTRATION

This may become one of the most important layers.

A useful clinical system increasingly needs:

context understanding

reasoning

planning

tool invocation

citations

guardrails

auditability

and:

workflow execution.

This is one reason several leading clinical-AI companies are already positioning beyond simple transcription.

Abridge now describes itself as a broader clinician-intelligence platform spanning care delivery, payment and evidence-based treatment, rather than only an ambient-scribing product.

Nabla describes a unified platform including ambient documentation, dictation, workflow tools and agentic capabilities.

Corti launched agentic healthcare infrastructure intended to support workflows including clinical decision support, coding and care coordination.

That is the direction I would watch:

NOTE → WORKFLOW → ORCHESTRATION

4. DATA ACCESS

This may be where some of the strongest moats survive.

The future clinical-AI stack can combine:

EHR context

clinical notes
labs
medications
vitals
encounters
orders

with:

trusted public evidence

PubMed
ClinicalTrials.gov
DailyMed
RxNorm
FDA data
CMS data

with:

proprietary context

specialty datasets
medical images
continuous sensor data
longitudinal outcomes
local protocols
specialty labels
real-world evidence
workflow feedback.

This leads to a useful founder test:

If ChatGPT has the same patient chart and the same public medical literature, what does your product know that ChatGPT does not?

That is a much sharper moat question than:

“Which LLM do you use?”

5. INFRASTRUCTURE

The lowest layer is not glamorous, but it is strategically important.

The major cloud players remain:

Microsoft Azure

AWS

Google Cloud

while the clinical stack above increasingly requires:

identity

security

FHIR

auditability

data governance

model monitoring

clinical evaluation

and:

enterprise deployment controls.

OpenAI's healthcare product itself emphasizes RBAC, audit logs, data residency, customer-managed encryption keys, HIPAA-supporting controls and a BAA option.

That tells startups something important.

Enterprise buyers are no longer comparing:

AI vs no AI.

They are comparing:

AI stack vs AI stack.

The 5 startup categories I would watch

Clinical copilots

Abridge

Ambience Healthcare

Suki

Nabla

Corti

This group faces obvious platform pressure because documentation and chart summarization are moving closer to EHR-native AI.

But it would be too simplistic to conclude that these businesses are therefore obsolete.

The leading companies are already moving deeper.

Abridge says its platform is trusted by more than 300 health systems and is expanding beyond documentation into contextual intelligence, payment and clinical decision support.

Suki is investing in real-world research around ambient clinical intelligence and continues expanding embedded workflows.

Nabla has expanded from ambient documentation into workflow tools and agentic capabilities.

Corti is explicitly building infrastructure for healthcare agents.

The winning strategy is increasingly:

DOCUMENTATION → WORKFLOW OWNERSHIP

Data and interoperability

Redox

Particle Health

Zus Health

Health Gorilla

Firely

I see a different dynamic here.

More AI in healthcare can actually increase demand for reliable data infrastructure.

The value shifts from:

“Can I technically fetch a record?”

toward:

Is it complete?

Is it normalized?

Can I trust the identity match?

Can AI consume it safely?

Are the permissions valid?

Is the provenance preserved?

Particle continues to expose clinical-data retrieval through formats including FHIR, C-CDA and structured data.

Health Gorilla operates as a QHIN and provides national clinical-data exchange and FHIR-oriented APIs.

Firely remains focused specifically on FHIR infrastructure and implementation.

This group may benefit from a useful paradox:

The smarter the AI becomes, the more expensive bad clinical context becomes.

Specialty AI

Aidoc

Viz.ai

Regard

Qure.ai

Aignostics

This is where I expect the "generic AI kills startups" thesis to break down most quickly.

Specialty AI can own:

modalities

care pathways

disease-specific workflows

specialty data

clinical validation

and:

action after detection.

Regard, for example, is expanding its diagnosis/documentation platform from hospital medicine into cardiology and surgery.

Aignostics continues to build pathology-specific foundation models and launched a visual pathology search capability in September 2026.

The competitive question becomes:

Can generic AI reason about medicine?

versus:

Can the startup execute this particular clinical workflow better, more safely and with specialty-specific evidence?

Those are very different questions.

Monitoring and care delivery

Huma

Doccla

Corsano Health

Biofourmis

Infermedica

This category can also defend itself differently.

The moat may be:

continuous data collection

devices

care protocols

clinical escalation

virtual wards

staffing

care navigation

or:

measured utilization reduction.

Doccla now positions around virtual wards, proactive care and remote monitoring and publishes operational outcomes from deployments.

Huma continues to operate remote-monitoring and virtual-care infrastructure.

Corsano combines medical-grade wearables, continuous monitoring and EHR integrations.

Infermedica continues operating clinical-AI triage across more than 30 countries.

Their stronger defense is not:

“Our AI understands healthcare.”

It is:

WE OWN A CARE LOOP.

Evidence and decision support

OpenEvidence

Glass Health

AMBOSS

UpToDate

Elsevier ClinicalKey

This category faces one of the most interesting platform shifts.

If ChatGPT can retrieve PubMed and other authoritative sources directly, generic medical search becomes less differentiated.

But trusted clinical knowledge remains valuable.

The competitive edge moves toward:

curation

editorial rigor

specialty context

provenance

citations

clinical governance

and:

integration into decision-making.

UpToDate now offers UpToDate Expert AI, combining generative AI with its clinician-authored knowledge base.

Elsevier expanded ClinicalKey AI in 2026 with additional full-text medical content and healthcare-oriented security capabilities.

Glass Health combines clinical decision support with ambient/documentation capabilities.

So once again, the market is moving from:

SEARCH → TRUSTED INTELLIGENCE → WORKFLOW

The new winning formula

The formula I would use is:

EHR CONTEXT + TRUSTED SOURCES + SPECIALTY INTELLIGENCE + WORKFLOW EXECUTION + MEASURABLE OUTCOMES

That is stronger than:

“We have a healthcare chatbot.”

Four things founders should stop treating as moats

1. Generic summarization

A major platform can increasingly do this.

2. Model access

Everyone can buy access to strong foundation models.

3. Basic PubMed search

Trusted medical search is increasingly becoming embedded infrastructure.

4. "AI-powered" branding

Hospital buyers now have multiple credible AI options.

None of those disappear.

They simply become less sufficient.

Six things that become more valuable

1. Workflow ownership

Does your product merely provide information?

Or does it:

trigger

route

document

coordinate

monitor

and:

close the loop?

2. Proprietary context

The key question becomes:

What do you know that the chart + public literature do not?

Examples include:

specialty datasets

longitudinal outcomes

annotated images

care-pathway data

real-world evidence

device streams

institution-specific knowledge

and:

feedback generated through workflow use.

3. Measurable ROI

Health systems should increasingly be able to compare:

bundled AI

against:

specialized vendor.

Your product needs to demonstrate why the second option is worth paying for.

I would measure:

clinician minutes saved

staff capacity released

additional cases handled

denials avoided

revenue captured

length of stay

readmissions

diagnostic time

treatment delay

or:

prevented utilization.

The calculator ROI example

The free tool I built for this article uses a deliberately simple buyer-value model.

Assume:

200 clinicians

save:

12 minutes per workday

with an estimated loaded cost of:

$120/hour

across:

220 workdays.

Annual capacity value:

200 × 12/60 × $120 × 220

=

$1.056M

Now assume the product creates another:

$250K

in measured annual value from revenue, utilization, quality or risk improvement.

Total measurable annual value:

$1.306M

At an annual contract value of:

$250K

the directional buyer-value multiple becomes:

5.2×

and simple payback is around:

2.3 months

Those are illustrative numbers, not industry benchmarks.

But that is exactly the conversation founders need.

Not:

“Our model is 7% better.”

Instead:

“Here is what this workflow is worth after your existing AI stack is taken into account.”

4. Integration becomes a product feature

The OpenAI announcement makes this particularly clear.

The Epic integration is not merely a connector.

It allows authorized clinical context to come into ChatGPT and, in supported deployments, ChatGPT to appear directly inside the EHR experience.

That raises the baseline.

A HealthTech company asking clinicians to:

open another application

authenticate again

search for the patient

copy data

and:

return to Epic

now has a bigger commercial problem than before.

I would track:

WORKFLOW STEPS REMOVED

as a product KPI.

5. Evidence and safety become commercial differentiators

OpenAI says ChatGPT for Healthcare includes citations, RBAC, audit logs and regulated-workspace controls, and explicitly says final decisions remain with clinicians.

That raises expectations for everyone else.

Startups should prepare:

clinical validation

evaluation datasets

known failure modes

source provenance

citation quality

human review points

model-change governance

audit trails

and:

escalation logic.

These are no longer merely compliance appendices.

They are part of sales.

6. Distribution still matters

A technically better product does not automatically win.

Health-system AI adoption is increasingly influenced by:

enterprise relationships

EHR partnerships

integration pathways

security approval

clinical champions

procurement history

and:

implementation confidence.

That means distribution itself becomes part of defensibility.

Where the visual's 70–90% and 2–5× figures need changing

I would not publish these as factual market statistics:

70–90% displacement risk

50–80% integration potential

2–5× growth acceleration

3–10× data value multiplier

I could not find credible market-wide evidence supporting those specific ranges.

They work as scenario concepts, but not as sourced benchmarks.

For the blog and calculator, I replaced them with something stronger:

Platform Displacement Exposure Score

Calculated from the company's own:

platform overlap

workflow ownership

specialty depth

data defensibility

and:

integration fit.

Platform Complementarity Score

Calculated from:

integration

workflow depth

specialty value

data

clinical evidence

and:

ROI.

That makes the output defensible because the user supplies the assumptions.

The five-layer investor diligence framework

For investors, I would use:

Then add a commercial overlay:

DEFENSIBILITY × ROI × DISTRIBUTION

A startup can have outstanding AI and still have weak investment economics if those three are missing.

Founder strategy by category

What executives should ask vendors now

Hospital executives should stop evaluating AI products in isolation.

I would ask:

What does Epic already provide?

What does our enterprise AI platform provide?

What unique layer does this vendor add?

How many workflow steps disappear?

What proprietary context is involved?

What outcome changes?

Who owns ongoing validation?

How easily could this capability become bundled?

That is a much better procurement framework than:

“Does it use AI?”

What investors should ask portfolio companies

For each company I would ask:

If Epic adds this feature next year, what remains?

If OpenAI improves the model, what remains?

If model costs fall 80%, what remains?

If every competitor gets the same model, what remains?

The answers should ideally include:

workflow

data

distribution

clinical evidence

integration

and:

customer outcomes.

If the only answer is:

“Our prompts are better,”

the moat probably needs more work.

A 90-day response plan

Days 1–30: map overlap

Separate functionality into:

commodity

differentiated

and:

proprietary.

Ask which features can realistically move inside Epic or another enterprise AI platform.

Days 31–60: quantify differentiated value

Build one buyer-grade model around:

time

capacity

revenue

risk

or:

clinical outcomes.

Days 61–90: map high-fit buyers

Identify the health systems where your product's differentiated layer matters enough to pay separately.

Not 500 hospitals.

Start with:

25 high-fit buyers + 15 relevant decision-makers

and map:

clinical owner

informatics owner

digital/AI owner

budget owner

security/data owner

and:

procurement path.

Where I can help

The missing layer for most HealthTech founders is not explaining what OpenAI or Epic launched.

That information is public.

The harder commercial questions are:

Which part of your product is now commoditizing?

Which part becomes more valuable?

Which health systems still have an unsolved gap?

Who owns that gap?

What ROI justifies a separate contract?

What integration pathway reduces buyer friction?

and:

Which 25 organizations should you pursue first?

That is where my HealthTech Buyer Pipeline Sprint fits.

It maps:

25 priority healthcare buyers

plus:

15 relevant decision-makers

around your actual:

workflow

specialty

integration path

ROI

and:

commercial timing.

The objective is not to produce another hospital list.

It is to identify buyers where your product still has a clear reason to exist after the platform shift.

HealthTech Buyer Pipeline Sprint: 25 Buyers + 15 Decision-Makers

Final takeaway

OpenAI's Epic connection does not mean every clinical-AI startup is threatened.

It means the baseline moved.

Capabilities such as:

chart retrieval

summarization

evidence search

and:

generic clinical assistance

can increasingly live closer to the system of record.

So I would expect defensibility to shift toward:

SPECIALTY DEPTH + PROPRIETARY CONTEXT + WORKFLOW OWNERSHIP + INTEGRATION + CLINICAL EVIDENCE + MEASURABLE ROI

The EHR can remain the system of record.

AI may increasingly become the system of interaction.

The strongest startups will own something deeper:

the system of action.