top of page

The Fastest Way Into the NHS Isn't Always Building More Technology

Jason Cropper
Sep 7
3 min read

When suppliers encounter barriers to adoption, the natural response is often to build more technology.


Illustration showing a health technology supplier's product represented by an amber cube connected to a healthcare ecosystem. On the left, a complex maze contains barriers labelled with concepts such as additional features, custom development, more interfaces, complex infrastructure and longer timelines. On the right, a clear puzzle-piece pathway leads directly to an NHS environment, with symbols representing connectivity, onboarding, security and collaboration. The image illustrates how simplifying interoperability and implementation can provide a faster route into the NHS than continually building additional technology.

A new feature is added, another interface is developed or additional functionality appears on the roadmap.


More time and investment are directed towards expanding the product.


Sometimes that is exactly the right decision.


Often, however, technology is not the problem that needs solving.


Many suppliers discover that some of the biggest obstacles to NHS adoption have little to do with functionality and a great deal to do with interoperability, onboarding, connectivity and implementation.


It's Rarely Just About the Product

Most health technology suppliers enter the market with a product designed to solve a specific problem.

  • It may improve efficiency.

  • It may support clinicians.

  • It may reduce administrative burden.

  • It may introduce entirely new capabilities.


The assumption is often that if the value of the solution is clear enough, adoption will naturally follow, the reality is usually more complicated.


Healthcare organisations are rarely evaluating a product in isolation, they are also considering how that product will fit into existing systems, workflows, governance arrangements and operational processes.


This means that technical capability is only one part of the overall equation.


More Features Don't Always Remove Barriers

When progress slows, suppliers understandably look at their roadmap.

  • Could another feature help?

  • Would a new capability make the solution more attractive?

  • Would additional functionality solve the problem?


Sometimes the answer is yes, more often, organisations are facing challenges that additional features will not solve.


The real questions may be:

  • How will we connect the system?

  • How will onboarding work?

  • How will users access information?

  • How will data flow between organisations?

  • How much effort will implementation require?

  • What support is needed to make the solution operational?


Adding more technology does not necessarily make these questions easier to answer.

In some situations, it can even make them more complex.


The Shortest Route Is Often the Simplest

One lesson that repeatedly emerges across successful interoperability projects is that simplicity matters. Healthcare organisations are already operating within complex technical environments and solutions that reduce complexity often have a natural advantage over those that add to it.


This does not mean products should be simplistic, it means suppliers should avoid creating unnecessary barriers to adoption.


Successful organisations often concentrate on removing friction wherever possible.

  • They simplify connectivity.

  • They reduce operational burden.

  • They make onboarding easier.

  • They minimise implementation effort.

  • They help customers realise value quickly.


These activities can have a greater impact on adoption than an additional feature release.


Interoperability as an Enabler

Interoperability is frequently viewed as a technical requirement, in practice, it is often an enabler of adoption.


Healthcare organisations want solutions that fit naturally into existing environments.

They want information to move effectively between systems, they want products that can participate in broader digital strategies.


The easier a supplier makes this process, the easier it becomes for organisations to realise value from the product. That is one reason why interoperability often becomes a competitive advantage, not because it's the primary reason a product is selected, but because it removes barriers that might otherwise prevent adoption.


Focus on Outcomes

The most successful suppliers tend to focus less on what their technology does and more on what it enables.

  • Their conversations revolve around outcomes.

  • They discuss benefits rather than features.

  • They consider workflows rather than interfaces.

  • They look at implementation as well as innovation.


Most importantly, they recognise that solving a customer's problem is more important than demonstrating technical capability.


Technology remains critical, but it isn't the only factor that matters.


A More Practical Approach

The fastest route into the NHS is not always through additional development effort, it often comes from understanding the environment more effectively, simplifying onboarding, reducing implementation complexity or improving interoperability.


The organisations that recognise this often progress more quickly than those that focus exclusively on adding functionality.


Success rarely comes from building the most technology, more often it comes from removing the barriers that prevent organisations from adopting it.


How Osprey Can Help

Osprey helps suppliers navigate the practical realities of NHS interoperability, onboarding and connectivity.


We work with organisations to reduce complexity, remove barriers to adoption and identify the most effective path from initial engagement through to successful implementation.


Whether you need support with onboarding, connectivity, interoperability strategy or implementation planning, our focus is always on helping organisations make meaningful progress while avoiding unnecessary complexity.


Related Solution

Navigate assurance, accreditation and connectivity requirements without unnecessary delay or complexity.

Want to discuss this post?

bottom of page