Case studies/Hospitals and clinics · United Kingdom

One care platform for a UK healthcare group

We rebuilt the core operational platform of a UK healthcare group. Patient data, clinical and administrative workflows and partner integrations across its hospitals and clinics now run in one secure, modern system, and the switch happened without pausing care.

Stack
ReactTypeScriptNode.js (NestJS)PostgreSQLRedisKeycloakDockerKubernetesOpenTelemetryGitLab CI/CD
One platform and one patient record, connected to the clinical systems and partners the group already works with. Illustrative diagram.
Context

The group had grown through new sites and acquisitions, and its core system had grown with it, one patch at a time. Business logic was tied to the database, so even small changes were risky. Laboratories and partners exchanged data through legacy message feeds and scheduled file transfers. Each site had its own version of the same processes, and some patients existed as duplicate records in different locations. Staff kept parallel spreadsheets to fill the gaps.

Challenge

Replace the legacy system with a platform that supports further growth and meets UK data protection and clinical safety expectations, while hospitals and clinics keep treating patients every day.

What we did

  1. 01Mapped how care actually flows. Together with clinical leads, ward managers, booking coordinators and the information governance lead, we mapped the real patient pathways from referral to follow-up, separated clinically justified local variations from historical habits, and harmonised them into one configurable model.
  2. 02Designed for clinical safety from the start. For every module that touches patient care we identified what could go wrong, such as a wrong patient selection or a lost referral, and built safeguards before release.
  3. 03Built a workflow and approval engine. Pathways are versioned configuration with owners, conditions and deadlines. Approval chains, automatic escalations and a full audit trail of who did what, when and why support inspections and clinical governance.
  4. 04Migrated data as a clinical asset. Module by module, with automated reconciliation before each switch-over. Duplicate patient records were resolved by matching national identifiers and demographics, with every uncertain match reviewed by a person. Legacy codes were mapped to standard clinical terminologies.
  5. 05Replaced fragile feeds with one integration layer. Laboratories, imaging providers, insurers and partners now connect through one documented, standards-based interface, while partners on older formats remain supported.
  6. 06Rebuilt the interface for every role. Role-specific screens in React and TypeScript, built to WCAG 2.2 AA and tested with staff at the front desk, on wards and in clinics.
  7. 07Secured it by design. Role-based access with single sign-on, encryption in transit and at rest, audit logging of all access to patient records, UK data residency, and delivery aligned with UK GDPR and NHS information governance expectations. Built on open-source components and open standards, with no vendor lock-in.
Result

The same configurable workflow and approval engine is the backbone we use for sustainability action plans: clear owners, deadlines, escalations and an audit trail for every decision.

All sites on one platform, with one patient record
Phased migration completed without interrupting patient care
Pathway changes made by configuration, not by development projects

The client's internal team now maintains and extends the platform independently.

In healthcare, rewriting software is never only a technical task. The hardest part was understanding how care really moves between people and sites, and then building a system that respects clinical safety at every step. That domain work is what made the migration invisible to patients and staff.

Clinical lead, UK healthcare groupName withheld under NDA
Next case
AllClinics, turning fragmented hospital data into decisions