Roadmap

Instrument Interface Roadmap

Each lab has its own instrument mix. Interfaces are scoped per deployment, validated by the customer, and mapped per instrument — not bundled out of the box.

← Back to lims.bot

How Instrument Interfaces Work Today (Demo)

Demo Mode

  • →The current LIMS BOX demo uses mock assets and Field Scout workflow examples — not live instrument data.
  • →No real instrument results are captured or transmitted in the demo environment.
  • →Field Scout demo tags use mock NFC identifiers linked to simulated lab assets.

This demo exists to show how LIMS BOX workflow demonstrations work — not to represent a production-ready instrument integration. Real instrument work is scoped separately per deployment.

How They Work in a Real Deployment

In a production LIMS BOX deployment, instrument interfaces are scoped during the configuration phase. Each interface is mapped to the specific instrument model, data format, and result structure your lab uses. This work requires customer authorization and is validated by the customer before going live.

Per-Instrument Scoping

Every instrument integration is defined per deployment. There is no one-size-fits-all connector — each lab's instrument mix is mapped individually.

Customer Authorization Required

Instrument interface work begins only after the customer authorizes the scope, instruments, and data flows in writing.

Customer Validation

After configuration, the customer validates each interface — confirming that results are captured correctly before production use.

Data Format Mapping

LIMS BOX maps each instrument's output format (ASTM, HL7, CSV, proprietary) to the SENAITE data model per instrument.

Field Scout — Discovery and Asset Tracking

Field Scout is an authorized asset discovery and inventory tracking tool. It uses NFC tags (NTAG215) affixed to instruments, consumables, and bench locations to enable fast check-ins, inventory status updates, and chain of custody logging — without requiring a LIS plugin or network reconfiguration.

Important clarification

Field Scout and the Flipper Zero integration are authorized asset discovery and tracking support tools — not network scanning, security testing, or unauthorized access tools. Every tag interaction is an authorized, lab-managed workflow. No unauthorized network access, no security probing, no data interception.

See Field Scout in action

Per-Instrument Mapping Process

  1. 01

    Customer provides an instrument list with model numbers and current data output formats.

  2. 02

    LIMS BOX team reviews each instrument and scopes the interface work required.

  3. 03

    Customer authorizes the scope in writing before any interface development begins.

  4. 04

    Interface is built and tested in a staging environment using the customer's actual instrument output.

  5. 05

    Customer validates the interface end-to-end before production use.

  6. 06

    Interface goes live. Customer maintains validation records.

Discuss your instrument needs

Questions? info@lims.bot