Ireland is investing €263 million in Digital for Care capital projects during 2026.

But founders should be careful with that number.

It is not a disclosed €263M budget for Ireland’s new national EHR.

The €263M covers a much broader portfolio including the HSE Health App, National Shared Care Record, Electronic Health Records, ePharmacy, virtual care, AI and automation, national finance and workforce systems, core ICT infrastructure and cyber resilience.

That distinction matters because the commercial opportunity around Ireland’s One Health Record is bigger and more complicated than simply asking:

Who wins the EHR contract?

The HSE describes One Health Record as the largest digital transformation programme ever undertaken by the Irish health system.

It is expected to support approximately:

5.3 million people

160,000 staff

and:

all six HSE health regions.

The real founder question is therefore:

What infrastructure, integration, data, identity, workflow and adoption capabilities have to exist around the winning EHR for a programme of that scale to work?

That is what my Ireland National EHR Opportunity Grid is designed to expose.

First, one correction to the visual

The February 5, 2026 milestone is best described as:

Government approval of the One Health Record Preliminary Business Case

rather than simply “procurement approved.”

The HSE Board recorded that Government approval was received on 5 February 2026, followed by publication of the Request to Participate during the week beginning February 9. Responses were due March 24.

The procurement is using competitive dialogue, and eTenders currently lists the competition in Evaluation. The HSE expects to select the successful vendor in 2027.

That is commercially important.

The market has moved beyond:

“Ireland might procure a national EHR.”

The procurement process is already underway.

The implementation opportunity is real, but suppliers need to understand where it sits

The official tender does not ask only for software.

Its scope includes:

managed software services, configuration, installation, integration, implementation, data migration, training, hosting and post-implementation support and maintenance.

This changes the commercial interpretation of my eight opportunity layers.

They should not be read as:

“Ireland will issue eight standalone contracts.”

Some capabilities may be provided directly by the winning EHR vendor.

Others may be subcontracted.

Some could be delivered by technology partners.

Other needs may emerge through separate national procurements, existing HSE programmes, regional adoption work or complementary systems.

So the useful commercialization question becomes:

Which route gets your capability into the programme?

I would think about four possible routes:

This is why partnership intelligence can become more important than generating a list of Irish hospitals.

The contract itself signals a long-term ecosystem

The European procurement notice lists a 240-month contract duration.

That is twenty years.

The notice does not disclose a meaningful estimated contract value; the published notice shows €0 for that field.

So again, the €263M Digital for Care allocation should not be used as a proxy for the value of the OHR contract.

But a long-duration national platform relationship has another implication:

Once architecture, interfaces and partner relationships are established, the cost of entering the ecosystem later may rise substantially.

That makes 2026–27 strategically important even for companies whose revenue may not materialise until closer to deployment.

The rollout calendar creates three different commercial markets

The HSE expects to choose a vendor in 2027.

The first OHR implementation is planned for HSE Dublin and North East in 2029.

A second health region is expected in 2030.

Two more regions are planned for 2031.

The final two are expected in 2032.

That gives me three commercially distinct phases.

This is why waiting for the EHR vendor announcement before building an Ireland strategy may be too late.

By that point, part of the partner architecture may already be taking shape.

The six regions matter, but they are not six separate EHR procurements

Ireland now operates through:

HSE Dublin and North East

HSE Dublin and Midlands

HSE Dublin and South East

HSE Mid West

HSE South West

and:

HSE West and North West.

Each region has its own leadership, budget and responsibility for local service delivery and decision-making.

But One Health Record is being procured as a national application service.

That distinction matters.

The national layer determines:

platform architecture

core procurement

standards

and much of the technology direction.

The regional layer increasingly matters for:

implementation

adoption

workflow

service configuration

training

operational priorities

and eventually:

value realization.

A founder therefore needs both a national buyer map and a regional adoption map.

My eight opportunity layers

1. System integration

Commercial rating: Very High

Main window: 2026–2029

Market-watch examples from the visual:

InterSystems

Rhapsody Health Solutions

Orion Health

These are examples of the type of capability to watch, not confirmed OHR bidders or suppliers.

Integration ranks highest because a national EHR does not make the surrounding health-system architecture disappear.

It still needs to work with:

diagnostics

laboratories

imaging

pharmacy

specialty systems

community services

identity infrastructure

finance

national platforms

and potentially legacy systems during transition.

