Over the last couple of years, I’ve spent a lot of time travelling between NHS Trusts and Health Boards, sitting with Clinical Engineering teams, nurses, operational leads, digital transformation teams, estates functions, and frontline staff.
What’s become increasingly clear during those conversations is that many NHS organisations are wrestling with the same operational challenges, regardless of geography.
Equipment cannot always be located quickly.
Devices leave departments and become difficult to track.
Preventive maintenance programmes are disrupted because assets are unavailable when engineers need them.
Community equipment moves beyond the visibility of acute sites.
And frontline teams often develop local workarounds simply to keep services moving.
What’s interesting is that these conversations rarely stay focused on “tracking technology” for very long.
Very quickly, they become wider discussions around:
- operational flow,
- workforce pressure,
- compliance,
- governance,
- integration,
- community care,
- patient discharge,
- and how healthcare systems adapt to increasingly distributed models of care.
Recently, we reviewed a detailed NHS asset tracking report produced following several years of operational testing and pilot activity within a UK healthcare environment. What stood out wasn’t simply the technology discussion. It was how honestly the report captured the operational realities of trying to implement innovation inside healthcare systems already under immense pressure.
What began as a relatively focused BLE deployment around bladder scanners evolved over time into a much broader operational conversation involving Clinical Engineering, community services, infrastructure, workflow management, integration challenges, and long-term service transformation.
In many ways, it reflected the same themes we continue to encounter in conversations across the NHS today.
The original problem rarely stays the original problem
One of the most important lessons emerging from these programmes is that organisations often begin by trying to solve a very specific operational issue.
Initially, the focus might be:
- bladder scanners,
- infusion pumps,
- wheelchairs,
- maintenance compliance,
- or reducing time spent searching for equipment.
But once organisations begin understanding how assets move operationally, entirely new use cases and challenges start to emerge.
The conversation quickly expands into:
- patient flow,
- equipment utilisation,
- over-purchasing,
- staff productivity,
- discharge delays,
- community visibility,
- workflow orchestration,
- and long-term operational planning.
That evolution is important because it changes how organisations think about deployment itself.
This is rarely about implementing a single piece of technology to solve a single isolated problem.
It becomes a broader operational transformation discussion.
Innovation often slows when operational ownership becomes fragmented
One of the more candid aspects of the report was its reflection on how projects can lose momentum over time.
Not because the original problem disappears.
But because healthcare environments are operationally complex.
The report highlighted challenges around:
- inconsistent project ownership,
- delayed development cycles,
- supplier dependency,
- unclear accountability,
- fragmented communication,
- and competing operational pressures.
Again, these are themes we hear repeatedly across healthcare environments.
The reality is that innovation inside the NHS does not happen in isolation from operational pressure. Teams are already balancing:
- workforce shortages,
- winter pressures,
- compliance obligations,
- digital transformation programmes,
- and increasingly complex care pathways.
That means even good ideas can stall if:
- workflows are unclear,
- stakeholder engagement weakens,
- or operational ownership becomes fragmented.
One of the most valuable lessons from these programmes is that technology alone is rarely enough.
Successful adoption requires:
- operational clarity,
- stakeholder alignment,
- realistic deployment expectations,
- and ongoing engagement with frontline teams.
Community care changes the complexity entirely
Another consistent theme emerging from conversations across the NHS is that the challenge becomes significantly harder once equipment leaves acute settings.
Historically, many asset management processes were designed around static hospital environments.
That is no longer the reality.
Today, equipment moves continuously between:
- wards,
- hospitals,
- community hubs,
- hospices,
- patient homes,
- and virtual ward environments.
As more healthcare shifts toward community delivery and hospital-at-home models, organisations are increasingly trying to understand how they maintain operational oversight across highly distributed environments.
The report highlighted this challenge particularly well in relation to community infusion pumps and mobile medical devices.
And this is where another important operational lesson begins to emerge:
No single technology solves every environment equally well.
Why Floki evolved its approach differently
Many of these conversations and lessons have directly shaped how we’ve evolved our own approach at Floki Health.
Early on, there can be a temptation in healthcare technology projects to think in terms of large-scale deployments from day one.
But what we’ve learned is that NHS organisations often need the opportunity to:
- understand a local operational issue first,
- test workflows safely,
- engage frontline teams gradually,
- validate adoption,
- and prove value incrementally.
In practice, some of the most important operational insights only emerge once systems are being used within live healthcare environments.
That is why we increasingly focus on smaller proof-of-value deployments around clearly defined operational pain points before scaling more broadly.
Sometimes that may involve:
- infusion pump tracking,
- theatre equipment flow,
- compliance workflows,
- community device movement,
- or understanding how assets move between departments and sites.
The objective is not simply to deploy technology.
It is to understand where operational friction genuinely exists and where measurable value can realistically be achieved.
One of the biggest lessons we’ve taken from NHS operational environments is that flexibility matters enormously.
Different healthcare settings require different approaches.
Some environments justify real-time Bluetooth tracking infrastructure.
Others are better suited to:
- QR-code workflows,
- GPS tracking,
- RFID,
- WiFi telemetry,
- geofencing,
- or mobile-native workflows.
That is why we’ve evolved Floki around a blended operational platform capable of bringing multiple technologies together into a single operational dashboard and workflow environment.
The important point is not the individual technology itself.
It is the ability to apply the right operational approach to the right healthcare problem.
In practice, a community workflow may require QR-code interactions and GPS confirmation.
A theatre environment may require BLE and fixed-location awareness.
A compliance workflow may rely on RFID scanning and mobile applications.
The operational challenge changes depending on:
- the environment,
- the asset,
- the movement pattern,
- and the value of the workflow being improved.
What we’ve found is that healthcare organisations gain far more confidence when they can:
- start pragmatically,
- prove operational value,
- understand adoption patterns,
- and then scale progressively where pressures are greatest.
That approach has shaped how we now work with NHS organisations.
The broader lesson emerging across the NHS
Perhaps the biggest takeaway from these conversations is that asset tracking programmes rarely remain purely about asset tracking.
Very quickly, they become conversations about:
- operational efficiency,
- patient flow,
- workforce pressure,
- sustainability,
- community care,
- integration,
- and how healthcare organisations adapt services around increasingly complex models of care.
The NHS does not need technology for technology’s sake.
It needs practical operational solutions that fit the realities of frontline healthcare delivery.
And in my experience, the organisations making the greatest progress are usually the ones willing to:
- start with a real operational problem,
- engage staff early,
- learn incrementally,
- and scale pragmatically rather than trying to solve everything on day one.
Those are the conversations increasingly shaping the future of healthcare operations across the NHS.
Exploring a specific operational challenge in your organisation?
One of the consistent lessons we’ve learned working alongside NHS teams is that the most valuable insights often come from starting small.
Rather than attempting large-scale transformation from day one, many organisations benefit from testing a clearly defined operational challenge first, whether that’s:
- infusion pump flow,
- community device tracking,
- equipment availability,
- compliance workflows,
- theatre utilisation,
- or understanding how assets move between departments and sites.
Small proof-of-value deployments allow teams to:
- validate workflows,
- engage stakeholders,
- understand operational pressures,
- and build confidence incrementally before scaling further.
If your organisation is exploring a particular operational challenge around medical devices, equipment flow, or asset management, we’d be happy to have an initial conversation and explore whether a focused proof-of-value approach could help get you started.
Fen Smith is CEO of Floki Health and spends much of his time working with NHS teams across the UK to better understand the operational realities shaping medical device tracking, community care, and healthcare workflow transformation.