Technical FAQ

What protocols does BioT support for device communication?

BioT uses two communication channels between devices and the cloud:

• MQTT for real-time bidirectional communication — sending measurements, statuses, and telemetry from the device, and receiving commands and configuration updates from the cloud. All MQTT traffic is encrypted with AES-256 over TLS 1.3.
• HTTPS for device-initiated requests such as firmware downloads, file transfers, and image uploads.

BioT provides device SDKs built on these protocols, so you can work with either the SDK or any standard MQTT library directly. See the Device Integration Guide for implementation details.

How do I connect my device to BioT?

BioT provides device SDKs for devices running an operating system (Linux, Android, RTOS with networking). For firmware on bare-metal hardware, use the REST API or MQTT documentation directly. The typical integration flow is:

1. Register the device in the BioT Console or via API
2. Configure the device data model (entities, attributes, measurements)
3. Implement the SDK or API calls in your firmware
4. Test with the BioT sandbox environment

Most device onboarding completes in less than a day. See "Hello World" with BioT to get started.

What data formats does BioT accept?

BioT accepts JSON payloads over MQTT and HTTPS, time-series measurement data, and files and images via HTTPS. MQTT is optimized for small, frequent payloads (sensor readings, vitals, telemetry). For larger transfers such as raw data files, images, and video, HTTPS is used instead.

The flexible data model lets you define custom entities and attributes to match your device's output. Time-series data is stored in a purpose-built analytics database accessible via SQL. For external system integration, BioT supports FHIR natively and provides open REST APIs for any data exchange format.

How does BioT's data model work?

BioT uses a configurable entity-relationship model. You define entities (devices, patients, organizations, caregivers), their attributes (custom fields with data types), and the relationships between them. Measurement templates define the structure of time-series data from devices. All of this is configured through the BioT Console (no-code) or via the Management API (pro-code). See System Concepts for the full data model reference.

How does ABAC (Attribute-Based Access Control) work in BioT?

BioT's access control system works in two layers. First, Static Access Control determines whether a user is authorized to make a request at all. Then ABAC is evaluated to control exactly which data the user can access or modify. For example, ABAC prevents patients from creating other patient profiles and restricts non-caregiver users from accessing PHI they shouldn't see.

ABAC policies are enforced by a global service that monitors all incoming API traffic. Every request is scanned before data is accessed or returned. BioT ships with a default ABAC implementation that covers most standard use cases, and rules can be customized to match your specific access requirements. See Attribute Based Access Control for full reference.

Can I run my own algorithms on BioT?

Yes. BioT's Plugin API enables you to deploy and execute proprietary algorithms on any BioT module. Common use cases include:

• Running AI/ML models on incoming device data
• Implementing clinical decision support logic
• Processing measurement streams for derived metrics
• Triggering alerts based on custom criteria

Your algorithms run on BioT's compliant infrastructure with full PHI protection and ABAC-controlled data access. BioT supports virtually any coding language. See What are BioT Plugins? for implementation details.

How do I integrate BioT with EHR systems?

BioT provides native FHIR support and pre-built EHR/EDC connectors. You can push device data to electronic health records, pull patient context into BioT workflows, or set up bidirectional sync. For EHR systems that support FHIR R4, integration is configuration-based. For proprietary interfaces, use BioT's open REST APIs to build custom connectors.

What analytics capabilities does BioT provide?

BioT includes a purpose-built time-series analytics database optimized for medical device data. You can query data using SQL, connect BI tools (Tableau, Power BI, Grafana) for visualization, or access raw data via the Analytics API. All queries respect ABAC policies and PHI protection rules. See Integration with the BioT Analytics DB for capabilities and query examples.

How do I manage OTA firmware updates through BioT?

BioT's device lifecycle management includes OTA update orchestration. You upload firmware packages to BioT, define rollout policies (target devices, scheduling, rollback criteria), and monitor deployment status in real time. The platform handles delivery, verification, and reporting. Updates can be targeted to individual devices, device groups, or entire fleets. See Over-the-Air (OTA) Update Module for details.

What is the Developer Studio?

The Developer Studio is BioT's development environment with three modes: no-code (visual templates and drag-and-drop configuration), low-code (SQL queries, rule builders, and workflow editors), and pro-code (full API access in any programming language). It allows you to build custom modules, extend platform capabilities, and tailor BioT to your specific clinical workflows without modifying core platform code.

How does BioT handle multi-tenancy?

BioT is multi-tenant with full data isolation. Each manufacturer operates in their own tenant with isolated data storage, separate access controls, and independent configuration. Within a tenant, you can create multiple organizations (hospitals, clinics, care centers) with their own user hierarchies and data boundaries. ABAC ensures that data never leaks between organizational contexts.

What environments are available for development and testing?

BioT provides separate development and production environments. Development environments are available for building and testing integrations without affecting production data or workflows. You get full API access, a sandbox console, and test device simulators. Promote to production when ready.

Where is BioT hosted?

BioT runs on AWS with multi-region availability in the US, EU, and Asia. Data residency is configurable per deployment to meet GDPR and local regulatory requirements.