Who we serve · Health systems
Device fleets that behave like infrastructure, not like a drawer of gadgets.
Twenty thousand connected devices across a dozen campuses is not a bigger version of twenty devices in a clinic. It is a different problem, and it is the one we build for.
What we hear from clinical engineering teams
These four come up in almost every first conversation, in roughly this order.
Devices arrive faster than anyone can inventory them
Procurement, donations, research grants, and departmental purchases all add equipment. The formal inventory is a lagging indicator, and nobody trusts it enough to plan from.
Telemetry that never reaches the chart
A device measures something, and the measurement stops at a gateway, a middleware box, or an interface nobody owns any more. Clinically it may as well not have been taken.
Firmware updates that need a person and a cart
An update that requires physically touching every device is an update that does not happen, which means the fleet is permanently a version or two behind the one with the fix in it.
Security review as a deployment schedule
A project is ready in March and live in October, and the six months in between are spent answering questions that could have been answered on day one with the right documentation.
What we bring
Six capabilities that exist specifically because of the four problems above.
Fleet management at campus scale
One console for every Nexaform device in the estate, grouped the way your organization is actually structured.
- Device groups by site, unit, or service line
- Staged rollouts with canary groups
- Signed firmware rollback without a site visit
- Automatic discovery of devices already on the network
Clinical integration
Data reaches the record through the interface your organization already runs, not through a new one.
- HL7 v2.5.1 ADT and ORU
- FHIR R4: Observation, Device, Patient, Encounter
- SMART on FHIR launch for in-context views
- Configurable mapping, versioned and reviewable
Biomed and clinical engineering workflows
Built around how the department already works rather than asking it to work differently.
- Asset records that reconcile against your CMMS
- Preventive maintenance scheduling by device group
- Calibration records held per device, per serial
- Failure analysis returns handled through one route
Security and lifecycle
The documentation exists before you ask for it, because the review is going to ask anyway.
- Software bill of materials per firmware version
- IEC 81001-5-1 aligned development process
- MDS2 forms for every shipping device
- Coordinated vulnerability disclosure, published
Service and uptime
Gateways fail. What matters is whether the fleet notices and what happens next.
- Gateway redundancy with automatic failover
- Store-and-forward through network outages
- Field service scheduling inside the console
- Named support engineer above 5,000 devices
Analytics that answer operational questions
Utilization, battery health, and failure patterns across the whole estate rather than per device.
- Fleet health and battery replacement forecasting
- Utilization by unit and by device family
- Export to your own warehouse, scheduled
- No per-query charging
Integration surface
What a technical review usually wants to establish in the first hour.
| Capability | What we support today |
|---|---|
| Clinical messaging | HL7 v2.5.1 (ADT, ORU, MDM), FHIR R4 |
| FHIR resources | Observation, Device, DeviceMetric, Patient, Encounter |
| Device transport | MQTT over TLS 1.3, mutual certificate authentication |
| Identity | SAML 2.0 and OIDC for console access, SCIM 2.0 for provisioning |
| Audit | Immutable event log, exportable, 7-year retention by default |
| Deployment | Nexaform-hosted, customer cloud tenancy, or on-premises for Fieldmesh and Formcloud |
| Data residency | United States, Canada, EU, or United Kingdom, selected per tenancy |
| Firmware provenance | Per-version SBOM, signed build hashes, published advisories |
| Downtime handling | 90 days of local buffering per gateway, timestamps preserved on reconciliation |
We thought we were buying a network. What we got that we did not expect was an honest list of what we own.
Dr. Aisha Bennett
Chief Medical Information Officer, Great Lakes Health
Products that show up in this work
The same four families, put together differently depending on what the deployment has to survive.
Start with your estate, not our catalog
The useful first conversation is usually about what you already have and what it is doing, not about what we sell. Bring your inventory, however untrustworthy you think it is.