Platform & engine modernisation
We move healthcare organisations off end-of-life engines, such as JCAPS and eGate, onto modern platforms such as Rhapsody. Interfaces are migrated like for like, proven with transaction comparison, and cut over safely.
Start with a risk assessment
We’ll assess your exposure first. A short, independent review of your current engine and interfaces shows how much risk you’re carrying, and whether to modernise now, plan for it, or stabilise what you have.
Engine, operating system or database support that has ended or is about to.
Only one or two people understand how the interfaces really work.
Business rules that live only in the code.
Unpatched platforms, outdated protocols and weak encryption.
What an outage would mean for care and operations.
A clear risk profile and a recommendation: modernise now, plan for it, or stabilise.
Like for like
An engine replacement is not the time to change how interfaces behave. We keep the logic like for like and introduce no new changes, so enhancements stay separate from the migration and every difference found in testing is a defect, not a design decision.
Proving the migration
Testing a migrated interface by hand only shows that it works for the cases someone thought of. Running real transactions through both engines and comparing the outputs shows that it behaves the same as the interface it replaces.
Our approach
Eight steps take your interfaces from the legacy engine to the new platform, with the transaction comparison at the centre of the approach.
We work with you to understand your current landscape: the systems connected to the engine and the number of interfaces running on it.
We trace the logic built into the engine from end to end, so every transformation, route and rule is understood before anything is rebuilt.
We work to your development and architecture guidelines for the new platform. If they don’t exist yet, we can help you build them.
Over the years, redundant logic accumulates in code across the legacy platform’s components. We remove it, so only what is needed moves across.
Interfaces are rebuilt on the new platform with the same logical behaviour. No new changes are introduced, keeping enhancements separate from the engine replacement.
Hundreds to thousands of transactions are run through both engines, and old and new outputs are compared using industry-standard message comparison tools.
Comparison reports for every interface give your teams clear evidence to review and sign off against.
A planned production cutover moves interfaces across in a controlled way, protecting live clinical operations.
Warranty
If something was missed, it’s on us.
Every migration we deliver comes with a 3-month warranty. If anything missed in the migration shows up once interfaces are live in production, we fix it under warranty, provided no changes have been made to the delivered build after deployment.