IBM Healthcare Belgium

Innocens BV

Risk Management

Innocens BV needed a faster, more reliable way to detect signs of late-onset sepsis in vulnerable newborns because NICU teams were relying on manual interpretation of many data sources and could miss critical changes for hours.

Can help detect sepsis hours faster than medical staff
Can identify a significant amount of severe sepsis cases
approximately one in five preterm neonates born under 3.3 pounds (1,500 grams) experience late-onset sepsis

Reported impact

Business outcome

The Innocens platform gave clinicians a path to detect severe sepsis earlier, preserve patient-data locality, and build a reusable AI foundation for broader neonatal decision support.

  • Productivity Improvement
  • Risk Reduction

Solution

Innocens BV worked with IBM to turn a decade of neonatal intensive care data into an explainable clinical decision-support platform. Using IBM Watson Studio on IBM Cloud Pak for Data, the team trained machine learning models on monitoring signals, reports, diagnoses, and patient-record data from Antwerp University Hospital. The implementation was designed around three architectural pillars identified by the team: a predictive model, an interpretable user interface, and a robust edge-oriented architecture. Explainable AI features in Cloud Pak for Data were used to help caregivers understand why the models were flagging risk, while federated learning let the models evolve without moving raw patient data outside the hospital. Parameters could move through the cloud, but raw NICU data stayed on premises behind hospital firewalls, creating a privacy-preserving operating model for continuous sepsis monitoring.

Data flow

Monitoring signals, reports, diagnoses, and electronic patient-record data remain inside the hospital environment, Watson Studio models analyze the patterns through Cloud Pak for Data, and federated-learning parameters move in the cloud while clinicians receive explainable risk insight locally.

Solution architecture

3 components · 3 layers
  1. Compute
    • IBM Watson Studio Trains and tests the machine learning models used to detect bloodstream infections in NICU patients.
  2. Serving
    • IBM Watson Machine Learning Supports operational deployment of the predictive models as Innocens prepares to expand to other hospitals.
  3. Governance
    • IBM Cloud Pak for Data Provides the data and explainable-AI platform used to build, run, and manage the models.

Architecture clues

  • Explainable AI capabilities were used to help caregivers understand model output.
  • The architecture brings computation close to patient-room data sources to reduce latency and improve privacy.
  • The implementation uses federated machine learning so raw clinical data stays on premises.

Evidence from the source

"Can help detect sepsis hours faster than medical staff"
"Innocens BV used IBM Watson Studio to train its solution's machine learning models"
"The UZA NICU is a highly digitized environment with multiple data sources"
"The raw data will remain on premises. Federated machine learning does this without moving the data."
Transparency Evidence & methodology 66/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value66/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Innocens BV customer story

    First-party
    https://www.ibm.com/case-studies/innocens-bv
    Source type
    Vendor-published customer story
    Published
    Apr 16, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.