Before
Transcript and notes only. Documentation that fails payer audit when physiology contradicts self-report.
REST API · SeroState
QOAX API Reference
Post-session fusion in. FHIR R4 evidence out.
Primary Endpoint
POST /v1/session
POST
/v1/session
{
"physiological_timeline": [ … ],
"risk_flags": [
{ "type": "…", "confidence": 0.0, "evidence": "…" }
],
"signal_quality": { "overall": 0.0 },
"cpt_support": [
{ "code": "…", "confidence": 0.0 }
],
"disposition": "documentation_support_only"
}
Documentation, not diagnosis. Confidence scoring and signal-quality metadata on every output. The clinician retains authority.
How to read these fields
- confidence: meaningful mismatch vs noise (default ≥0.75 surfaces; below logs for audit). Computed by SeroState and bounded by input quality; not a sensor readout.
- signal_quality: computed by SeroState from heart-rate sample continuity and plausibility over the session (<0.80 flags insufficiency); not reported by the watch.
Your clinical team sets the thresholds. We deliver the evidence.
Response includes
- Physiological timeline Continuous heart rate and voice (HRV where sampling permits), time-aligned to transcript.
- Risk flags Patterns + confidence + evidence refs.
- Signal quality Flags thin or noisy data before the record.
- CPT support Alignment suggestions with confidence tiers.
- FHIR R4 artifacts Structured bundle for EHR ingestion.
Before & After
What changes for your platform
After integration
Time-aligned physiology plus transcript. Confidence-scored evidence surfaced inside your existing product.
Authentication
Partner Access
OpenAPI spec, sandbox, and webhooks: on request for qualified engineering teams.
Production
OAuth 2.0 client credentials for authorized platform partners. Scoped to your integration environment with audit logging on all evidence requests.
Sandbox
Sandbox with sample payloads and synthetic streams, on request.
Go Deeper
QOAX session report sample, fusion protocol, and evidence scoring, on the Platform page.
Explore Platform