AnyBio

Catalog

The full list of biosignals AnyBio supports, with units, sample rates, and LOINC codes.

This is the canonical list of biosignals AnyBio supports today. Each row is a stable contract: the abbreviation, unit, and LOINC code are guaranteed to remain consistent across releases.

Vitals

SignalAbbrUnitSample RateLOINCValidation
Heart RateHRbpm1 Hz8867-420-300
Respiratory RateRR/min1 Hz9279-14-60
Blood PressureBPmmHg1 Hz--
Body TemperatureTEMPCel1 Hz8310-530-45
Oxygen SaturationSpO2%1 Hz59408-50-100

Waveforms

SignalAbbrUnitSample RateLOINCValidation
ElectrocardiogramECGmV250-500 Hz--
PhotoplethysmogramPPGAU100-250 Hz--

Autonomic & derived

SignalAbbrUnitSample RateLOINCValidation
Electrodermal ActivityEDAuS1 Hz-0-100
Heart Rate VariabilityHRVms0.2 Hz80404-70-500

Metabolic

SignalAbbrUnitSample RateLOINCValidation
Glucose (CGM)GLUmg/dL1 Hz41653-720-600

Activity & sleep

SignalAbbrUnitSample RateLOINCValidation
StepsSTEPSsteps/day1 Hz55423-80-100,000
Sleep DurationSLEEPmin1 Hz93832-40-1,440
Calories BurnedCALkcal/day1 Hz41981-20-10,000
Active Zone MinutesAZMmin/day1 Hz-0-1,440

Field reference

Every biosignal entry in the catalog carries the following fields:

FieldTypeDescription
idintegerStable numeric identifier. Used in observation queries and stream metadata.
namestringHuman-readable name (e.g., "Heart Rate").
abbreviationstringShort identifier used in UIs and SDK code (e.g., "HR").
unitstringUCUM-aligned unit string (e.g., "bpm", "mV", "Cel").
loinc_codestring | nullLOINC code for FHIR interoperability, where one exists. See FHIR Mapping.
signal_typestringCategory: "Vital Signs", "Waveform", "Autonomic", "Activity", "Sleep", "Metabolic", "Derived".
throttle_secondsintegerMinimum interval between persisted observations from the same device (per-device throttling). 0 for waveforms.
validation_range[min, max] | nullRange used to flag suspect values. Out-of-range values are still ingested but tagged.
emission_enabledbooleanWhether observations for this biosignal are persisted. Set to false to ingest without storing.

Adding new biosignals

The catalog is data-driven. New biosignals can be added by extending the catalog without code changes - your existing application picks them up the next time it queries the API. Reach out if you have a biosignal type that isn't covered.

Need a biosignal that isn't listed? The catalog is intentionally extensible. We add biosignals as we onboard new device categories - if your use case needs something specific, contact us.

On this page