The HSE itself has acknowledged the variation of IT systems across services and has been reviewing data duplication as part of the EHR programme.

A strong integration proposition therefore should not say:

“We support HL7 and FHIR.”

That is table stakes.

The buyer case should answer:

Which interface burden do we remove, how much deployment effort do we save, and how reusable is that integration when the next region goes live?

The integration metric investors should watch

I would track:

Regional Integration Reuse Rate

Suppose a company builds ten interfaces for Dublin and North East.

When region #2 goes live, how many need to be built again?

If 80% of the work repeats, the startup may still be operating like an integration consultancy.

If 70–80% becomes reusable, the operating leverage changes.

This is more useful than simply saying:

“We are integrated with the HSE.”

2. Identity and access

Commercial rating: High

Main window: 2026–2029

Market-watch examples:

Daon

Okta

Imprivata

Identity becomes strategically important because One Health Record is intended to function across multiple organisations, settings and user groups.

That raises issues around:

authentication

role-based access

single sign-on

consent

patient matching

staff identity

access governance

and:

audit trails.

There is already a particularly relevant market signal here.

The 2026 Irish Healthcare Awards shortlist includes an HSE / Galway University Hospitals / PFH / Imprivata national single-sign-on rollout specifically described as preparation for One Health Record and Digital for Care 2030.

That tells founders something useful:

Some enabling infrastructure is being built before the EHR itself arrives.

Waiting until 2029 misses that market.

3. Data migration

Commercial rating: High

Main window: 2027–2032

Market-watch examples:

BridgeHead

Informatica

Iron Mountain

The tender explicitly includes data migration.

That makes migration a confirmed requirement.

But it does not mean every migration vendor gets a separate HSE contract.

The question is whether that capability is supplied by:

the prime EHR vendor

a subcontractor

an implementation partner

or:

another HSE procurement.

For a specialist vendor, the commercial argument should therefore be stronger than:

“We migrate data.”

It needs to answer:

How do we reduce mapping effort?

How do we measure data quality?

How do we reconcile old and new records?

What remains in legacy systems?

What can safely be archived?

How do we validate migration clinically?

What can be reused at the next region?

A better migration equation

I would model:

Migration Value = Effort Avoided + Data-Risk Reduced + Cutover Time Saved + Reusable Assets

rather than:

price per record.

That produces a much stronger executive business case.

4. Patient portals and digital access

Commercial rating: Medium–High

Main window: 2027–2032

Market-watch examples:

Patients Know Best

DrDoctor

Induction Healthcare

This layer needs careful positioning because Ireland is already investing in the HSE Health App, and One Health Record is expected eventually to allow patients to access their own records online.

So a portal startup cannot simply pitch:

“Patients need access to their records.”

Ireland already has that strategic direction.

The stronger adjacent opportunities may be:

booking

pre-visit workflows

forms

patient messaging

pathway navigation

consent

PROMs

remote engagement

or other functionality that improves what happens around the record.

The commercial test becomes:

Does this solve a workflow the national EHR and HSE App do not solve sufficiently well?

That is a much harder but much more defensible question.

5. Analytics and reporting

Commercial rating: Medium

Main window: 2028–2032

Market-watch examples:

C2-Ai

IQVIA

SAS

A national longitudinal record changes the potential value of analytics.

Instead of isolated hospital-level data, Ireland is trying to create more consistent information across acute and community settings.

The six health regions also now have more local responsibility for planning and delivery.

That creates potential needs around:

population health

capacity planning

clinical outcomes

service variation

regional performance

risk stratification

and:

resource allocation.

But analytics often arrives after foundational data quality.

So I would be cautious about pitching sophisticated AI before answering:

Is the underlying data standardized, accessible and trusted enough?

6. Clinical coding and terminology

Commercial rating: High

Main window: 2027–2032

Market-watch examples:

Solventum

IMO Health

Clinithink

This layer is easy to underestimate.

A national health record has to make clinical information usable across:

organisations

regions

specialties

and potentially multiple downstream systems.

That increases the importance of:

SNOMED CT

ICD

terminology mapping

semantic normalization

and:

clinical coding.

The technical proposition is standardization.

The commercial proposition is broader:

Can the same clinical information be safely understood, reused, analysed and reported consistently across the country?

That is much closer to the value buyers care about.

7. Training and change

Commercial rating: Medium–High

Main window: 2028–2032

