Client Profile
The client is a UK-based private healthcare group operating a network of 28 hospitals, specialist surgical centres, and outpatient clinics across England and Wales. The organisation treats approximately 450,000 patients per year across a mix of NHS-funded and self-pay activity, employs 7,200 staff, and has an annual turnover of approximately £620 million. Its technology estate includes clinical information systems, patient administration platforms, radiology and laboratory information systems, and enterprise back-office applications covering finance, HR, and supply chain management.
Oracle's role within the estate was primarily in the back-office domain. Oracle Database Enterprise Edition underpinned the group's finance and HR applications, Oracle E-Business Suite provided the core financial management, procurement, and HR platform, and Oracle Analytics was used for management reporting and financial consolidation. Clinical systems — including the patient administration, electronic patient record, and theatre management platforms — ran on separate, non-Oracle database infrastructure and were explicitly excluded from the scope of the Oracle support review.
The group had certified its Oracle ULA six months prior to the Redress Compliance engagement, locking in a perpetual licence position of 64 processor licences across its primary data centre and a disaster recovery site. The post-certification annual Oracle support obligation was £1.4M per year — a significant and growing cost line that the group's technology director had identified as a priority for review during the current financial year.
The Challenge
The post-ULA support review presented a specific challenge common to healthcare organisations: the need to distinguish between Oracle deployments where clinical safety or regulatory obligations required Oracle-direct support, and deployments where the primary support use case was break-fix and patch management on stable, non-upgrading back-office applications. Healthcare organisations often treat all Oracle support as uniformly high-risk, accepting Oracle's premium rate across the entire estate without analysing whether that premium is justified for each component individually.
The group's technology leadership understood that Oracle's value proposition for support — access to new product features, upcoming Oracle patches, and Oracle's own technical resources — was meaningful only for systems that were actively upgrading or where Oracle-specific issues were a regular occurrence. For the group's Oracle E-Business Suite and Oracle Database instances, which had been running without material incident or upgrade for four years, the realistic support consumption was a small fraction of the support contract value.
The complicating factor was the healthcare context. The group's risk committee required assurance that any transition from Oracle-direct support would not affect the availability or performance of systems that, while not clinical in themselves, supported functions material to patient care — including procurement of clinical supplies, payroll for clinical staff, and financial controls relevant to CQC regulatory reporting. Any support model change needed a robust risk assessment and clear escalation procedures to gain board-level sign-off.
The Approach
Redress Compliance conducted a structured support triage of the group's Oracle estate, classifying each Oracle Database instance and each E-Business Suite module into one of three categories: business-critical with active upgrade dependency, business-important but stable, and low-criticality or effectively dormant.
The triage identified 18 processor licences directly supporting the group's patient administration billing interface, CQC regulatory reporting extracts, and payroll processing as requiring Oracle-direct support due to the proximity of these functions to regulated and time-sensitive clinical operations. These were retained on Oracle support at their existing rate of approximately £460,000 per year. The remaining 46 processor licences — covering Oracle Database instances supporting internal management reporting, non-critical E-Business Suite modules including travel and expenses, and Oracle Analytics — were assessed as candidates for third-party support transition.
Redress conducted a formal third-party support provider evaluation on behalf of the group, assessing three specialist providers against criteria including their Oracle E-Business Suite coverage depth, patch equivalency processes, UK-based support capability, and healthcare sector reference base. A preferred provider was selected on the basis of a superior SLA framework for healthcare environments and a demonstrated track record with similarly regulated organisations. The transition was executed over a 90-day period, covering patch management handover, access revocation from Oracle's support portal for transitioning systems, and onboarding of the third-party provider into the group's IT service management platform.
The Outcome
The annual Oracle support cost after transition was £460,000 — a reduction of £940,000 per year from the pre-transition level of £1.4M. Over three years, the cumulative saving was £2.82M. The organisation retained Oracle-direct support for the 18 processor licences covering regulated and patient-proximate functions, maintained a single, clean Oracle support relationship for those systems, and transferred the remaining estate to third-party support without incident.
In three years of operation under the new model, the group experienced no clinical system disruption attributable to the support transition, no Oracle audit challenges relating to the support change, and no escalations to Oracle for the transitioning workloads that could not be resolved by the third-party provider. The board-level risk committee confirmed at its annual review that the transition had delivered the anticipated savings without introducing the clinical or operational risks that had initially been cited as barriers.
Key Takeaways
- Not all Oracle support in a healthcare environment carries equal risk. The clinical sensitivity of an organisation does not mean that all Oracle back-office systems require Oracle-direct support. A structured triage distinguishing regulated-adjacent systems from stable administrative applications consistently identifies transition candidates that carry manageable risk.
- Third-party Oracle support for E-Business Suite is technically mature. Specialist third-party providers have deep expertise in Oracle E-Business Suite environments and can provide patch equivalency, break-fix support, and critical update coverage at 45–55% of Oracle's rate for organisations with no Oracle upgrade plans.
- Governance processes in regulated environments add time, not fundamental barriers. Risk committee approval, board sign-off, and CQC-alignment requirements can all be addressed with appropriately structured risk assessments and clear contractual escalation paths. Healthcare organisations that assume regulatory constraints block third-party support transitions are consistently proved wrong by the evidence.
- Retaining Oracle support for a subset of systems is a valid and common outcome. A hybrid model — Oracle-direct for regulated-adjacent systems, third-party for stable back-office workloads — delivers substantial savings while preserving the Oracle relationship where it is genuinely valued.
- Post-ULA is the optimal point for a support review. At certification, the organisation has a defined, documented licence position. This clarity — combined with the removal of the open-ended unlimited commitment — is the ideal moment to reassess whether Oracle-direct support at scale continues to represent value for money.
Paying Oracle support rates across your entire estate, including systems you haven't upgraded in years?
Redress Compliance can triage your Oracle estate and model the savings from a hybrid support approach.