IBM Healthcare Finland

Benete

Real-time Analytics

Benete needed a way to turn large volumes of BeneCare assisted-daily-living sensor data into usable caregiver insights without forcing nurses and care teams to manually interpret dashboards and create summaries.

30 minutes of daily time savings per nurse
90% reduction in patient data interpretation time, down to 1 minute from 10
Accurate, tone-appropriate and on-demand translation of summary reports into 5 languages
Easy-to-consume summary reports in less than 5 seconds

Reported impact

Business outcome

Benete gave caregivers near-instant, multilingual summaries of client conditions, sharply reduced the time needed to interpret patient data, and improved the ability to deliver preventive care while serving more elderly clients efficiently.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

Benete worked with IBM Client Engineering to add an LLM-based summarization layer to its BeneCare elder-care platform. IoT sensors already captured activity, movement, sleep, hygiene, and food-preparation signals for elderly clients; IBM watsonx.ai was introduced to convert that raw operational data into concise care summaries and multilingual reports. Benete created prompt templates in watsonx.ai, used IBM Cloudant to store structured sensor findings and generated summaries, and tracked model development with Jupyter Notebook plus AI factsheets in IBM watsonx.governance. Llama and Mistral models were evaluated and then deployed on watsonx.ai as endpoints that transform the incoming care data into readable insights integrated back into BeneCare. This architecture preserves the continuous monitoring workflow while automating the most time-consuming interpretation step for caregivers.

Data flow

IoT sensors feed BeneCare with assisted-daily-living data, Benete stores structured findings in IBM Cloudant, prompt templates in IBM watsonx.ai call Llama or Mistral endpoints to generate summaries and translations, and the resulting outputs are pushed back into BeneCare dashboards for caregivers and nurses.

Solution architecture

5 components · 3 layers
  1. Compute
    • IBM watsonx.ai Hosts the prompt-driven LLM endpoints that turn care data into readable summaries and translations.
    • Llama Provides one of the large language models Benete evaluated and deployed for summary generation.
    • Mistral Provides an alternative large language model Benete deployed to keep the summarization capability model-agnostic.
  2. Storage
    • IBM Cloudant Stores structured IoT-derived findings and the generated summaries for efficient retrieval and querying.
  3. Governance
    • IBM watsonx.governance Tracks AI factsheets and evaluation artifacts so Benete can monitor prompt and model behavior.

Architecture clues

  • Benete kept the summarization feature model-agnostic after testing both Llama and Mistral.
  • Prompt templates were tracked with AI factsheets for model evaluation and cost monitoring.
  • The BeneCare dashboard continuously monitors key care metrics and generates data 24x7.

Evidence from the source

Benete saved valuable time in documentation procedures, enabling caregivers to focus more on patients.
By creating prompt templates in watsonx.ai, Benete sourced variables, data and tasks from IBM Cloudant
Summary reports, which were previously generated and interpreted manually, are now instantly generated in less than 5 seconds
These prompts were then deployed in watsonx.ai to become endpoints where data is transformed into understandable insights and integrated into BeneCare.
there’s a 90% reduction in the time taken to understand client data
Transparency Evidence & methodology 100/100 reference value · 92% confidence · 2 sources

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 value100/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 specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/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

    Benete customer story

    First-party
    https://www.ibm.com/case-studies/benete
    Source type
    Vendor-published customer story
    Published
    May 12, 2025
    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
  2. LinkedIn

    Benete | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/benete/

    The public Organization JSON-LD for Benete includes numberOfEmployees value 4; 4 maps to SMB under the enrichment thresholds.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

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