Frequently asked questions
What teams need to know before evaluating Efatha.
Direct answers about the product’s current in-room workflow, security controls, implementation, records, and support.
Clear answers for clinical and enterprise review.
Product scope, security language, implementation, and support—without hiding important limitations.
Product and workflow
What is Efatha?
Efatha is an AI-powered language interpretation app for in-person clinical conversations. A clinician and patient use a common phone or tablet in the same room to interpret both directions.
How quickly can an encounter begin?
Efatha connects to its interpretation service in about five seconds, allowing the people in the room to begin speaking without waiting on a traditional language line.
Do we need dedicated hardware?
No dedicated interpretation cart is required. Efatha is designed to work on common phones and tablets used in the room.
What happens after an encounter?
Efatha generates an editable transcript and clinical note in a couple of seconds. The physician reviews and approves the record before it remains in the patient history.
What does Lumis do?
Lumis reviews translations and flags language that a physician should double-check. It supports review; it does not replace clinical judgment.
Security and privacy
Is Efatha HIPAA compliant?
Efatha is designed to support HIPAA-compliant workflows. Organizations should evaluate the product, configuration, and their own policies as part of their compliance review.
How is information encrypted?
TLS 1.2+ protects information in transit, and transcripts are protected with AES-256 encryption at rest.
Are patient conversations stored on the device?
No. Patient conversations are not stored on the clinician’s phone or tablet.
How is access controlled?
Role-based access controls scope access by responsibility and facility, including admin, superadmin, and facility roles.
Can information be deleted?
Discarded sessions and an entire account can be permanently deleted. Efatha also uses short-lived, scoped credentials rather than storing long-lived service keys on the device.
Implementation and support
How difficult is implementation?
Implementation is designed to be straightforward. Efatha’s founder works directly with customers to configure facilities, roles, and initial workflows without a drawn-out hardware rollout.
What training is required?
The workflow is intentionally simple: open the app, choose languages, and begin. Practical onboarding helps clinicians and administrators understand encounter review and management.
Who provides technical support?
Support is currently founder-led. Technical questions and rollout issues go directly to the person building and maintaining Efatha.
Does Efatha replace qualified human interpreters?
Qualified human interpreters remain important. Efatha provides an immediate in-room option for clinical teams and should be evaluated according to the needs and risk of each encounter.
Bring dependable interpretation to more patient encounters.
Book a focused walkthrough of the live interpretation experience, security model, encounter records, and rollout questions that matter to your organization.