Question 1

What is Emma, exactly?

Accepted Answer

Emma is a multimodal conversational AI clinical companion for clinicians, patients, and operations teams. She's built on Anthropic Claude under our HIPAA BAA, deployed as a white-label SaaS that plugs into your existing healthcare systems — EHR, RPM, lab (LIS), scheduling, patient apps.

Question 2

Is Emma a medical device?

Accepted Answer

No. Emma is clinical decision support software (CDSS) that surfaces information, identifies patterns, and answers questions in natural language. She does not diagnose, treat, or replace clinical judgment. She is not currently classified as FDA Software as a Medical Device (SaMD). All clinical decisions remain with the licensed provider.

Question 3

How does Emma handle PHI?

Accepted Answer

Emma does not persist PHI on her infrastructure. She queries your existing systems in real time via their APIs — she never touches the underlying EMR data store directly. Conversation logs use opaque patient identifiers (not names or dates of birth). See our Security page for the full architecture.

Question 4

What's the integration timeline?

Accepted Answer

First site live in 12 weeks. Production-ready cutover at 16 weeks. Each additional site onboarded under the same partner: under 2 weeks.

Question 5

Do I need to migrate my data?

Accepted Answer

No. Emma uses an adapter pattern to query your existing system APIs (EHR, RPM, LIS, scheduling). Your data stays in your systems. We never write to your EMR data store.

Question 6

What languages does Emma support?

Accepted Answer

English at production. Spanish in beta. Additional languages added based on partner demand.

Question 7

What systems and devices does Emma work with?

Accepted Answer

Whatever your stack already supports. Emma is multimodal — she parses EHR records (Epic-FHIR, athenahealth), RPM device data (RTV today; Omron, A&D, Accu-Chek, Withings, iHealth, Beurer), lab results (HL7 / LIS), and scheduling. Custom adapters are part of partner onboarding.

Question 8

Who owns the Emma IP?

Accepted Answer

Jolabdan Group LLC owns all IP in the Emma platform. Customers receive a license to use, not modify or sublicense.

Question 9

What about Anthropic / OpenAI BAAs?

Accepted Answer

Signed with every vendor in the path of an Emma transaction. We publish the current BAA status to active customers under their MSA.

Question 10

Is Emma SOC 2 certified?

Accepted Answer

SOC 2 Type I is in progress and targeted for completion within 6 months of our first paid clinical deployment. Type II within 18 months of Type I issuance.

Question 11

Can I see Emma in action without committing?

Accepted Answer

Yes. We do live demos every week. Request one on our Contact page.

Question 12

How is Emma different from a generic AI scribe or chatbot?

Accepted Answer

Emma is a licensable, multimodal clinical AI designed from day one to layer on top of the systems you already run — EHR, RPM, lab, scheduling. She is not an AI scribe (we don't transcribe encounters); she is not a generic chatbot (she's grounded in real patient data via your APIs); she doesn't replace your EHR or RPM. She is the AI brain your existing stack has been missing.

Question 13

What does it cost?

Accepted Answer

See our Licensing page. Three pricing structures, picked based on how you want to share upside and how predictable your patient volume is.

Question 14

Can we white-label Emma as our own?

Accepted Answer

Yes — that's the default deployment model. Your name, your colors, your subdomain (e.g., emma.yourpartner.com).

Common questions about Emma.

Didn't find your question?