Healthcare / Connected sensor, AI signal analysis and cloud

Sensocor: from a Bluetooth heart-signal sensor to a doctor's web portal

Sensocor case study: how Indeema delivered medical device software development for a heart-signal sensor, from firmware to doctor portal.

Sensocor sensor unit in front of a laptop showing a patient-details page with three indicator graphs, and a phone showing three live signal traces.

The opportunity

A sensor without a product around it

Monitoring Life had a heart-signal sensor and a basic Android app. There was no cloud, no doctor portal and no way to update units once assembled. The goal grew from an Azure connection to the full path from sensor to doctor.

The solution

One connected path

Indeema built every layer as one system: firmware, patient app, cloud, AI analysis and the doctor portal.

01Sensor
02Patient app
03Cloud
04AI analysis
05Doctor portal

Diagram of a hand on the sensor unit, a Bluetooth Low Energy link to a phone showing signal traces, a cloud, and a laptop with the Sensocor doctor portal.

The impact

What changed for the business

Recordings stayed on a basic appRecordings reach a doctor portal
Fixing firmware meant opening the unitUpdates delivered through the app
Doctors reviewed raw signals aloneAI highlights potential risks for review

AI highlights potential risks; the doctor makes the clinical call.

Engineering judgement

Decisions that shaped the product

Bluetooth Low Energy instead of Bluetooth Serial

BLE addressed data-transfer congestion between the unit and the app and allowed a protected pairing process.

Native ESP-IDF instead of Arduino

Moving the ESP32 firmware to ESP-IDF was chosen for stability and to leave room for later firmware development.

Firmware updates through the app

A BLE OTA mechanism lets the app fetch firmware images from Azure Blob Storage and update units in the field; the proposed USB programming path covers bench updates.

Start and stop measurements from the app

BLE commands let users start and stop measurements, so the unit records only when needed and conserves battery.

Testable backend structure

The .NET backend uses an Onion architecture with a Chain of Responsibility pattern, documented REST endpoints and an integration test that checks the data flow after each rebuild.