Seven device families, one platform underneath them.
Everything we make shares a firmware base, a fleet platform, and the same idea about who it is for: the clinician, the technician, and the person wearing it.
Device families
Hardware that sits on a person, in a ward, on a bench, or in a back room.
Axon Sense
Wearable sensing patches for continuous ECG, respiration, temperature and activity outside the clinic.
Corta
An insertable cardiac monitor and the bedside reader that carries its data home to the care team.
Fieldmesh
Gateways and environmental sensors that carry device data across a campus, a county, or a cold chain.
Lattice bench systems
Instrument-grade acquisition benches for research labs and device test teams.
Nexa Edge
Hubs that gather readings from several devices in a home, an ambulance, or a rural clinic.
Accessories and consumables
Adhesive carriers, charging cradles, probes, leads, mounts and calibration fixtures.
Legacy devices
Earlier generations, what support they still get, and when it ends.
Platforms and data
The software that keeps a fleet current and gets its data where it is needed.
Formcloud
Fleet management, staged firmware, signed rollback, and data routing for every device we make.
Lattice OS
The embedded operating system our devices run on, assessed to IEC 62304 Class C.
HL7 and FHIR integrations
Device data into the clinical record through the interfaces you already run.
Fleet analytics
Battery health, utilization and failure patterns across the whole estate.
Security and compliance
SBOMs, MDS2 forms, disclosure policy and the documentation a review asks for.
API and developer docs
REST and MQTT interfaces, SDKs, a sandbox, and the research data dictionary.
How the pieces fit
Most deployments use three or four of these together. A typical home monitoring program looks like this.
A sensor on the person
An Axon Sense patch or a Corta monitor records continuously and holds data locally when it has nowhere to send it.
A hub or gateway nearby
A Nexa Edge hub at home or a Fieldmesh gateway on a ward picks the data up and forwards it, with its original timestamps.
Formcloud in the middle
Formcloud knows which device belongs to which program, keeps firmware current, and routes data by rule.
The record at the end
Observations land in the clinical record through HL7 v2 or FHIR R4, mapped the way your interface team already works.
Not sure which family fits?
Tell us what you are trying to measure and where. A specialist will tell you which devices fit, and which of ours do not.