Evaluation packet
Kore.ai HealthAssist
Kore.ai · Triage & Patient Access · Scheduling & intake
Prepared November 22, 2026 from the public listing on CIFoundry. It shows what the public record says and what to ask the vendor. It is not a recommendation or an endorsement.
1. What the public record shows
- Regulatory status
- Not on record
- Published evidence
- Not on record
- Named health-system users
- Not on record
- Integrations
- Not on record
- Data inputs
- Not on record
- HIPAA BAA
- Not on record
- SOC 2 / HITRUST
- Not on record
- Deployment model
- Not on record
Integrations, data inputs, BAA, SOC 2, HITRUST and deployment model are reported by the vendor and not checked by us. Confirm them in writing.
From public directories
Third-party directories checked by our team. These are not the vendor's own pages and not an endorsement.
- Listed in Epic Showroom
- Connection Hub: HealthAssist by Kore.aisource, checked Nov 21, 2026Epic’s public app directory. Listed developers pay Epic for services; Epic does not endorse, certify or validate listed products.
2. Evaluation checklist for your role
Each question shows what the public record says: on record (with its source), reported by the maker, or not on record. It is a list of things to check, not a score.
For every reviewer
Administrator & finance
Physician
IT & security
Compliance & risk
Your ticks and notes stay in this browser. Nothing is sent to us.
3. Gaps to raise with the vendor
Based on what is missing or worth confirming in this tool’s public record.
- No regulatory status is listed. Ask whether the tool is regulated by the FDA as a medical device and, if so, for the clearance number and the exact cleared intended use.
- No published study is linked. Ask for peer-reviewed validation done outside the developer’s own sites, and for results on patients and equipment like yours.
- We found no public reports naming health systems that use it. Ask for reference sites similar to yours and contact them yourself.
- Will the vendor sign a HIPAA Business Associate Agreement?
- Does the vendor have a current SOC 2 Type II report or HITRUST certification you can review?
- Where is data stored and processed (cloud region, on-premises), and which subcontractors, including any large-language-model provider, touch patient data?
- It is listed in Epic Showroom, which says nothing about how it is configured. Ask which Epic integration it uses at live sites and where results appear for the clinician.
- Is your data used to train the vendor’s models, and can it be deleted when the contract ends?
4. Questions for this kind of tool
From our Patient access and triage AI guide.
Change tool type:
Voice agents and contact center
Use this section if the tool answers patient calls or chats on its own.
Questions to ask
- How does it recognize emergencies such as chest pain or stroke symptoms mid-call, and what happens next?
- How quickly does a human pick up after escalation, and do they see what was already said?
- Does it tell callers they are speaking with AI?
- Which languages are supported, and was safety tested in each one?
- Can we edit escalation rules ourselves?
Test it locally
- Before launch, run 50 to 100 scripted test calls including red-flag scenarios in every supported language. Review every escalation failure during the first month.
Red flags
- Containment rates reported without safety measures
- No 24/7 emergency script
- No handoff with context
Symptom checkers and triage
Use this section if the tool asks about symptoms and recommends a level of care (self-care, clinic, urgent care, emergency).
Questions to ask
- What are its under-triage and over-triage rates compared with clinicians or established nurse protocols (such as Schmitt-Thompson)?
- How often does it falsely reassure patients in emergency scenarios?
- What is its regulatory position? Tools that recommend care levels may fall under FDA oversight depending on their claims.
- Was it tested in children, older adults and patients with limited English, if you serve them?
Red flags
- Accuracy reported only on common, mild complaints
- No published under-triage rate
Scheduling and intake
Use this section if the tool books, moves or fills appointments, or collects history and forms before a visit.
Questions to ask
- Does it write directly into your scheduling system, respecting visit types, provider rules and referral requirements?
- How are urgent symptoms in an intake form flagged and routed?
- What changes in no-show rate and slot fill have similar sites measured?
Reminders and outreach
Use this section if the tool sends appointment reminders, care-gap outreach or other automated messages.
Questions to ask
- How does it handle consent and opt-outs for calls and texts under the Telephone Consumer Protection Act (TCPA)?
- What happens when a patient replies with a clinical question or an emergency?
5. Questions for every tool
The 12 questions that apply to every tool
Fit and evidence
- Intended use. Does the stated use match the patients, setting, user and decision you plan to use it for?
- Evidence level. From weakest to strongest: vendor-internal test, retrospective external validation, prospective "silent" run, prospective live study, randomized trial, proven change in outcomes. Ask which level the claims rest on and look for peer-reviewed external validation.
- Population and equipment. Ask for results by age, sex, race and ethnicity, language and payer, and, where relevant, skin type and body habitus. Ask for results on your scanner or device vendors, EHR and protocols.
- Local validation. Before go-live, run the tool on your own recent cases and compare it to ground truth. Agree in the contract on what counts as passing.
Workflow and people
- Workflow cost. Count clicks, alerts per clinician per shift, minutes added per case, and who acts on the output. A strong tool that nobody acts on has no value.
- Integration. Native EHR or PACS integration or a separate window? Single sign-on? Where do results land?
- Human oversight. Who has the final say, how are disagreements with the tool handled, and how do you guard against over-reliance? Train users on known failure modes, not just features. Explanations matter most for risk scores and decision support.
After go-live
- Monitoring. Who checks for drift, how often, and what triggers a pause? Re-check after vendor updates, scanner or EHR changes, and shifts in your patient population. Agree in advance on the results that would retire the tool.
- Model updates. Version control, advance notice of changes, and the right to stay on a version you validated.
Data, liability and money
- Data rights and security. BAA, where data is stored and processed, encryption, retention, SOC 2 or HITRUST, whether your data trains the vendor's models, the list of subcontractors that touch patient data (including any large-language-model provider), and whether data can be deleted.
- Liability and patient notice. Who is liable when AI-assisted care goes wrong is still unsettled, and responsibility currently stays with the clinicians and organizations using the tool. Ask your malpractice carrier, and cover indemnification, audit rights and incident reporting in the contract. Joint Commission and CHAI guidance says patients should be told when AI directly affects their care, with consent where relevant.
- Money and exit. Pricing model, any real payment pathway, the return you will measure, termination for performance failure, data return, and no auto-renewal without a performance review.
6. Notes and decision
Problem we want to solve and how we will measure it
Vendor answers and follow-ups
Local test plan and what counts as passing
Decision, owner and next step