IoMT & Healthcare Monitoring
Turn a connected health sensor into a system your clinicians can view
In the Internet of Medical Things, a sensor that measures something about a person is the easy part. Indeema engineers the route its readings take: the pairing with a phone, the measurement, the hand-off to the cloud, the portal where the data is viewed, and the updates that keep the device current. Clinical meaning stays with you and your advisers.
See the reading pathWhere this begins
Most connected health devices start from one of these
IoMT software development usually begins from a situation like these. They are common starting points, not claims about a past delivery.
The sensor works, but nothing behind it can hold or show what it measures.
STORE · VIEWThe prototype talks to one phone over a serial link, and the link struggles with the data.
PAIR · RELAYThe unit cannot be reprogrammed once it is assembled.
UPDATEThe app is dated, and pairing a new unit is awkward.
PAIRThe figures to show are defined, and there is nowhere to show them.
VIEW
The reading path
Five changes, from the device to the view
Each station changes something in your system. Interpreting the reading is not one of them. Two people sit at the ends of the path: the one who carries the device, and the one who looks at the data.
PAIR
A device and a person’s phone are bound together: discovery first, then protected pairing.
Hand over Embedded & FirmwareCAPTURE
The sensor unit measures when it is told to. The phone can start and stop a measurement, which spares the battery. Sampling rate and link throughput are weighed together, because they decide what the phone can carry.
RELAY
The phone app sends the collected data files on to the cloud, so the phone is part of the system and not only a screen.
Hand over Applications & ExperienceSTORE
The cloud holds the files and the key figures for each signed-in user.
Hand over Cloud & Connected SystemsVIEW
A web portal shows the data and the key figures to the clinician. The figures are the ones you define.
UPDATE New firmware travels back the same way, from cloud storage through the phone to the device. It carries no readings.
Whose number is it?
The engineering path ends at the view
You decide what each figure is and what it means. Indeema builds the path that carries the figures and the view that shows them.
You define
Which figures are shown, and how each one is calculated.
Indeema builds
The route the readings take, and the portal that shows them.
Outside the path
Clinical interpretation, medically meaningful thresholds, clinical action and regulatory status remain outside this engineering path.
Whether a product is regulated depends on its intended use. Settle that with qualified regulatory advice before technical scope.
Healthcare industryKeeping the device current
The device stays updatable after it ships
A unit that cannot be reprogrammed once assembled is a common trap. Updates run the path in reverse, from the cloud to the device.
- Cloud storage
- Phone app
- Sensor unit
- ReprogramThe unit can be programmed over USB without opening its enclosure.
- DeliverNew firmware is held in the cloud, fetched by the phone app and sent to the unit over the air.
- CheckA data-flow test runs after each rebuild, so an update does not break the route.
The device side is Embedded & Firmware . The service side is Cloud & Connected Systems .
What this has looked like
One example, and what Indeema owned in it
The client and the product are not named, and no results are shown.
- PAIR · CAPTURE · RELAY · STORE · VIEW · UPDATEHeart-signal sensor unit, phone app, cloud and clinician portal
A medical-device startup had a heart-signal sensor unit and a phone app that read its serial stream. It had no back end, no portal and no way to reprogram the unit once assembled.
- Indeema owned
- The unit’s firmware and hardware changes, the phone app, the cloud back end and the clinician web portal, from requirements onward.
- What changed
- The unit moved to Bluetooth Low Energy with protected pairing and can be updated over the air. The app starts and stops measurements and sends data files to the cloud. Key figures are held in a database and shown in the portal.
- The hard part
- Aligning the specifications for the device, the phone app and the web portal, so that the parts joined up.
- The team
- Hardware, embedded, mobile, web, design, QA and project management in one team.
Boundary This is one example. The client defined the figures shown. Signal quality, results and regulatory status are not claimed.
Where to start
Start with the path your readings take
Product Discovery & Technical Strategy
Scope the reading path, and where the clinical boundary sits, before anything is built.
IoT Product Engineering
Have one team own the device, the phone app, the cloud and the portal.
Connected Product Engineering
The same one-system discipline, for products outside health.
Bring us
- The device and what it measures
- Who views the readings, and where
- Who defines the figures