Biosignals Overview

AnyBio is biosignal infrastructure. Whatever the source - a chest strap, a ring, a smartwatch, a continuous glucose monitor, an EEG headset, or a custom-built sensor - the platform normalizes the stream into a consistent set of biosignals that your application can query, visualize, and act on.

This section documents the biosignal catalog: the canonical list of biosignals AnyBio understands, the metadata each one carries (units, sampling rate, validation ranges, LOINC codes), and the APIs you use to discover and query them.

What a biosignal is

In AnyBio, a biosignal is a typed measurement series with stable identifiers and units. Whether the underlying device emits a 250 Hz ECG waveform or a once-per-minute heart rate value, the platform represents both as biosignals - the difference shows up in the sample rate and the way you consume the stream, not in two different APIs.

Each biosignal has:

• A stable ID and abbreviation (HR, ECG, PPG, SpO2, ...).
• A unit (bpm, mV, Cel, mg/dL, ...).
• A sample rate range (1 Hz for derived vitals; 100-500 Hz for waveforms).
• An optional LOINC code for FHIR interoperability.
• A validation range the platform uses to flag suspect values.
• An emission policy (per-device throttling, quality-aware filtering).

What's in the catalog

AnyBio's biosignal catalog covers vitals, waveforms, autonomic signals, derived rhythms, metabolic data, activity, and sleep. See Catalog for the full reference.

The catalog is data-driven. New biosignals can be added without code changes, and your application discovers them through the API rather than hard-coding identifiers.

Where to go next