Seven capability domains — FHIR-native, HIPAA-compliant, AI-powered — accessible through a single authenticated API key scoped per partner application.
API Capabilities
From patient onboarding to AI coaching — seven domains, one integration.
Register patients within your existing system without requiring them to create OnePath accounts. Manage platform-level consent and revoke access at any time with full audit traceability.
Submit and retrieve longitudinal patient health data backed by FHIR R4. Observations and conditions are coded to LOINC and SNOMED CT standards, ensuring interoperability across systems.
Upload lab reports as PDFs or images. Our AI engine automatically extracts structured data, coding results to LOINC and storing them as FHIR DocumentReferences — no manual entry required.
Generate LLM-powered clinical summaries from a patient's complete health history. Results are cached to minimize latency and cost, and are grounded in the patient's actual longitudinal record.
Embed session-based health Q&A directly in your platform. Each conversation is grounded in the patient's FHIR data. Resource-specific chat allows focused queries against individual lab results or documents.
Create structured health goals and fitness plans for patients. Track progress over time and trigger automated coaching conversations that generate and update goals based on patient dialogue.
Retrieve a computed overall health score derived from a patient's complete profile — conditions, observations, goals, and history — providing a single signal for risk stratification and engagement.
Architecture
All health data is stored as FHIR R4 resources. Observations reference LOINC codes. Conditions use SNOMED CT. Medications use RxNorm. Your integration speaks the same language as EHR systems — interoperability is built in, not bolted on.
Each partner application receives a dedicated FHIR namespace. Data submitted under one partner application is structurally inaccessible to any other. Cross-partner data leakage is not possible by design.
Users do not need to create OnePath accounts. Your system onboards them via API using your own identifiers. OnePath stores only a tokenized SHA-256 reference — never the raw identifier.
A BAA is required for production access. Sandbox credentials are available immediately upon request.
Request Partner Access