Market-watch examples:

Kainos

Version 1

Accenture

One reason I include training/change as a separate market is that technology adoption becomes an operating issue at this scale.

The HSE Strategy and Reform Committee has already specifically discussed the workforce culture challenge associated with OHR adoption.

That means change management is not decorative project work.

It can determine whether the investment actually produces value.

A national EHR affecting about 160,000 staff creates a major requirement around:

training

role redesign

workflow change

super-users

implementation support

communications

and:

post-go-live adoption.

The wrong metric is:

“People completed training.”

Better metrics are:

workflow adoption

support tickets

time-to-proficiency

error rate

task completion time

and:

percentage of intended functionality actually used.

8. Infrastructure and cloud

Commercial rating: Very High

Main window: 2026–2032

Market-watch examples:

AWS

Microsoft Azure

Ekco

Hosting is explicitly part of the OHR tender, while the broader 2026 Digital for Care programme also includes major investment in core ICT infrastructure and cyber resilience.

Again, this does not imply Ireland will separately procure every cloud-related component.

It means infrastructure is fundamental to the programme.

The commercial questions become:

resilience

performance

security

data protection

identity

operations

monitoring

backup

disaster recovery

and:

long-term cost.

For infrastructure vendors, it may be much more valuable to become part of the winning delivery ecosystem than to pitch the HSE independently after architecture decisions have already been made.

The full 24-company market-watch stack

I would label all 24 exactly as:

market-watch examples, not confirmed OHR bidders

because no public evidence currently supports saying that these 24 companies are all competing for the programme.

That distinction protects the credibility of the map.

The procurement route may matter more than your product category

This is one of the biggest strategic conclusions from the research.

Suppose a migration startup has an excellent product.

There are still at least four possible outcomes.

Route A: direct national supplier

The HSE contracts directly.

Route B: technology partner

The winning EHR vendor embeds the product.

Route C: implementation subcontractor

A prime systems integrator buys the capability.

Route D: later regional deployment

The need emerges during rollout or adoption.

Those are four very different sales strategies.

A startup that chooses the wrong route can waste a year talking to people who cannot buy.

Competitive dialogue changes how suppliers should think

The One Health Record procurement uses a competitive dialogue process.

That mechanism is typically used when the buyer needs dialogue with qualified suppliers to refine complex solutions before final tenders.

For adjacent vendors, that means 2026–27 is particularly important for:

architecture awareness

partner discovery

proof packaging

and:

knowing which problems are likely to sit inside the prime contract.

You do not want to spend 12 months trying to sell something directly to the HSE only to discover that the successful EHR bidder is contractually responsible for delivering it.

The buyer map should have four layers

I would structure Ireland account intelligence as follows.

The OHR tender itself anticipates coverage across HSE services, acute and community care, Section 38 providers and some Section 39 providers.

That makes this a larger commercialization ecosystem than simply targeting Irish hospital CIOs.

The six-region structure creates an investor test

Because the deployment is phased regionally, investors should ask:

Does region #2 become easier than region #1?

Track:

implementation cost

integration reuse

training reuse

security documentation reuse

partner dependency

support burden

sales-cycle reduction

and:

gross-margin improvement.

If none improve, the business may still be selling bespoke projects.

If each regional implementation creates reusable deployment assets, the economics become much more interesting.

The calculator ROI model

I designed the accompanying calculator primarily from the supplier/investor side because that is where this market map is most useful.

The model uses:

Commercial Contribution

=

Expected contract value × gross margin

−

bid / partnership / localization investment

−

first-delivery cost

Then it separately calculates the cost of getting timing wrong.

Window Delay Cost

=

Monthly GTM burn × months delayed

Example with the calculator defaults

Suppose a HealthTech company estimates:

€180K first-year opportunity

60% gross margin

€40K pursuit / localization cost

and:

€45K first-delivery cost.

Gross profit before pursuit/delivery:

€180K × 60% = €108K

Contribution after those costs:

€108K − €40K − €45K

=

€23K

That means the first contract may not be enormously profitable.

But assume 60% of the delivery work becomes reusable in the next region.

The second-region delivery exposure falls from:

€45K

to:

€18K

That is where the commercial thesis becomes interesting.

The value may not be the first project.

It may be the operating leverage created by the first project.

Now model the cost of arriving late

Suppose the commercial team burns:

€35K/month.

Missing the partner / procurement window by six months produces:

