No. SleekAI is configured to refuse any medication recommendation in rheumatology including biologic selection, DMARD initiation, dose adjustments, route changes (subcutaneous to infusion), drug holidays, and substitutions. Those decisions belong to the rheumatologist after reviewing disease activity, antibody status, infection risk, prior response history, and current labs. The bot redirects every medication question to a consultation booking and explains what prior records to bring for the visit.

Yes, when your infusion center page lives on WordPress. The bot reads which biologics you infuse, the scheduling cadence, infusion suite logistics, and how transfer of infusion care from another practice works. For patients considering transferring infusion care, the bot captures the current biologic, frequency, prior reactions, and route, then attaches the summary to the consultation booking. It does not commit to accepting a transfer, which is a clinical decision at the visit.

Yes. Tag your paediatric-trained rheumatologists in custom fields and the bot routes JIA, paediatric lupus, periodic fever syndromes, and other paediatric cases to them directly. Paediatric intake has different needs: age and weight, growth context, parent or guardian consent, school setting, current treaters. The bot branches on the paediatric page to capture those details. The same hard clinical boundary applies across all paediatric conversations.

The system prompt is configured to recognise infection-suspicion language in patients on biologics (fever, new severe rash, productive cough with fever, unusual fatigue with fever, surgical-wound concerns) and direct the patient to call the practice's after-hours line or go to the ER before any non-urgent intake. Infections on biologics are a known risk and the bot does not attempt severity assessment by chat; the default is rapid routing to clinical care.

Yes. Rheumatology transfers of care benefit from organised prior records: serologies and antibody panels, prior imaging reports, infusion records, DMARD trial history, prior biopsy reports if applicable, and current medication list. The bot captures the list of available records and explains your records-transfer workflow (patient brings, prior practice faxes, or HIPAA-compliant request). The summary attaches to the booking so the rheumatologist walks in with organised context.

It can describe what labs you typically order at a new-patient visit (CBC, comprehensive metabolic panel, CRP, ESR, ANA reflex, RF, anti-CCP, and others depending on suspected condition) from your published copy, and explain whether you have on-site phlebotomy. It will not interpret prior labs for a specific patient, will not predict which labs will be ordered for them specifically, and will not estimate findings, all of which are clinical at the visit.

In your WordPress database under your control. Retention is configurable through the plugin and most rheumatology practices set 30 to 60 days. For US practices handling PHI, you need a HIPAA-eligible model configuration, signed BAAs across the stack, encryption at rest, and access controls on log readers. The bot does not proxy model calls; they go to OpenAI or Anthropic using your own API key directly.

Yes, when telerheumatology is part of your service menu. The bot describes what a telerheumatology visit covers, what it cannot replace (in-person joint exam, in-office injections, infusion services), and which rheumatologists on your team offer it. It captures the patient's preference for telehealth versus in-person and routes the booking accordingly. The same clinical boundary applies: no diagnosis, no medication recommendation, no interpretation of prior labs.