Changelog

Medication Lifecycle

New medications resource in both the JavaScript and Python SDKs, and a new PartnerMedicationsController on the API — order/refill creation, refill-due polling, progress check-ins, and an explicit discontinue signal so a therapy's refill status is never ambiguous.

New endpoints:

POST   /partner/v1/users/{id}/medications
GET    /partner/v1/users/{id}/medications
GET    /partner/v1/medications/refills-due
POST   /partner/v1/users/{id}/medications/{orderId}/progress-checkins
GET    /partner/v1/users/{id}/medications/{orderId}/progress-checkins
PATCH  /partner/v1/users/{id}/medications/{orderId}/discontinue

New scope: medications.write (medications.read already existed). See the medication refill lifecycle guide for the full order → Tebra sync → refill-due poll → check-in → refill-or-discontinue flow.

Medication orders and progress check-ins are also synced into the prescribing practice's Tebra chart. Configure a practice's Tebra credential under Partner Portal → Settings → Tebra Practices.

SDKs bumped to JS 1.2.0 / Python 1.1.0 — full parity across both, since this resource is server-to-server only.

Partner Product Advisor

Partners can now configure product recommendations for their users. When a user's health insights meet certain thresholds, the API returns relevant product suggestions scoped to your partner catalog.

New endpoint: POST /partner/v1/users/{id}/product-advice

FHIR Context in Partner API Responses

FHIR context (resource IDs, narrative text) is now included in all health data API responses. This enables richer EHR integrations that need to write back to source systems.

Idempotency Key Support

All POST endpoints now accept an Idempotency-Key header. Requests with the same key within 24 hours return the original response, making it safe to retry on network failures without creating duplicate records.

POST /partner/v1/users/onboard
Idempotency-Key: unique-request-id-abc123

Improved Insight Cache Eviction

Insights are now automatically invalidated when new health data is submitted, ensuring AI summaries always reflect the most recent data. Previously, the 6-hour cache persisted even after a FHIR data update.

Cosmos DB Stability Fix

Fixed a startup failure when Azure Cosmos DB was transiently unavailable. The app now starts cleanly and retries the connection in the background, rather than failing the entire deployment.

Partner API Key Management

Partners can now self-service their API keys from the Partner Portal:

• Generate new keys with custom expiry dates
• Rotate existing keys with zero-downtime (old key stays valid for 24 hours after rotation)
• Revoke compromised keys immediately

FHIR Resource ID on Lab Uploads

Lab document upload responses now include the FHIR DocumentReference resource ID, enabling partners to reference the specific document in downstream FHIR queries.

{
  "analysisId": "anlz_abc123",
  "fhirDocumentId": "DocumentReference/dr-xyz789",
  "structured": true
}

Stage Environment

A dedicated stage environment is now available for pre-production testing with production-equivalent infrastructure:

https://stage.api.onepath.health

Stage environment uses the same database isolation and AI models as production, but with relaxed rate limits (500 req/min).

CORS Policy Update

Partner subdomains matching *.onepath.health are now automatically added to the allowed CORS origins, removing the need to manually register each subdomain.

OnePath Connect is Live

After 18 months of building, the OnePath Connect partner API is available to organizations integrating health intelligence into their products.

Partner API Endpoints

Method	Endpoint	Description
POST	/partner/v1/users/onboard	Register a user and create their FHIR record
PATCH	/partner/v1/users/{id}/health-data	Submit FHIR R4 health observations
POST	/partner/v1/users/{id}/lab-analysis	AI-powered lab document processing
GET	/partner/v1/users/{id}/insights	Retrieve AI-generated health summary
POST	/partner/v1/users/{id}/coaching-chat	Session-based conversational health AI

Documentation Site

The OnePath Connect documentation is live at onepath.health/docs. Getting Started guide, API reference, and integration guides are published.

Partner Demo

A sandboxed demo environment is live at demo.onepath.health. Explore the full API flow with pre-seeded fictional patient data — no signup required.

BAA Template Published

The BAA template is now available for review at /baa. BAA execution is required before production credentials are issued.

AI Assistant Quality Gate

The AI health assistant now requires at least one prior user message before responding. This prevents low-quality initial responses from setting poor expectations and improves the coherence of multi-turn health coaching sessions.

User Search Role Filtering

User search now accepts an optional role filter parameter, enabling partners to scope searches to specific user types (patient, caregiver, wellness coach) within their partner namespace.

Onboarding Visibility Default

New users now default to public visibility within the partner context, reducing the number of required fields in the onboarding payload. Visibility can still be set explicitly.

Support Contact Update

Support email updated to partners@onepath.health across all communications and documentation.

Dependent Invites

Users can now invite dependents (family members, caregivers) into the platform. Dependents get a scoped view with appropriate consent controls. The inviting user retains full control over dependent access.

Emergency Access

Designated emergency contacts can view a user's critical health data (medications, conditions, allergies) in emergency situations. Emergency access events are logged to the immutable audit trail.

Friend & Network Features

Users can send and receive friend requests, enabling social support features for health journeys. Network-based nudges and shared goal tracking are supported.

AI Home Screen

A new AI-first home screen replaces the static dashboard. The embedded health chat is accessible on first load, with the AI proactively summarizing recent health activity.

Twilio Integration Stubs

Twilio messaging integration is stubbed for future notification features (appointment reminders, health alerts, coaching nudges). Full activation coming in v0.6.0.

Visual Theme Refresh

Complete UI redesign with new dark/light theme system, improved typography, and a more consistent design language across all pages. The new design better reflects the enterprise and clinical nature of the platform.

Demo Environment Links

Links to the partner demo environment are now integrated throughout the marketing site. Sales prospects and evaluating engineers can access the live demo directly from relevant sections of the platform overview and use case pages.

Navigation Improvements

Improved cross-linking between marketing pages and the live demo. Anchor navigation within pages is smoother with CSS scroll-behavior adjustments.

AI Health Chat Assistant

An embedded AI chat widget is now available for health questions. Users can ask about their health data, get explanations of lab results, and receive personalized wellness guidance. The assistant is grounded in the user's actual health record.

Clinical Advisory Team Expansion

Two new clinical advisors joined the OnePath team, bringing expertise in population health management and clinical data interoperability. Their contributions are reflected in the updated team page.

JSON Data Migration

All site content (team bios, use cases, capability descriptions) has been migrated from inline JSX to structured JSON data files. This makes content updates faster and enables future CMS integration without code changes.

Shared Component Library

A shared component library is introduced: CapabilityCard, TeamMemberCard, PageHero, and TrustBar are now reusable across all pages, reducing duplication and ensuring visual consistency.

Initial Launch

OnePath Health launches its public presence with a complete marketing and information site covering:

• Platform overview — the API capability domains and technical architecture
• Use cases — integration patterns for health plans, EHRs, telehealth, and wellness apps
• Security & compliance — HIPAA, FHIR R4, audit logging, and the dual-auth model
• Company — team backgrounds and the founding story
• Partner access — a direct channel for organizations to request integration credentials

The site is built on Next.js 15 with a fully custom design system, Tailwind CSS, and Radix UI components.