One number makes NSW Health's Single Digital Patient Record look like a platform story:

A$969.6 million.

That is the amended estimated amount payable, including GST, disclosed under NSW Health's agreement with Epic Systems for the Single Digital Patient Record solution and associated services. It should not be confused with the total cost of every SDPR-related activity across NSW Health.

But three other numbers make the commercial opportunity much more interesting:

9 electronic medical record systems

10 patient administration systems

5 laboratory information management systems

NSW Health says the SDPR will ultimately unify all 24.

And during the first major district rollout alone, NSW Health transferred more than 12 million patient records, tested 1,500+ clinical devices and trained 23,000+ staff across 26 hospitals.

That changes how I would look at NSW as a HealthTech market.

The core platform decision has already been made.

The more useful question is:

What has to happen around Epic for a statewide transition of this scale to work?

That is where I see the commercial opportunity.

The first important distinction: Epic won the core platform, not every surrounding problem

NSW Health has contracted Epic Systems to provide the core SDPR technology platform.

Amazon Web Services provides the secure cloud hosting environment.

RLDatix Galen provides the statewide data archive.

eHealth NSW is a major delivery partner, while the Single Digital Patient Record Implementation Authority leads the statewide implementation.

That means a startup approaching NSW with:

“We can replace the EHR”

has probably misunderstood the market.

A much stronger question is:

“What does a statewide Epic transition still need around the core platform?”

Possible answers include:

integration

data migration

data-quality validation

historical-record retrieval

specialty workflows

legacy coexistence

device connectivity

change management

patient-facing workflow

reporting

and services or applications that need to be repositioned around the new architecture.

The commercial opportunity is therefore not necessarily another core clinical system.

It is often a transition problem.

The Audit Office finding makes this more important

The NSW Audit Office's 2025 State Agencies report made a particularly relevant observation.

It found that the original SDPR business case did not capture all relevant project costs, including the estimated cost of integrating SDPR with legacy systems that will remain in use. It also said implementation-cost estimates for in-scope health entities lacked robust supporting documentation because limited information was available when the estimates were developed.

That does not mean the project is failing.

It means something commercially more useful:

Integration complexity was significant enough that the original business case did not fully quantify it.

The phrase “reactive procurement risk” in my visual is my commercial interpretation of that finding, not language used by the Auditor-General.

Why does that matter?

Because large transformation programmes often create two markets.

Planned procurement

Known well in advance and incorporated into the architecture.

Emergent procurement

Problems become clearer during:

configuration

migration

testing

cutover

or:

post-go-live operations.

For vendors, arriving after the problem becomes urgent usually means:

less time

more incumbent advantage

more procurement friction

and potentially:

worse negotiating economics.

That is why the rollout calendar matters.

The market is bigger than a handful of hospitals

NSW says the SDPR programme will ultimately cover around:

228 public hospitals

600+ community health centres

60 pathology laboratories

and:

150+ pathology collection centres.

It is therefore closer to a statewide health infrastructure transition than a conventional hospital EHR implementation.

That has an important consequence for startups and investors.

A product that succeeds at one facility but requires completely bespoke technical work at the next five may have limited strategic value.

A product that creates reusable assets across successive tranches could become substantially more interesting.

The real unit of strategy is the tranche

NSW Health is deploying SDPR in five phases through 2028.

The published schedule remains the clearest official tranche map, while NSW's current SDPR pages confirm that Tranche A has been completed and statewide deployment remains targeted for completion by the end of 2028.

This creates a very different GTM question.

Not:

“Should we sell to NSW Health?”

But:

“Which tranche, which organisation and which transition problem should we enter through?”

Tranche A already provides useful evidence

Hunter New England is particularly valuable because it shows the scale of implementation behind a single tranche.

The May 2026 go-live covered:

26 hospitals

11 laboratories

46 collection centres

100+ community, patient and custodial settings

and:

23,000 staff.

More than 12 million patient records were transferred and more than 1,500 clinical devices were tested.

For a founder, those figures reveal that the opportunity is not simply “software installation.”

It is:

data

devices

interfaces

workflow

training

validation

