The questions
we hear most often.

An ambient scribe captures the visit. Sarthi captures the visit and runs everything around it — fax intake, voice and scheduling, eligibility, intake forms, prior auth, coding, claim submission, denials, and follow-up.

Most practices using a standalone scribe still run four to seven other tools alongside it. Sarthi replaces those, end-to-end, with one operating layer.

Native connectors today: Epic, Athenahealth, eClinicalWorks, NextGen, Practice Fusion. Standards rails for everything else: HL7, FHIR, X12.

For legacy systems with no API, we bridge via RPA — not as a hack, but as a deliberate connector pattern. We will not ask you to rip and replace the system your practice already lives in.

Two-week observation phase — we shadow the workflows you want to hand off and document the hours they consume. Then a narrow rollout on the one or two workflows that hurt most.

Most launch partners are running their first production workflow on Sarthi inside the first month. We expand from there, one workflow at a time, on a cadence that respects how your team actually adapts.

You do. The covered entity owns its PHI under a signed Business Associate Agreement. Sarthi processes data on your behalf, under your direction, with administrative, physical, and technical safeguards in production.

On exit, your data is exported in standards-compliant formats and deleted from our systems on a published retention schedule. No contract tail. No hostage data.

HIPAA: BAA on request, full administrative / physical / technical safeguards in production today. SOC 2 Type II observation window is underway, audit report targeted for 2026.

AES-256 at rest, TLS 1.3 in transit, per-tenant key isolation, zero plaintext PHI in logs, US-only data residency, hardware-key MFA, and immutable audit logs scoped per workflow. Read the full security paper →

Every engagement starts with a written time-back target — agreed before you sign. If Sarthi doesn’t meet that target inside 90 days, you exit without penalty: no clawback, no contract tail, no hostage data.

Exactly one launch partner has ever invoked this clause. Zero have walked.

That’s the Atelier engagement — see Pricing. Most independent practices start with one or two workflows scoped tightly: ambient scribe + coding, or intake + scheduling, or prior auth standalone.

The operating layer expands as you add workflows; the engagement doesn’t require committing to all of it on day one.

By conversation, scoped to the workflows you hand off. We’re calibrating with our launch partners — every engagement is sized against the labor it absorbs, not against a per-seat list price.

You see the math before you sign. No per-claim fees, no per-seat fees, no annual lock-in. See Pricing →