Metric Availability
Understand which Circadify outputs are standard and which depend on configuration, validation, and intended use.
Circadify returns configured vital sign outputs from a guided camera scan. Availability depends on account configuration, SDK version, device quality, deployment environment, and intended use.
Output Matrix
| Output | Status | Notes |
|---|---|---|
| Heart Rate | Standard | Returned in BPM with confidence context. |
| Heart Rate Variability | Standard | Returned as supported HRV metrics for the scan. |
| Respiratory Rate | Standard | Returned in breaths per minute when scan quality is sufficient. |
| Blood Pressure | Configuration-dependent | Available as systolic and diastolic trend outputs when enabled for the deployment. |
| SpO2 | Configuration-dependent | Available when enabled for the deployment and supported by the validation plan. |
| Stress / Recovery Signals | Configuration-dependent | Derived from supported cardiovascular signals when enabled. |
Caution
Do not assume every account, SDK, or deployment returns every field. Build your UI and API handling around optional fields.
Implementation Guidance
- Treat optional fields as nullable.
- Display confidence and scan-quality context with results.
- Confirm enabled metrics during onboarding before building production workflows.
- Validate BP, SpO2, and derived signals against your intended use, population, and operating environment.
Related Pages
- Results - Result object and confidence scoring
- Intended Use - Use Circadify in the right workflow context
- On-Device Processing - Local capture and payload preparation boundary