No. SleekAI is configured with explicit refusal language for every diagnostic, treatment, dosage, and 'is this normal' question. The instruction includes a hard refusal: never diagnose, never recommend specific treatments. For OB-specific urgency keywords (heavy bleeding, decreased fetal movement after 28 weeks, severe headache, vision changes, persistent vomiting, signs of pre-eclampsia), the bot routes immediately to the practice line during hours, the on-call line after hours, or 911 for emergencies. Audit-test quarterly with edge-case prompts.

Yes, as published procedural information. The bot can quote your practice's standard cadence (monthly to ~28 weeks, biweekly to ~36 weeks, weekly until delivery) and explain which routine tests happen at which visits per your protocol. It does not interpret results or advise on cadence deviations, those conversations always belong to the OB or midwife at the visit. The bot helps patients show up to the right visit at the right week with the right preparation.

Yes, for practices that offer both care models. The bot reads each provider's role and routes patients who explicitly request OB or midwife care to the right calendar, with a clear explanation of what each care model looks like at your practice. For mixed-model practices the bot defaults to neutral language and asks the patient's preference rather than nudging toward one model. The choice of OB versus midwife is a values-and-risk-based decision that belongs with the patient and clinician.

The system prompt is configured with OB-specific urgency keywords (heavy bleeding any trimester, decreased fetal movement after viability, severe abdominal pain, severe headache with vision changes, persistent vomiting with dehydration, fever above 38C, ruptured membranes, signs of pre-term labour). Each routes immediately to the appropriate line: the practice daytime line during hours, the on-call line after hours, and 911 for life-threatening signs. The widget header includes a visible disclaimer reinforcing scope.

Yes. For group practices with shared call, the bot explains the rotation so patients understand they may meet different practice members at labour and delivery. It lists the hospitals you have privileges at, what to expect at admission, and your practice's policy on doula support, labour preferences, and birth plans. None of this is clinical, all of it is currently a high-touch front-desk explanation that the bot can deliver consistently.

Yes. Six-week post-partum visit booking, lactation consultation routing, post-partum depression and mental health screening logistics, and contraception consultation if the patient requests it. The bot is configured to recognise post-partum red-flag symptoms (severe bleeding, signs of post-partum pre-eclampsia, signs of post-partum sepsis, signs of severe mood disturbance or self-harm risk) and route them immediately to the practice line and 911 or a crisis hotline as appropriate.

HIPAA compliance is a stack question, not a single-plugin question. SleekAI runs on your WordPress install with an API key you provide. For US obstetric practices handling PHI, you need a HIPAA-eligible API vendor configuration, a BAA in place with that vendor, encryption at rest on the WordPress database, role-restricted access on conversation logs, and the chat channel documented in your Notice of Privacy Practices. The plugin gives you the building blocks, the compliance posture is wider than the bot.

Yes, in your WordPress database. Retention is configurable. For PHI we recommend short retention windows (days, not years), encryption at rest on the database, role-based access on log readers, and BAAs with every vendor in your stack including the API issuer (OpenAI, Anthropic, Google, OpenRouter) and your hosting provider. The bot is configured to avoid inviting clinical detail into chat, so logged content stays operational.