The platform your analyzers run on.
FluxOS connects every Search Analyzer to one cloud: set up instruments, push new assays, review results, and hand them off to an EMR or LIMS — from any device.
Diagnostics don't end when the run does.
A result still has to be reviewed, released, recorded, and traced — and the instrument that produced it still has to be maintained. FluxOS is where all of that happens.
Fleet management
Every analyzer in every location on one screen — status, utilization, consumable stock, and who ran what.
Result delivery
Results land in FluxOS the moment a run finishes, ready to review, release, or route onward automatically.
Remote assay deployment
A new assay is a file. Push it to one analyzer or a whole fleet without a firmware patch or a service visit.
Preventative maintenance
Instrument telemetry feeds models that flag a drifting analyzer before it fails a run rather than after.
Roles and access
Operators, reviewers, and administrators get scoped permissions per site, with every action attributable.
Works on any device
The same interface on a PC, a tablet at the bench, or a phone between rooms — nothing to install.
Fits the systems your site already runs.
Point-of-care testing only saves time if the result reaches the record without someone retyping it. FluxOS is built to hand results off cleanly.
EMR and LIMS
Release results into the record system your site already runs, so Fluxergy testing doesn't create a second inbox.
- HL7 and FHIR interfaces
- Bidirectional order and result flow
- Per-site routing rules
API access
Pull results, instrument state, and run metadata into your own systems rather than exporting spreadsheets.
- REST API
- Webhook notifications
- Structured run metadata
Multi-site operations
Group analyzers by clinic, region, or study arm, and report across the whole network from one place.
- Site and group hierarchies
- Cross-site reporting
- Centralized assay rollout
New assays arrive as a file, not a service visit.
Because the analyzer's capabilities are defined in software and on the card, adding a test to a fleet is a deployment — not a hardware revision or a technician dispatch.
Built for patient data from the start.
Handling protected health information is a design constraint on the platform, not a policy layered over it after the fact.
HIPAA-compliant
Built and operated to handle protected health information as a first-class requirement.
Encrypted end to end
Data is encrypted in transit from the analyzer and at rest in the cloud.
Auditable by design
Every run, release, and configuration change is recorded against a user and a timestamp.
Traceable results
Each result carries its analyzer, card lot, operator, and assay version with it.
Specifications.
A working summary of the platform. Integration documentation, security detail, and compliance artifacts are available from our team.
- Delivery
- Cloud-hosted; no on-premise server required
- Clients
- Desktop browsersTabletsSmartphones
- Instrument connectivity
- Wi-Fi, Ethernet, or cellular from the Search Analyzer
- Integrations
- EMR and LIMS via HL7 and FHIRREST APIWebhooks
- Assay management
- Remote deployment of new and updated assays as files
- Fleet management
- Status, utilization, telemetry, and preventative-maintenance alerts
- Access control
- Role-based permissions scoped per site and per group
- Compliance
- HIPAA-compliant with encryption in transit and at rest
- Audit trail
- Full history of runs, releases, and configuration changes
See FluxOS running a fleet.
We'll walk through instrument management, assay deployment, and the handoff into your EMR or LIMS using a setup that matches how your sites are organized.