No. MRI safety determinations for implanted devices depend on the specific manufacturer, model, placement date, scan field strength, and scan area. The bot captures the device details (manufacturer, model, year placed, hospital, surgeon, any implant card the patient has) and routes the question to the MRI technologist for review before scheduling is confirmed. The technologist is the appropriate decision maker. The refusal is locked into the prompt and tested before launch.

Pacemakers and cochlear implants are particularly nuanced. Some pacemakers are MRI-conditional and some are not. Cochlear implants vary by manufacturer with different precautions. The bot does not categorize these on its own. It captures the device details, flags the booking for the MRI technologist, and explains that the technologist will confirm or deny the appointment after reviewing the device. We recommend an extra refusal example in the prompt for these specifically.

Yes, in a basic way. The bot can ask the screening questions from your published form (any metal in the body, any implanted devices, any history of metal in the eye, pregnancy status, allergy to contrast if relevant) and capture the answers for the tech to review. It does not clear or deny patients based on those answers. Final screening is the technologist's call before the patient enters the magnet room.

It quotes your published policy on gadolinium use, contraindications (impaired kidney function per your protocol), and what to expect at injection. Specific risk discussions for individual patients (especially patients with kidney impairment, prior contrast reactions, or pregnancy) route to the radiologist or the referring provider for context-aware decisions. The bot does not make gadolinium eligibility calls.

Yes. The bot describes what wide-bore magnets are, your published bore diameter, and which scans you offer on wide-bore versus standard from your published equipment page. For patients with significant claustrophobia, it can describe your published sedation policy (which typically requires the referring physician to order sedation in advance) and route the patient to coordinate with that provider.

Pediatric MRI often involves sedation, longer scheduling windows, and parental presence considerations. The bot routes pediatric inquiries to the pediatric-imaging coordinator per your published policy. We recommend a separate bot for the pediatric program, which SleekAI's multibot setup supports out of the box. Pediatric MRI safety screening adds developmental and consent considerations that warrant a distinct prompt.

No. MRI interpretation is the radiologist's role and result delivery is the referring provider's role per the standard workflow. The bot routes result questions to your published timeline (typically results to the referring provider within 24 to 72 hours depending on protocol) and points patients to their provider's office. The bot does not interpret findings or estimate clinical significance.

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