No. Insulin dosing, sliding scale interpretation, basal-bolus adjustments, correction factors, and any dosage question are explicitly refused in the system prompt. The bot routes those questions to the clinical line, the patient portal, or to the on-call CDCES. For symptoms of DKA or severe hypoglycemia, the bot directs the patient to call 911 or go to the nearest ER. The refusal is tested with a standard set of dosage prompts before launch and re-tested whenever the prompt changes.

The bot does not interpret blood glucose readings, A1c values, time-in-range data, or CGM trends. If a patient shares numbers, the bot acknowledges them, declines to interpret, and routes the patient to their care team via the portal or clinical line. For numbers paired with symptoms suggesting DKA or severe hypoglycemia (nausea, vomiting, confusion, rapid breathing), the bot escalates immediately to 911 or the ER.

Yes. Diabetes self-management education and support programs (group classes, one-on-one MNT, pump and CGM starts) live as posts in WordPress with schedule, prerequisites, duration, and CDCES instructor. The bot describes each program accurately and books the first session. It does not recommend which program fits a specific patient. The CDCES does that during the initial visit.

Yes operationally. Parents booking for a pediatric type 1 patient or adult children booking for an elderly parent are common and the bot accepts the booking. Verification of relationship, consent, and HIPAA authorization is a front-desk responsibility on arrival. The bot captures both the caller name and the patient name separately so staff have the right context for the visit.

Indirectly. SleekAI does not write into Epic, Athena, or any EHR directly. It captures the inquiry (patient name, DOB, reason, preferred clinician, insurance) and emails or webhooks the structured handoff to your scheduling team. They confirm in the EHR the way they would for a phone inquiry. That keeps the EHR as the single source of truth and avoids the integration surface area.

HIPAA compatibility is a stack decision, not a plugin feature. SleekAI is a WordPress plugin that uses your own API key (OpenAI, Anthropic, Google, or OpenRouter). For US clinics handling PHI, you need a HIPAA-eligible OpenAI configuration with a signed BAA, encryption at rest on the WordPress database, role-based access on logs, and BAAs with your host and any other vendor in the path. The plugin gives you the building blocks; the compliance posture is yours to assemble.

Yes, in your WordPress database with retention you control. We recommend short retention for any clinic that may see PHI in a chat (days rather than years), encryption at rest, and role-based access on who can read logs. The conversation log gives the care team context for the next visit and lets the medical director audit the refusal posture weekly. Document the log in your privacy notice.

Yes. SleekAI is multibot. Configure a separate bot for pediatric type 1 with its own system prompt, tone, and crisis routing rules. Adolescent and pediatric conversations need different parental consent language and different escalation paths than adult endocrinology, and the multibot setup handles that distinction cleanly. Display conditions can pin each bot to the right page or post type.