Fieldmesh: the network that assumes the network will fail.
Gateways and environmental sensors for hospitals, clinics, warehouses and the back room of a pharmacy, built to store and forward when the connection drops.
Where it earns its keep
Fieldmesh tends to arrive to replace several networks, not to add one.
Four networks, one fabric
Great Lakes Health moved 22,000 devices from four telemetry networks to one Fieldmesh fabric in six weeks.
Sites with no reliable connection
Gateways hold 90 days of readings and reconcile when the link returns, with original timestamps and a delayed flag.
Cold chain
Environmental sensors in fridges and freezers turn a weekly USB download into a continuous record.
Mixed estates
Fieldmesh carries Nexaform devices natively and third-party devices through standard Bluetooth and Wi-Fi profiles.
The family
Two gateway generations in production and a set of sensors that share them.
Fieldmesh G4
Our current gateway for clinical areas: ceiling or wall mounted, powered over Ethernet.
- Bluetooth Low Energy 5.3 and Wi-Fi 6
- Redundant pairing: every device sees two gateways where coverage allows
- 90 days of local buffering
Fieldmesh G3
The previous generation, still in production for estates standardized on it.
- Bluetooth Low Energy 5.0
- Firmware parity with G4 for all clinical features
- Supported until December 2029
Fieldmesh E-series sensors
Temperature, humidity and door sensors for storage, labs and pharmacy.
- Probes for refrigerators, freezers and ultra-low freezers
- Two-year battery, user replaceable
- Calibration certificate with every probe
Fieldmesh Cell
A cellular backhaul unit for sites with no wired network at all.
- LTE-M and NB-IoT
- Runs one site of up to 40 sensors
- Mobile units: syncs when it returns to coverage
Specifications
Current production model. Full detail is in the instructions for use.
| Specification | Value |
|---|---|
| Gateway models | Fieldmesh G4 (current), G3 (in production, supported to 2029) |
| Radios | BLE 5.3, Wi-Fi 6 (G4); BLE 5.0, Wi-Fi 5 (G3) |
| Power | Power over Ethernet (802.3af) or 12 V supply |
| Local buffer | 90 days per gateway, timestamps preserved |
| Device capacity | Up to 120 active devices per gateway |
| Failover | Automatic re-homing to a neighboring gateway |
| Transport | MQTT over TLS 1.3, mutual certificate authentication |
| Deployment | Nexaform-hosted, customer cloud tenancy, or on premises |
| Mounting | Ceiling tile, wall, or DIN rail |
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
Works with
Fieldmesh is the road. These are the vehicles and the dispatch.
Formcloud
Gateway fleet management and data routing.
Fleet analytics
Coverage, uptime and battery forecasting.
Field service
Surveys, installs and replacements on site.
Firmware updates
Current Fieldmesh firmware and its release notes.
Product support
Phone lines, severity levels, and what to have ready.
Recalls and advisories
Every field safety notice and software advisory we have issued.
Planning a site survey?
Every good Fieldmesh deployment starts with a walk around the building. Bring your floor plans and your least trusted inventory.