Healthcare
What changes when a connected product has to work in healthcare
A connected product in a healthcare setting answers to more than its specification: who uses it, what data it handles, what happens when the connection drops, and who decides what its data means. Indeema engineers the product around those answers, and is clear about where engineering responsibility ends.
Custom healthcare software development for connected products and the tools around them. This is not a page about hospital information systems.
The setting
A care setting is not a lab
The same connected product meets different conditions depending on where it is used.
Worn, held or set down: each device meets its own conditions.
- HOME
At home
No one from the product team is present. A household’s phone and network carry the product, and the person using it may be unwell, older or new to technology.
- CLINIC
In a clinic or ward
Units are shared between people, staff have little time, and other systems are already in place. Whatever is added has to fit around them.
- FIELD
In the field
Care is delivered where the connection comes and goes. The product keeps working, and decides what it holds until it can reconnect.
- REMOTE
At a distance
Remote care adds video, scheduling and records questions of its own. They are covered on the Telemedicine applications page.
Five things change
Healthcare changes five things about a connected product
For each, the ledger separates what engineering settles from what stays with the product owner and qualified advisers.
INTENDED USE
What changes
What the product is for decides which rules apply. Two near-identical products can sit on opposite sides of a regulatory line.
What engineering settles
Asks for the intended use first, writes it down, and draws the architecture to it.
Stays with the product owner and qualified advisers
What the product is for, in which markets, and what that means for documentation and testing.
PEOPLE
What changes
One product serves several people at once: the user, a carer, a clinician, an administrator.
What engineering settles
Roles, permissions and flows for each, built for people who may be unwell, rushed or unfamiliar.
Stays with the product owner and qualified advisers
Who the users are in the real service, how they are trained, and how clinical work flows.
DATA
What changes
Health data is personal by default. Who sees what, and where it is held, become design decisions.
What engineering settles
Separate stores where the design needs them, access rules, consent held as a state the application respects, deletion paths.
Stays with the product owner and qualified advisers
Privacy obligations by country, consent wording, retention periods, and what counts as health data.
CONDITIONS
What changes
Homes, clinics and the field are not labs. Connections drop and devices change hands.
What engineering settles
What the product does when data is late, partial or missing, what it keeps until it can send, and how a user recovers.
Stays with the product owner and qualified advisers
Acceptable operating conditions, and what to do clinically when data is missing.
CHANGE
What changes
A fix or a feature on a deployed product is a decision, not a routine release.
What engineering settles
A way to update what is deployed, and a record of what the engineering did.
Stays with the product owner and qualified advisers
Whether a change needs review, the quality system it sits in, and release approval.
Boundary Indeema does not decide the right-hand column.
Decisions that arrive late
Some decisions are expensive to settle after the architecture
These four are a matter of engineering judgement. They are not results from a past project.
Intended use, after the data model
If the purpose is written down late, storage, roles and logging may have to be redrawn.
Data separation, after the storage design
Separating personal details from other records is far easier before the storage design is in use.
Offline behaviour, after the app flows
A product that must work without a connection has to save, queue and recover. Adding that later touches every screen.
A way to update, after the hardware is sealed
A unit that cannot be reprogrammed once assembled turns every later fix into a replacement.
The boundary
Indeema engineers the product. The owner and advisers settle the rest
Two lists, kept apart on purpose.
The boundary is agreed by people, early.
Indeema engineers
- Device behaviour
- The apps people use
- How data is handled and kept apart
- Interfaces to other systems
- A way to update what is deployed
- Tests of what Indeema builds
Stays with the product owner and qualified advisers
- What the product is for
- The clinical meaning of any figure
- Medically meaningful thresholds
- The regulatory route
- Privacy obligations
- Evidence of clinical performance
In one device project, the client defined the figures shown; Indeema built how they are carried and displayed. The device path has its own page: IoMT & Healthcare Monitoring
Whether a product is regulated depends on its intended use. That is settled with qualified regulatory advice before technical scope.
What Indeema can own
Parts of the product Indeema can take on
IoT healthcare software development, as Indeema practises it, is the engineering around a connected product. Each part changes in a care setting.
The unit
How it behaves when a connection drops, and how it is updated.
Hand over Embedded & Firmware Hand over Hardware & Electronics
The apps
Patient-facing and clinician-facing apps are built for different people on different devices.
The data
Where personal data is held, kept apart and removed.
The whole product
When device, apps and cloud have to behave as one, healthcare changes how they are scoped.
Hand over IoT Product Engineering Hand over Connected Product Engineering
What this has looked like
One example, and what Indeema owned in it
The client and the programme are not named, and no results are shown.
The sign-in and the saved forms, as a person using the app sees them.
- DATA · CONDITIONSField data-collection software for psychologists
Psychologists working in places with an unreliable connection needed to collect client data on tablets.
- Indeema owned
- Indeema developed the software: an Android application and two servers.
- What changed
- Client data can be collected and sent without a stable connection. Personal details are kept in one store and notes about the client’s condition in another. Data entry for a client begins only after consent is recorded.
Boundary Not claimed here: diagnosis or assessment, clinical results, a security level, legal compliance, hospital information systems, record integrations or remote-care platforms.
Where to start
Start with the intended use and the people around the product
IoMT & Healthcare Monitoring
If the question is how a health sensor’s data reaches the people who view it.
Product Discovery & Technical Strategy
When the intended use and the boundaries are not yet written down, start by scoping them.
IoT Product Engineering
When the question is the whole product: device, apps and cloud together.
Bring us
- The product, and where it will be used
- Who will use it, and who administers it
- What has been decided about its intended use