Skip to content

Diagnostic AI:
Shared learning without sharing patient data

We built a federated learning platform that trains diagnostic AI inside each hospital's own firewall. Hospitals share model updates, not patient data. Diagnostic accuracy rose 40%, with zero data leaving any site.

Industry: HealthcareService: AI & Automation

Higher diagnostic accuracy
40%
Patient data leaving hospitals
Zero
HIPAA alignment
100%

Overview

Project
at a glance

Industry
HealthTechA multi-centre clinical research network that needed shared diagnostic AI across independent hospital systems.
How we worked
Dedicated product teamAn ML architect, a bio-data engineer and a HIPAA compliance lead worked inside the client's clinical innovation group.
Goal
Precision medicine within HIPAA rulesTrain detailed diagnostic models on large, varied datasets without pooling sensitive patient health information in one place.
What we built
Federated learning platformTraining pods inside each hospital's firewall that share model updates, never patient records, with one global model.

Client

Who we
built it for

BioMetrics Solutions

Multi-centre clinical research network

Healthcare
About the client
A multi-centre clinical research network that needed shared diagnostic AI across independent hospital systems.
What they needed
Train detailed diagnostic models on large, varied datasets without pooling sensitive patient health information in one place.
Where they were
The client wanted AI that could locate tumours early, but the data it needed sat in separate regional hospital systems. Standard machine learning would have meant copying everything into one cloud store. That carried major HIPAA legal risk, and the hospitals refused on data-control grounds.

Engagement snapshot

Industry
Healthcare
Service
AI & Automation

The challenge

What was getting
in the way

The client wanted AI that could locate tumours early, but the data it needed sat in separate regional hospital systems. Standard machine learning would have meant copying everything into one cloud store. That carried major HIPAA legal risk, and the hospitals refused on data-control grounds.

Models trained at single sites on small datasets were too weak for clinical use. The network needed a way to learn from every site's data without moving it.

  • Regulatory deadlock

    Hospital legal teams blocked data from leaving their sites over patient data liability, which halted diagnostic AI work for 14 months.

  • Siloed, weak models

    Separate models trained on small datasets were not accurate enough for clinical use, wasting millions in R&D spend.

  • Loss of trust

    Centralised approaches lacked the detailed audit trail needed for patient consent across several organisations.

The solution

What
we built

  1. 01

    Training inside each hospital

    Cloud-based training pods run inside each hospital's private firewall, so patient data never leaves the site.

    Type
    Local inference
    Privacy
    Zero egress
    Runtime
    HIPAA-gated
  2. 02

    Secure weight aggregation

    Only model weights, the patterns a model has learned, are collected to update the global model. Patient data stays where it is.

    Protocol
    Differential privacy
    Aggregation
    Federated averaging
    Audit
    Weight lineage
  3. 03

    Traceable compliance records

    An encrypted audit trail of every training round proves that no raw patient health information went into the global model updates.

    Audit
    Traceable data
    Compliance
    SOC 2-ready
    Trail
    Secure, traceable logs

Key features

What made it
useful

  • FEDERATED LEARNING

    Trains inside each hospital

    Diagnostic models train inside each hospital's firewall, and only model weights are combined into one shared model through federated averaging.

    Business impact

    Zero patient data left hospitals

  • PRIVACY

    Private, audited training rounds

    Differential privacy protects patient identities, and an encrypted audit trail records every training round.

    Business impact

    Diagnostic accuracy up from 62% to 87%

  • HIPAA-GATED

    Differential privacy

    Mathematical noise is added to weight updates so patient identities cannot be worked out from them.

    Business impact

    Zero re-identification risk

  • AI-ASSISTED

    Automated data selection at each site

    Pods at each hospital pre-process local data and pick only high-quality samples for training.

    Business impact

    3.5x faster convergence

  • READY TO GROW

    Self-healing edge clusters

    Remote nodes recover on their own, so training carries on through hospital network interruptions.

    Business impact

    24/7 training uptime

Before and after

How the work
changed

Data residency

Before

High-risk data transfer

Moving patient records to a central cloud created a large security target and HIPAA liability.

After

Local control

Data stays where it was created. Only model weights move between sites, which removes the patient data risk.

Compliance

Before

Consent delays

Hosting data with a third party meant a complex process of asking patients to consent again.

After

Privacy by design

AI developers never see the raw data, which keeps the work aligned with GDPR and HIPAA.

Model accuracy

Before

Weak single-site models

Models trained on narrow regional data did not generalise across different patient groups.

After

Learning from every site

Diagnostic accuracy rose 40% by learning from varied datasets at all sites at once.

Results

The business
difference

  1. ACCURACY

    40% Accuracy Gain

    Diagnostic accuracy

    The 40% gain is relative to the earlier model. Learning from every site made the model dependable across all major ethnic and age groups.

    Before: 62%After: 87%

  2. SECURITY

    100% Risk Reduction

    Data egress events

    No raw patient health information crossed any hospital firewall during training.

    Before: High RiskAfter: Zero

  3. SPEED

    18x Faster Sync

    Training sync time

    Automated edge processing cut the time needed to sync local updates with the global model.

    Before: 72h SyncAfter: 4h Sync

Testimonial

What the client
says

“We needed shared diagnostic models without sharing patient data. Coretus set up training inside each hospital's firewall, and accuracy rose from 62% to 87% with zero patient data leaving any site. Training sync is also 18x faster.”
Angela DaviesDirector of Research Informatics, BioMetrics Solutions

Key results

  • Diagnostic accuracy up from 62% to 87%
  • Zero patient data left hospitals
  • Training sync 18x faster

Trust and control

How we kept it
safe and reliable

  • 01

    Patient privacy

    Raw patient health information never leaves the hospital. Differential privacy stops patient identities being reverse-engineered from the model.

    HIPAA-GATED
  • 02

    Hospital control

    Each hospital keeps 100% control over training on its own node and can disconnect from the platform at any time.

    VERIFIABLE DATA
  • 03

    No cloud lock-in

    The platform runs on AWS, Azure or on-premise hardware, with no dependence on one vendor.

    READY TO GROW
  • 04

    Code and IP ownership

    The client owns 100% of the federated system design and the global diagnostic model it produced.

    100% OWNED

Faster delivery

Built on tested foundations

Reusing tested components saved about 12 weeks of setup work, which went into the privacy controls and the diagnostic model.

  • HIPAA data vault module

    Our tested data vault kept each hospital's training data locked inside its own firewall.

  • Federated automation platform

    A reusable federated platform sent the global model out to each site and collected the weight updates back.

  • Bio-ML monitoring platform

    An existing monitoring platform tracked training rounds and model accuracy at every site.

  • Edge FinOps safety controls

    Pre-built cost controls kept compute spend on the edge training pods within budget.

FAQ

Straight
answers

Have a different question? Ask it on a 30-minute call.

Book a call

Training happens inside each hospital's own firewall, on that hospital's data. Only the model weights, the patterns the model has learned, are sent out and combined into one global model. Differential privacy adds noise to those updates, so patient identities cannot be worked out from them.

Train on patient data without moving it

If privacy rules are blocking your diagnostic AI, we can help you train across sites while each hospital keeps its own data.