operations

and:

change occurring simultaneously.

That gives us a much better framework for identifying adjacent opportunities.

Opportunity 1: Integration and legacy coexistence

This is probably the most obvious transition layer.

The mistake is assuming:

24 systems retire → integration complexity disappears.

It does not work like that.

Even with a common eMR/PAS/LIMS platform, hospitals still operate:

imaging systems

medical devices

specialty applications

pharmacy systems

registries

external-provider interfaces

analytics

identity systems

financial systems

community systems

and numerous other clinical and operational applications.

eHealth NSW itself highlights system integration as a major delivery responsibility and says it worked with SDPRIA, Epic and Solventum on statewide coding integration.

So an integration company's sales proposition should not be:

“We build interfaces.”

It should be:

“We reduce transition risk while making each successive tranche cheaper and faster to connect.”

The metric I would track: Integration Reuse Rate

For investors especially, I would ask:

What percentage of integration work from Tranche B can be reused in C, D and E?

Suppose a vendor builds eight integrations.

If every integration costs another A$20K at the next LHD, that looks service-heavy.

If 70–80% of the architecture becomes reusable, the economics improve considerably.

That is one of the reasons the accompanying calculator estimates:

interfaces × cost per interface

rather than hiding integration inside a generic implementation budget.

Opportunity 2: Data migration and validation

The 12 million records transferred in Hunter New England alone should get the attention of any founder working in:

migration

data-quality tooling

clinical terminology

mapping

validation

reconciliation

testing

or:

data observability.

Moving data is the easy way to describe the problem.

The harder questions are:

Did the right data move?

Did it map correctly?

What failed?

What was duplicated?

What must remain accessible but not migrate?

Which clinical history needs structured migration?

What requires manual validation?

Can the clinician trust what appears after cutover?

That makes migration much more than an ETL project.

It is also a clinical-risk problem.

A better migration framework

I would break it into:

Discover

What exists?

Classify

What should migrate, archive or retire?

Map

How does the legacy model translate?

Clean

What needs normalization or deduplication?

Validate

Did the right information land correctly?

Reconcile

Does source equal destination at clinically meaningful levels?

Sign off

Who accepts the result?

Reuse

Can the methodology be repeated in the next tranche?

The last step is where investors should focus.

Opportunity 3: Archive and historical-data retrieval

RLDatix Galen has already been selected to provide the statewide data archive, so a startup should not interpret the opportunity as:

“NSW needs an archive vendor.”

That platform decision has been made.

But archive infrastructure and historical-data usability are not necessarily the same thing.

There can still be adjacent questions around:

specialty-data retrieval

clinical context

reporting

legal/audit access

workflow integration

old application decommissioning

data discovery

and:

how users locate older records without recreating legacy complexity.

That distinction matters.

Storing old data safely is one problem.

Making it useful without keeping the old system alive forever is another.

Opportunity 4: The displacement and repositioning window

This is the part of the market I would look at particularly carefully if I were advising an existing HealthTech vendor already embedded somewhere in NSW.

A statewide platform change forces adjacent applications into one of roughly four positions:

REPLACE → INTEGRATE → ARCHIVE → REPOSITION

Replace

Epic or another statewide capability fully substitutes for the product.

Integrate

The product retains a distinct workflow and must connect.

Archive

The application stops being operational but historical information must remain accessible.

Reposition

The product still solves a useful problem, but its role changes in the new architecture.

That creates urgency for incumbent HealthTech companies.

The worst strategy is waiting until an LHD is weeks from cutover to discover which category applies.

Existing vendors should run a “survival audit”

I would ask five questions.

A product can move from:

threatened incumbent

to:

complementary layer

if that analysis happens early enough.

The three technology companies in the map matter for different reasons

Epic Systems

Epic is the core SDPR technology provider.

The commercial implication is straightforward:

Do not build a NSW thesis that assumes the core platform decision is still open.

Instead, understand the Epic ecosystem and where your application can complement it.

Amazon Web Services

AWS supplies the secure hosting environment for SDPR.

eHealth NSW describes the AWS Landing Zone as the secure, scalable foundation for managing and deploying SDPR.

