Intelligence for healthier care
More time
for the patient.
AI patient conversations.
Clear clinical review.
Asclepius brings the previsit patient conversation, physician-reviewed history and source-linked insurance work into one workspace.
Before the visit
The patient’s story,
before you walk in.
Share a secure interview link before the appointment, or open Clinical Intake on a clinic device. Patients can have a continuous voice conversation with Asclepius AI about their main concern. Focused follow-up questions explore symptoms, daily life and treatment so far; patients can also type, correct an answer, pause or stop.
A draft history of present illness—HPI—and the separate full questions and answers arrive in the patient’s profile. Review and edit the history, clarify missing details and make the clinical decisions. Transfer the approved HPI into the correct EMR patient and visit through your practice’s authorized connection.
How it works
How the work moves forward.
Start before the appointment, review the history during care and carry the chosen plan into the insurance work. Authorized chart access brings relevant notes and treatment history into the same patient workspace.
- 01
AI patient interview
A one-use previsit link opens a voice conversation. An in-office device and typing are also options.
Patient + Asclepius AI - 02
Chart + history
A concise draft HPI, separate full Q&A and relevant records from authorized chart access.
Asclepius prepares - 03
Clinical review
Review and edit the HPI, resolve gaps and approve the note for transfer to the EMR.
Physician decision - 04
Authorization packet
Bring the care order and relevant chart history into a rationale with source attachments and a missing-item checklist.
Asclepius drafts - 05
Review + follow-up
Review the packet, answer a denial when needed and follow recorded payer replies through payment checks.
Practice follow-up
Reviewed noteAuthorized EMR transfer or approved-note export
If deniedDraft response → review → follow-up
Payment checkMatch payment to the case record
Community-supported development
Start in Memphis.
Build evidence for care.
Better preparation should reach the clinics where time and resources are stretched.
We are seeking grant support to develop Asclepius with Memphis nonprofit clinics serving underserved communities. The first focus: patient conversations, useful histories and more informed visits.
Multilingual intake is part of that plan, with Spanish as an initial evaluation priority. Clinic feedback and measured results will guide what comes next.
Our next chapter
Support the work
Seek grants for product development, privacy, security and cloud operations.
Build with clinics
Shape focused pilots around patient access and the physician’s daily workflow.
Measure what matters
Evaluate history quality, review time and patient experience before expanding.
EMR connections
Alongside the records
you already use.
Keep the EMR and the patient workspace connected. Transfer the physician-approved HPI to the correct patient and visit, and bring relevant chart notes, orders and treatment history into the insurance work through authorized connections.
Tested
Developer environments
Epic public sandbox and athenaOne Preview, using selected fictional patient charts.
Public sandbox
Preview
Planned
Future integrations
Vendor onboarding and workflow testing are planned for these systems.
Oracle Health (Cerner)
Build with us
Start a conversation.
Explore the product, discuss a clinic pilot or help support its development. We would like to hear what matters to your organization.
Product vision
Questions before we talk?
How does the patient conversation become a physician-reviewed HPI?
Before the visit, patients open a secure, one-use link and have a continuous voice conversation with Asclepius AI. An office device and typing are also options. Focused follow-up questions build the history, and patients can correct their words, pause or stop. A draft HPI and the separate full questions and answers return to the assigned patient profile. Physicians review the key facts, edit the HPI, clarify gaps and make the clinical decisions. Urgent concerns need direct clinical assessment rather than waiting for intake.
Can Asclepius read our chart and put the approved HPI into our EMR?
Through an authorized connection, bring relevant chart notes, orders, treatment history and supporting documents into the selected patient’s workspace. Review and edit the HPI, transfer the approved version to the correct EMR patient and encounter, and verify the result. Current connection evaluation uses selected fictional patients in Epic public sandbox and athenaOne Preview; other integrations are planned. Production access and transfer require vendor and practice authorization and integration acceptance.
How does the same information support authorizations and denial appeals?
The physician’s care order, reviewed HPI and relevant chart evidence support an authorization rationale with source citations, attachments and a checklist of missing information. For a denial, Asclepius drafts an argument that addresses the payer’s stated reason using the documented treatment course. The physician reviews the facts and reasoning. Deadlines, assigned follow-up and recorded payer responses stay with the case through payment review. Packet export and recorded tracking are available; live payer delivery and automatic updates require a separately accepted integration.
How will the first community pilots be funded and evaluated?
We are seeking grants, foundation support and government innovation funding for development, security and HIPAA implementation, and cloud and API costs. We plan to develop pilots with Memphis nonprofit care organizations, subject to partner agreements and readiness review. Before real-patient use, the work includes identity confirmation and consent, access controls, clinical and security acceptance, and applicable business associate agreements. Pilot measurement will examine clinical quality, physician review and correction time, workflow fit and delivery costs. These results will guide product changes and later venture funding.
Will patients be able to speak in their preferred language?
Multilingual intake is part of our development plan. We plan to offer conversations in a patient’s preferred supported language, keep the original-language Q&A available, and produce a physician-readable HPI. Spanish is an initial priority, with other languages evaluated as the program develops. The plan includes translation review with qualified translators and clinical reviewers before pilot use. Language availability will follow clinical and translation validation for the workflow used by each practice.