€210K of additional runway exposure

before considering:

lost contract value

engineering rework

management time

or:

the opportunity cost of pursuing the wrong route.

This is why I think timing should sit alongside TAM in any Ireland market-entry decision.

A 25-target pipeline scenario

The calculator also lets founders test the logic behind targeted account intelligence.

Using:

25 priority buyers / partners

32% genuinely qualified

20% directional win rate

and:

€180K average first-year opportunity

gives:

€288K probability-weighted pipeline scenario

This is not a forecast.

It is useful because it exposes the assumptions.

If only 10% of your 25 targets are actually capable of buying or partnering, the strategy needs fixing before more outreach begins.

A stronger investor diligence framework

For a portfolio company claiming an Ireland opportunity, I would ask:

That last question is especially important.

The platform-risk test

Every vendor in the eight opportunity layers should ask:

Could the winning EHR vendor simply absorb this functionality?

If yes, there are three possible strategies.

Differentiate

Solve something the core platform cannot solve sufficiently.

Partner

Become part of the core vendor's ecosystem.

Reposition

Move to a workflow where the national EHR increases rather than removes your value.

Ignoring platform risk is not a market-entry strategy.

Why the €263M number is still useful

Even though it is not the OHR contract value, it tells us something important.

Ireland is not implementing the national EHR in isolation.

The same Digital for Care programme is simultaneously investing in:

the HSE Health App

Shared Care Record

ePharmacy

virtual care

AI

finance/workforce systems

infrastructure

and:

cybersecurity.

That means successful vendors should think less about:

one EHR tender

and more about:

Ireland's emerging national digital-health architecture.

There may be opportunities at the intersection of those programmes that are more attractive than the EHR itself.

My commercialization framework

For this market, I would use:

PROGRAMME PHASE → BUYER → PARTNER → PROBLEM → PROOF → PROCUREMENT → REGIONAL SCALE

Programme phase: Position, integrate or scale?

Buyer: HSE national, region, provider or partner?

Partner: Can the winning EHR / SI accelerate entry?

Problem: Which implementation dependency do you solve?

Proof: What deployment or ROI evidence matters?

Procurement: Direct, subcontract, ecosystem or regional?

Regional scale: What becomes easier at the next rollout?

That is the commercial layer underneath the visual.

A practical 30-day Ireland OHR sprint

During the first week, I would classify the offer into one of the eight layers and identify whether it competes with the core EHR or complements it.

During week two, I would map the national programme, all six regions, major provider stakeholders and the likely implementation ecosystem.

During week three, I would narrow the market to around 25 genuinely relevant organisations / buyer-partner targets and identify approximately 15 decision-makers or influencers who matter to the selected route.

During week four, I would build an account thesis for each priority target:

Why this organisation?

Why this capability?

Why now?

Is the route direct or through a partner?

What implementation problem exists?

What proof is missing?

What would winning this account unlock?

That gives business development something much more useful than:

“Here is a database of Irish hospitals.”

Where I can help

The public information already tells founders that Ireland is buying One Health Record.

You do not need a consultant to discover that.

The missing commercial layer is usually:

where your product sits around it

whether the capability is already inside the core scope

which procurement route is realistic

which partners matter

which region becomes commercially relevant first

who actually owns the problem

and:

whether the first deployment creates repeatable economics.

That is the work I would do before scaling outreach.

My HealthTech Buyer Pipeline Sprint is designed around that gap: 25 priority buyers / partners + 15 relevant decision-makers, selected around the specific commercialization thesis rather than simply company size.

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

Final takeaway

Ireland’s One Health Record is a significant opportunity.

But the wrong interpretation is:

“€263M is being spent on the national EHR.”

It is not.

The more defensible interpretation is:

€263M has been allocated to the wider Digital for Care capital programme in 2026.

The national OHR procurement is already in evaluation.

The tender includes integration, migration, implementation, training, hosting and ongoing support.

The successful vendor is expected in 2027.

The first regional deployment is planned for 2029.

National rollout is targeted for completion by 2032.

So the companies most likely to capture value will not simply be those with technology Ireland could use.

They will be those that understand:

WHERE THEY FIT → WHO BUYS → WHO PARTNERS → WHEN TO ENTER → WHAT PROOF IS NEEDED → HOW REGION #2 BECOMES CHEAPER THAN REGION #1

That is the real Ireland EHR opportunity