For infrastructure vendors, that changes the question from:

“Should NSW move to cloud?”

to:

“What can we contribute inside or around an AWS-hosted statewide architecture?”

RLDatix Galen

RLDatix Galen provides the statewide archive.

That means archive-adjacent companies need a particularly disciplined value proposition.

Do not duplicate what is already contracted.

Look for gaps around:

retrieval

data usability

specialty access

transition

or:

workflow around archived records.

The buyer map is more complicated than “NSW Health”

This is one of the biggest commercial mistakes I would expect overseas HealthTech founders to make.

“NSW Health” contains multiple decision layers.

Potential stakeholders include:

Single Digital Patient Record Implementation Authority

eHealth NSW

NSW Health Pathology

individual Local Health Districts

specialty health networks

clinical executives

CIO / ICT leadership

data and interoperability teams

cybersecurity

privacy

procurement

and potentially existing strategic technology partners.

NSW's organisation structure itself separates LHDs, specialty networks, statewide services, eHealth NSW and SDPRIA.

The person who feels the pain may therefore not be the organisation that contracts the solution.

I would map six stakeholder roles

Problem owner

Who experiences the transition gap?

Clinical owner

Whose workflow is affected?

Technical owner

Who controls architecture and integration?

Data / governance owner

Who approves information handling?

Economic owner

Who benefits from solving the problem?

Procurement owner

Who can actually contract?

When those six are confused, commercialization slows.

My applied NSW framework

For founders, investors and technology executives, I would use:

TRANCHE → BUYER → SYSTEM → DATA → INTEGRATION → PROCUREMENT → REFERENCE

Tranche

When does the problem become urgent?

Buyer

Who actually owns it?

System

What is being replaced, retained or connected?

Data

What migrates, remains or archives?

Integration

Which systems have to work together?

Procurement

How does the vendor legally and commercially enter?

Reference

How does this tranche make the next one easier?

This is a much more useful GTM framework than simply targeting every NSW hospital.

The ROI equation should include the cost of missing the window

Most HealthTech ROI models look only at buyer value.

Vendors need their own equation.

Missed-Tranche Cost = Monthly GTM Burn × Months Until Next Viable Window

Suppose a startup burns:

A$45,000/month

and targeting the wrong buyer causes a six-month delay.

That is:

A$270,000 of commercial runway exposed

before counting:

lost contract revenue

engineering rework

founder time

or:

opportunity cost.

This is why market timing is financially material.

Model integration separately

Assume:

8 interfaces

at:

A$18,000 each

for discovery, configuration, testing and deployment.

Illustrative exposure:

A$144,000

Again, that is not an NSW benchmark.

It is an example of why integration should appear explicitly in the business case.

The Audit Office's finding makes that particularly relevant.

Model migration separately too

Suppose:

750,000 records / objects

with an assumed:

A$180 per 1,000 records

for migration, validation and QA.

Then:

A$135,000

of migration/validation effort is exposed under those assumptions.

The point is not that this is the correct NSW price.

It is that:

migration is not free just because the core platform is already funded.

Then test whether the contract economics still work

Using the calculator defaults:

Integration: A$144K

Migration / QA: A$135K

Implementation/change: A$90K

Total delivery exposure:

A$369K

If the first contract is only:

A$180K

then:

contract value ÷ estimated delivery cost = 0.49×

That is not automatically a bad opportunity.

A first tranche might have strategic reference value.

But the founder should then know exactly why the economics improve later.

Perhaps:

interfaces become reusable

migration logic repeats

training assets repeat

procurement documentation repeats

or:

contract scope expands.

Otherwise you may have built a consultancy project rather than a scalable HealthTech product.

Investors should test tranche-to-tranche operating leverage

I would ask a NSW-focused portfolio company:

What did Tranche B cost to implement?

What percentage is reusable in C?

How much shorter is D?

How many founder hours disappear?

How many technical assets repeat?

Does gross margin improve?

Does procurement get easier because the reference exists?

That is a much stronger scalability test than:

“We have NSW Health experience.”

A 25-buyer scenario is more useful than 500 Australian leads

