Healthcare
Facilities and data, not clinical systems
Our work in this sector concerns the building and the data around it — power, cooling, water, cold chain, asset tracking and access. It does not extend to clinical systems or medical devices.
Context
Industry context
What shapes technology decisions in this sector.
This page is about facilities and information handling. Healthcare providers run estates whose conditions have to hold continuously rather than on average, and data whose confidentiality obligations shape system design before implementation begins.
Cold chain is the clearest example. A temperature that stays within tolerance on a daily average can still have left tolerance for an hour, and only continuous monitoring distinguishes the two.
The rest is ordinary infrastructure under unusual continuity expectations: power, cooling, water and access systems supporting services that cannot pause while something is repaired.
Constraints
Key operational challenges
The conditions any solution here has to work within.
- Cold-chain and environmental conditions that must hold continuously, not on average.
- Building systems — power, cooling, water — that support services which cannot pause.
- Patient-related data with confidentiality obligations that shape system design.
- Equipment and consumables that need to be traceable.
Capabilities
Relevant ZouhThings capabilities
What we can bring to this sector, stated as capability rather than track record.
Environmental and cold-chain monitoring
Can support continuous monitoring of temperature and humidity in storage areas, with alerting when a reading leaves a configured range.
Building systems visibility
Designed for bringing power, cooling, water and generator status into one operational view rather than several panels.
Asset and consumable traceability
May enable tracking where equipment and stock are, which is a logistics question rather than a clinical one.
Data handling and access control
Relevant where confidentiality obligations require access to be role-based, auditable and revocable by design.
Solutions
Relevant solutions
Solution areas that apply here. Each links to how it is delivered.
Platforms
Relevant platforms
Platforms that would apply to this sector.
- thethings.io
Applications
Example use cases
Possible applications, to show the shape of the work.
Cold-chain condition monitoring
Possible use cases include continuous temperature monitoring of storage with an alert before a threshold is breached rather than after.
Facility utilities monitoring
Can support monitoring power quality, water tanks, cooling plant and generator readiness across a site.
Equipment location and stock visibility
May enable knowing where movable equipment and consumables are, reducing time spent searching rather than treating.
Access and occupancy visibility
Designed for surfacing access events and occupancy in non-clinical areas, where that supports facilities and security operations.
These are possible use cases, described to illustrate what the technology can support in this sector. They are not descriptions of completed work, and none should be read as a reference. Where a confirmed project exists, it will be named and linked under Related projects. Nothing here is a medical or clinical claim: every application listed concerns facilities, environmental conditions, logistics or data handling, and none describes a medical device, a clinical function or an effect on care.
Security
Security considerations
What has to be decided early rather than added later.
Confidentiality obligations first
Access, retention and audit decided before implementation, because data obligations in this sector shape architecture rather than follow it.
Separation from clinical networks
Relevant because facility monitoring must not share a path with clinical systems; segmentation is a design requirement, not a hardening step.
Role-based, revocable access
Designed so access follows a role and can be withdrawn immediately, in an environment with high staff turnover and shift working.
Auditability of readings
Can support a defensible record of what a sensor reported and when, which is what makes a condition log worth keeping.
This describes how we approach security in this sector. It is not a claim to hold any specific certification, accreditation or compliance attestation — where one exists, it will be named. It is also not a claim of compliance with any medical-device or health-data regulation, and nothing here describes a clinical or regulated medical function.
Integration
Integration considerations
Where the difficulty usually sits in this sector.
Working alongside building management
Designed for taking data from installed building management and refrigeration systems rather than replacing them.
No interface to clinical systems
This scope deliberately excludes clinical and medical-device systems. Any such integration would be a separate question requiring people we do not have on this project.
Continuity during change
Relevant because a service being upgraded cannot pause, so new and installed systems run alongside each other for a period.
Named ownership for alerts
A cold-chain alert with no named recipient is not configured, whatever the platform reports.
Evidence
Related projects
Confirmed work in this sector, where any is published.
No project is published for this sector yet. When one is confirmed and approved for publication, it will appear here — so an empty section means exactly that, rather than work we cannot discuss.
Next step
Discuss a requirement in this sector
The useful conversation is usually about a specific asset, site or corridor rather than the sector in general.