A New LIMS Does Not Automatically Create an Integrated Pathology Network

In our previous article, Maturing or Truly Integrated? The Next Question for NHS Pathology Networks, we explored the idea of operational proof, moving beyond how far a pathology network has developed to consider what it can demonstrably do as a result. Technology is a critical part of that conversation.

In this post, we look specifically at LIMS transformation and ask whether the success of a major technology programme should be judged primarily by successful implementation, or by the operational capabilities it enables across the network.

For pathology networks undertaking major digital transformation, replacing or consolidating Laboratory Information Management Systems (LIMS) can be one of the most significant investments they make. Modern platforms can provide essential foundations for standardisation, interoperability, automation and more effective working across multiple sites.

But a new LIMS does not, by itself, create an integrated pathology network.

The Pathology Transformation Review 2026 makes this distinction particularly clearly. It describes digital capability as core service infrastructure and identifies interoperable requesting and reporting, reliable specimen tracking, service-model-capable LIMS, operational analytics and tested resilience arrangements as essential to integrated pathology services.

But it also states that LIMS convergence or interoperability is “necessary, but not sufficient”. Benefits depend on factors including common data, workflow redesign, governance, adoption, workforce readiness and continuing investment. This matters because it changes how we should think about the success of major pathology technology programmes.

Go-live is a milestone, but not necessarily a measure of transformation

Implementing a new LIMS across a pathology network is a substantial achievement. It can require years of planning, procurement, configuration, migration, validation, training and organisational change.

Successful deployment matters. But if the objective is pathology transformation, the more important question comes after implementation:

What can the new service do now that it could not do before?

The same principle should apply to technology. A network may have successfully implemented a common LIMS, but the key questions are:

• Can leaders now see workload and capacity across the service?

• Can work be routed between sites more easily when pressure changes?

• Are test catalogues and reference data sufficiently harmonised to support consistent working?

• Can specimens be followed across organisational boundaries?

These are different measures of success from whether the system was delivered on time or whether the technical migration was completed successfully. Both matter, but they answer different questions. One tells us whether the technology programme was delivered. The other tells us whether it has helped create a more integrated pathology service.

A common system does not necessarily mean common working

This is particularly important in network environments. Carter identifies fragmented LIMS, duplicated test catalogues and inconsistent reference data as barriers to shared queues, cross-site routing, comparable activity data and consistent operational analytics. It also makes the point that technical connectivity alone cannot create shared service infrastructure. Common master data, adopted workflows and clear ownership of data quality are also required.

This highlights a distinction that pathology technology programmes need to address.

System convergence and service convergence are related, but they are not the same thing. Different laboratories can use the same technology while retaining different workflows, terminology, processes and ways of managing activity. Equally, technically connected systems may exchange information without enabling the service to manage workload, capacity and performance as a single network.

Technology creates the possibility of integration. The operating model determines whether that possibility is realised.

Start with the capability the network is trying to create

At JTG, we believe this should influence how pathology organisations approach digital transformation. Instead of focusing only on the system being replaced, networks should first be clear about the operational capabilities they need the new environment to enable.

If the ambition is to manage pathology as an integrated service, those capabilities might include network-wide workload visibility, shared queues, consistent requesting and reporting, cross-site referral and routing, end-to-end specimen traceability, comparable operational data and resilient working across sites.

Carter's proposed minimum digital standard reflects many of the same principles. It describes service-model-capable LIMS and master data arrangements that support harmonised test catalogues, shared queues, referral routing, workload visibility and comparable analytics. It also warns that procurement and architecture choices should avoid creating further integration problems through proprietary interfaces, supplier lock-in or data models that cannot be used consistently across the pathway.

That suggests a broader test for technology investment.

Not simply - Does the new system work?

But - Does the new system enable the network to operate more effectively as one service?

Technology should create operational proof

This brings the argument back to operational proof. If a LIMS transformation is contributing to genuine network integration, that should become visible in the way the service operates. Work should be easier to coordinate. Information should be more consistent. Capacity and backlogs should become more visible. Specimens should be easier to trace. Expertise should be easier to deploy across locations. Resilience arrangements should work at network level rather than only within individual laboratories.

The Carter Review describes completed operational integration as an environment where digital capability operates as shared service infrastructure rather than a collection of local systems, supporting shared queues, cross-site reporting, traceable samples, live backlog management and tested resilience. That is a useful standard against which to consider digital transformation.

A successful LIMS implementation can provide one of the most important foundations for an integrated pathology network. But implementation should not be confused with the end result. The real measure of transformation is what the technology enables the pathology service to do better as one network.

So the question for pathology leaders, suppliers and implementation partners is this:

When a major technology programme is complete, should success be measured by the system that has been delivered, or by what the pathology network can now do differently because of it?