“Is CentrixConnect a software-only solution, or does it include IT equipment? One of the challenges we run into is IT holding things up.”
This question came up in our recent webinar with Chrystal Medical, and we thought it would be worth bringing the conversation here.
For healthcare organisations, NHS in particular, IT resources and provisions can be a real barrier to change.
The question of “Is this going to get held up by IT?” is a fair one!
Prior to working with us, we’ve heard this from our customers too. Almost every healthcare team has been through it before. A project to resolve their inventory management issues starts with good intent, then slows down once infrastructure, approvals, devices, and competing priorities come into play. By the time everything is aligned, the original problem is still there and the team has lost momentum.
So, the hesitation is understandable.
When we think about adoption, we try to remove as many of those barriers as possible upfront. CentrixConnect is fully web-based, which means there’s no requirement for local server infrastructure. It can run on existing devices, which avoids the need to wait on hardware rollouts before getting started.
Some teams choose to introduce mobile devices like iPads for certain workflows, but that’s driven by what works operationally, not by a dependency in the system.
The other part of this is how you approach the rollout itself.
We’re not expecting teams to replace everything in one go. That’s not how this works in reality. What we’ve seen work is starting in one area where the pressure is highest, getting that working properly, and then expanding from there. Which department is struggling the most? Alright then, let’s start there.
That’s how we’ve been able to get departments live quickly in some cases. Not because the environment is simple, but because the scope is controlled.
In our experience, this IT concern is usually a signal of something broader. It’s about disruption, time, and whether the effort required to implement something will outweigh the benefit.
That’s the part that needs to be answered clearly.
If it feels like the only way to improve things is through a long, complex rollout, it’s understandable that teams hold back. When there’s a more manageable way to approach it, that’s usually where the conversation opens up.
If this is something you’ve been weighing up internally, we’re happy to talk it through in detail.