Now in design-partner phase · v1 → v2 SDK HQ — Cambridge, MA

Clinical intelligence, in the room.

Celias builds ambient clinical intelligence for hospitals — listening, structuring and acting alongside care teams without ever leaving the bedside or the EHR.
0
Priority states · day-one HIPAA
scroll
HIPAA-native· CHAI-aligned· NIST AI RMF· BAA on day one· SOC 2 Type II in flight· Designed for the bedside· Ambient by default·
§ 01 / Manifesto A note from the team

We believe the next decade of medicine will be quietly augmented — not by another dashboard, but by intelligence that listens, understands the work, and disappears into it. Celias is built for that moment: safe by construction, governed by design, and devoted to the clinicians who carry the weight.

§ 02 / What we do

A care-team copilot
that lives in the visit.

Celias is a HIPAA-native ambient platform. It joins clinical encounters in real time, structures what's said into the EHR, and routes downstream actions — referrals, prior auth, follow-up — to the right human or system. No new screens for the clinician.

⟶ Capability 01
Ambient scribing with structure that the EHR understands.

Continuous, multi-speaker capture with section-aware structuring (HPI, ROS, A/P) and direct write-back to Epic, Oracle Health and Athena. No copy-paste, no after-clinic notes.

⟶ Capability 02
Real-time care intelligence at the bedside.

Surfaces guideline-relevant prompts, contraindications and missing documentation as the conversation unfolds — subtly, on-device, never intrusively.

⟶ Capability 03
Downstream action — not just notes.

Referrals, orders, patient instructions and prior auth drafted, routed and tracked from a single ambient capture.

⟶ Capability 04
Governance baked in, not bolted on.

Per-encounter audit, model versioning, and a human-in-the-loop gate on every clinical write.

⟶ Capability 05
Built as an SDK first.

Drop into existing scribe, telehealth or rounding workflows. v1 ships behind your stack; v2 unlocks the full care-team copilot for design partners.

§ 03 / Product

One SDK.
Many moments of care.

The Celias SDK is a thin runtime that runs on the device or the edge of your network. Capture, structure and act on clinical encounters with primitives your team already knows — sessions, transcripts, actions, audits.

celias-sdk · examples/encounter.ts
// Begin a HIPAA-native ambient encounter
import { Celias } from "@celias/sdk";

const celias = new Celias({
  tenant: "st-marys-cardiology",
  governance: { committee: "on", audit: "per-encounter" },
  ehr: { vendor: "epic", writeBack: true }
});

const session = await celias.openEncounter({
  patient: mrn, clinician: npi,
  consent: "verbal+visual"
});

session.on("insight", (i) => ui.whisper(i));
session.on("action", (a) => queue.route(a));

await session.close(); // notes signed, audits sealed.

Sessions, not recordings.

Every encounter is a first-class object — patient, clinician, consent, governance posture. PHI never lands where it shouldn't.

Whispers, not pop-ups.

Insights surface where they're useful and stay quiet where they aren't. The clinician stays present; Celias stays helpful.

Actions, not artifacts.

Notes are a starting point. Celias closes the loop — orders, follow-up, patient instructions and prior auth — with a human-in-the-loop check on every clinical write.

v1 → v2, transparently.

v1 ships as a plug-in to your current scribe stack. v2 — full care-team copilot — converts in place for active design partners. No re-papering, no re-integration.

§ 04 / Trust & governance

We treat safety the way clinicians treat sterile fields.

Privacy
HIPAA
BAA on day one
AI Governance
CHAI
Assurance-aligned
Risk Management
NIST AI RMF
Mapped + audited
Security
SOC 2 Type II
In flight · Q3 26
⟶ Priority
jurisdictions
US Federal CA NY TX IL · WOPR NV · AB 406 UT · AI Policy Act FL MA WA NJ
§ 05 / Roadmap

Where we are.
Where we're going.

Celias is shipping in deliberate steps. The product converts in place — no re-papering for design partners, no surprise re-integration for IT.

2025 · Q4
Founding partners
Three flagship health systems sign on. v1 SDK ships behind their existing scribe stack. We listen, we learn, we co-design.
Shipped
2026 · Q1
v1 — ambient capture
Multi-speaker, section-aware capture with full EHR write-back. Per-encounter audit, opt-in consent, governance committee dashboard.
Live in production
2026 · Q2
Care-team copilot beta
Real-time guideline whispers, contraindication checks, missing-documentation prompts. Quiet by default, opt-in surface.
2026 · Q3
v2 — downstream actions
Referrals, orders and prior-auth flows generated from the encounter, routed to the right human or system. SOC 2 Type II in hand.
Planned
2026 · Q4
Open partner cohort
Enrollment opens to a wider class of regional systems and physician groups. v1→v2 conversion language built into every contract.
Enrollment opens
2027 · H1
Specialty modules
Cardiology, oncology and primary-care modules layered on the same runtime. Same SDK, deeper context, same governance posture.
Roadmapped

The first AI tool I've actually let into the room with a patient. It writes the note I would have written, surfaces what I almost missed, and then gets out of the way — which is, weirdly, the highest compliment I can give software.

Sanjeet Jayaseelan · Founder & Developer
§ 06 / Partner enrollment

Build the next decade of care with us.

We're enrolling a small cohort of design partners for the v2 conversion. If you run a clinical service line and want a real say in what ambient AI looks like in your hospital — start here.

By submitting, you agree to our partner privacy practices. We respond personally within two business days. PHI never leaves your environment.