The free calculator also tests a targeted-pipeline scenario.

Suppose:

25 priority buyers / ecosystem accounts

32% are genuinely qualified

20% directional win probability among those qualified

and:

A$180K first contract value.

Then:

25 × 32% × 20% × A$180K

=

A$288,000 probability-weighted pipeline scenario

It is not a forecast.

It forces the founder to expose their assumptions.

That is useful.

What I would prioritize by tranche today

With Tranche A already live and Tranche B still scheduled for late 2026, the commercial posture should differ by tranche.

Tranche A

Study what actually happened.

Look for:

post-go-live issues

integration lessons

migration patterns

training lessons

historical data needs

and:

reference evidence.

Tranche B

This is the highest-urgency near-term window.

The official schedule includes:

Northern NSW

Mid North Coast

Northern Sydney

Central Coast

and remaining LIMS North implementation.

At this stage, generic awareness-building is probably too weak.

The market intelligence needs to become account-specific.

Tranche C

Use 2026 to map architecture, buyers and evidence for:

South Eastern Sydney

Illawarra Shoalhaven

and:

Sydney Children's Hospital Network.

Tranche D

Large Sydney health districts make this particularly relevant for companies needing stronger reference evidence before approaching more complex environments.

Tranche E

Regional and rural implementation changes the economics again.

A product requiring heavy on-site configuration may be disadvantaged.

A lower-burden, repeatable deployment model may become more attractive.

What founders should do next

I would not start with:

“Give me every hospital in NSW.”

I would start with:

Once those are answered, lead generation becomes much more valuable.

What health-system executives should take from this

For NSW Health executives and implementation leaders, vendor evaluation should go beyond:

technical capability

and:

price.

A stronger transition scorecard would include:

implementation burden

integration reuse

migration validation

clinical safety

legacy decommissioning impact

historical-data access

staff change burden

security

vendor dependency

and:

cost across later tranches.

The cheapest first implementation is not necessarily the lowest-cost statewide architecture.

What investors should take from this

The NSW SDPR programme illustrates an important HealthTech diligence lesson.

A giant public-sector digital programme can create an attractive market while simultaneously making some startups obsolete.

The key question is:

Does standardisation remove the startup's reason to exist or create a larger interface into which it can scale?

That deserves diligence before treating:

“NSW Health transformation”

as automatically bullish.

Where I can help

The missing commercial layer for many vendors is not understanding that NSW is implementing Epic.

That information is public.

The harder work is determining:

which tranche matters

which LHD or ecosystem buyer matters

which system gap remains

who owns that gap

when the buying window opens

what proof NSW will need

and:

whether the economics can repeat across later tranches.

That is where my market-intelligence and commercialization work fits.

I would use the HealthTech Buyer Pipeline Sprint to turn this transition thesis into:

25 priority buyers / ecosystem accounts

plus:

15 relevant decision-makers

mapped around:

tranche

technical fit

buyer ownership

transition need

and:

commercial timing.

The aim is not another Australian healthcare directory.

It is a smaller list of accounts where there is a defensible reason to act now.

HealthTech Buyer Pipeline Sprint: 25 Buyers + 15 Decision-Makers
https://growthvybz.com/products/healthtech-buyer-pipeline-sprint-25-buyers-15-decision-makers

Final takeaway

The NSW opportunity is not:

“A$969M is being spent on Epic, so digital health vendors should sell to NSW.”

That is too simplistic.

The more useful interpretation is:

24 incumbent systems are being consolidated.

Five rollout tranches run through 2028.

More than 12 million records were migrated in the first major district.

1,500+ devices were tested.

23,000+ staff were trained.

And the Audit Office says legacy-system integration costs were not fully incorporated into the original business case.

That points to a more interesting commercial thesis:

The core platform has already been bought. The surrounding transition problems are where vendors now need to look.

And the companies most likely to benefit will not be those that simply arrive before 2028.

They will be those that can convert:

TRANCHE → TRANSITION GAP → BUYER → PROOF → PROCUREMENT → REUSABLE DEPLOYMENT

into a repeatable business.