Medical AI Chatbot for Providers: Clinical Search or Patient FAQ?

A medical AI chatbot for providers is either a clinical search tool, which answers a clinician's question with cited sources, or a patient FAQ bot, which answers website visitors from a fact sheet you approve. Most small practices need the FAQ bot first if admin queries are the pain, and clinical search only if clinicians want faster reference lookups.

The two are different products with different risks, so the choice is not really "which is better". Clinical search sits behind a clinician login and is judged on whether its citations hold up. An FAQ bot faces the public and is judged on what it refuses to say. Below is how to tell which job you have, what each costs, and how to set either one up without giving advice by accident.

Follow me on Instagram@sagnikteaches

Two products that share a name

Vendors use "medical chatbot" for both, which is why search results mix them. Here is the split that matters to a practice owner.

Connect on LinkedInSagnik Bhattacharya

A third product often gets lumped in: the AI scribe, which writes consultation notes. Several scribes now bundle clinical search too, which blurs the line again. If notes are your real bottleneck, read the scribe decision rule first and treat any search feature as a bonus.

Subscribe on YouTube@sagnikteaches

What clinical search tools actually offer

As of November 2026 there are three kinds of clinical search a small practice is likely to meet.

General assistants with a clinician mode

OpenAI launched ChatGPT for Clinicians in April 2026 as a free workspace for verified individual clinicians: physicians, nurse practitioners, physician assistants and pharmacists. Sign-up needs a ChatGPT account, a national provider number and a licence that a third-party service can verify, and at launch it is open in one country only; OpenAI says more countries will follow. Its help page for ChatGPT for Clinicians lists clinical search with citations (titles, journals, authors and publication dates), deep research across medical literature, and drafting help for referral letters and patient instructions.

Two details matter for a practice. OpenAI says content shared in the clinician workspace is not used to train its models, and an individual clinician can sign a business associate agreement (a contract that makes the vendor responsible for protecting patient data) under Settings > Agreements. That agreement covers one person; a practice that wants one contract for several users is pointed to the separate organisation product. Until the agreement is signed, OpenAI's own guidance is to keep protected health information out of it, and many lookups never need it.

Scribes with an evidence feature

Heidi's pricing page lists a free plan that includes an Evidence feature with unlimited answers and transparent citations, plus a scribe with unlimited transcription on standard templates. The paid Clinician and Practice plans each offer a 14-day trial and Enterprise goes through sales, but the page shows no dollar prices for any of them, so do not assume one. Freed's page lists Starter at $39 a month on annual billing ($59 monthly) with up to 40 notes a month and no evidence feature; Core, with unlimited notes and Clinical Evidence answers, currently shows $59 on one billing toggle and $79 on the other, so read the checkout total; Premier is $104 a month billed annually or $119 monthly and adds letters, EHR push and coding. Freed says its evidence answers cite more than 50 sources and offers a 7-day trial with no card needed. Both pages change often; confirm on the day.

Standalone evidence engines

There are also search products built only for clinicians, with no scribe attached. Their access rules vary: many ask for registration with a professional number, and some are open only in certain countries, so read the sign-up terms and the data policy before anyone uses one with a patient in mind. If one is open to you, treat it like the others: a pointer to sources, not a verdict.

What a patient FAQ bot does, and where it must stop

An FAQ bot answers questions that already have a fixed answer: opening hours, which services you offer, fees, how to register, how to cancel, where to park, what to bring, how long results usually take to reach you. It is a front-door tool. The good ones answer only from the documents you give them, and say "I can't help with that, here is how to reach the team" when the question is outside.

The line it must not cross is advice. A bot that reads "my chest feels tight, should I come in?" and replies with reassurance has stepped into triage. Your configuration needs a hard rule for that sort of message, which I cover below. The tutorial on what a clinic chatbot may collect covers the data side: do not let a public bot ask for names, dates of birth or symptoms unless you have checked the vendor's contract and consent flow.

The approved fact sheet

This is the document that makes an FAQ bot safe or unsafe. Keep it to one or two pages. Here is a filled-in illustration for a small primary-care practice (all details invented for the example).

PRACTICE FACT SHEET (approved by: practice manager and lead doctor, reviewed 1 November)

Opening hours: Mon-Fri 8:30-17:30. Closed on public holidays.
New patients: accepting new registrations, online form on the Register page.
Appointments: book by phone, online or at the desk. Same-day slots released at 8:30.
Cancellations: please give 24 hours' notice by phone or the booking link.
Fees: standard appointment $65; extended appointment $110; certificate letters $30.
Repeat prescriptions: allow 3 working days; request through the patient portal.
Test results: the practice contacts you; please do not call before 5 working days.
Urgent or emergency: if you think this is an emergency, call the emergency number now.
Out of hours: recorded message on the main line gives the on-call route.
NOT COVERED: symptoms, results meaning, doses, referrals. Say "please call the practice".

Anything not on that sheet, the bot should not state. That one rule removes most of the risk.

How to decide: the owner's test

Work from the pain, not the product. Spend ten minutes tallying the last two weeks.

1. Count admin enquiries. Look at your phone log or inbox. How many were opening hours, fees, registration or "where is the form"? If more than about a quarter of contacts are answerable from a fact sheet, an FAQ bot has a job.
2. Ask clinicians what they look up. Do they stop mid-clinic to check interactions, dosing references or guideline updates? If yes, and the answer is "several times a week", a search tool is worth a trial.
3. Check who has time to own it. An FAQ bot needs a monthly review by a person. A search tool needs every clinician to verify sources. If nobody can do that, buy neither yet.
4. Check what already bundles it. If you are already paying for a scribe, see whether it includes search. Do not pay twice.

Here is that test applied to three illustrative practices.

A worked choice with numbers

Illustration only. A four-clinician practice has two receptionists. Over two weeks, the manager samples the phone log and finds 640 contacts. She tags them: 190 are fixed-answer questions (hours, fees, registration, forms, parking), 260 are booking changes, 120 are prescriptions and results, and 70 are other. The fixed-answer share is 190 of 640, about 30%.

Say each fixed-answer contact takes a receptionist an average of two minutes including the wrap-up. That is 380 minutes in two weeks, roughly 3 hours 10 minutes a week. If a web FAQ bot handled half of them, which she should not assume, that frees about 95 minutes a week. At a loaded receptionist cost of $20 an hour that is under $32 a week, around $130 a month. Those are her own made-up inputs; yours will differ, which is the point of measuring them.

Now the clinical side. She asks the four clinicians how often they leave the room to look something up. Two say "once or twice a week"; two say "most clinics". Time per lookup is about three minutes. The two heavy users might save a few minutes a day. That is real but unmeasured, and the free clinician tools cost nothing but verification time. Her decision: put an FAQ bot on the website first, and let the two heavy users trial a free evidence tool for a month with a rule that they open the cited source every time.

Notice what she did not do: promise a saving, or buy anything before the tally. For more on payback inputs, see the worked AI implementation plan for a small practice.

Setting up a patient FAQ bot safely

Step 1: restrict it to your sheet

Choose a tool that lets you upload documents and set it to answer only from them. Ask the vendor two questions in writing: can I stop it answering from general knowledge, and where are chat logs stored and for how long. If the answers are vague, move on.

Step 2: write the refusal rules

Put these in the bot's instructions. A sample you can adapt:

You are the website assistant for [practice name]. Answer only from the fact sheet provided.
If the question is not covered, say: "I can't help with that here. Please call the practice on [number] during opening hours."
Never give medical advice, interpret symptoms or results, suggest doses, or say whether something is serious.
If the message mentions chest pain, difficulty breathing, severe bleeding, thoughts of self-harm, or anything that sounds urgent, reply only: "This sounds like it may be urgent. Please call the emergency number now."
Never ask for a name, date of birth, or health details. If the user offers them, ask them not to share them and direct them to the phone line.
Always state that you are an automated assistant and not a clinician.

Step 3: test with awkward questions

Before going live, run twenty questions. Include ten on the sheet, five off it, and five that try to pull advice out. Here is an illustrative test and what you want back.

Step 4: show the limits on the page

Place a visible line by the chat window: "This is an automated assistant. It cannot give medical advice. In an emergency, call the emergency number." Keep the wording simple and consistent with the bot's own opening message.

Using clinical search without being misled

A clinical search answer reads like a confident summary. The failure to watch for is a citation that exists but does not support the sentence beside it. Build one habit: for every answer that changes what you do, open the cited source and read the relevant paragraph.

A verification routine that takes two minutes

1. Ask the question with the patient's context stripped of identifiers. Say "adult, mid-fifties, type 2 diabetes, eGFR 40" rather than a name or date of birth.
2. Open the top two citations. Do they exist, and do they say what the summary says?
3. Check the date and population. Is the study recent, and does it include people like your patient?
4. Cross-check against the guideline you normally rely on if the answer differs from it.
5. Record in the notes that you used a reference tool only if your practice policy requires it.

A realistic miss

Illustration: a clinician asks about interaction risk between two common drugs. The tool gives a tidy paragraph and cites a review. The clinician opens it and finds the review covers a different drug in the same class. The tool had generalised. Nothing was harmed because the habit caught it. If that habit slips, the risk is real, so make it a written practice rule.

A sample search exchange and what to fix in it

Illustrative only, not a real tool's output. A clinician types: "Adult, stable type 2 diabetes, new persistent dry cough on an ACE inhibitor. Options and what the guidelines say?" A typical tool replies with three short paragraphs: ACE-inhibitor cough is a recognised effect in a minority of patients, switching to an angiotensin receptor blocker is the usual alternative, and the cough usually resolves within weeks of stopping. Each paragraph ends with a numbered citation.

What you would fix or check. First, "a minority" and "usually" are vague, so open the review and read the actual range. Second, the reply did not ask about other causes of cough, so add those yourself. Third, one citation was a narrative review rather than a guideline; look for the guideline your practice follows. The tool saved the search, not the thinking. That split is the whole value of it, and it is why clinicians, not receptionists, should own the trial.

A second FAQ example: the after-hours message

Many practices find their busiest bot moments are in the evening, when the phones are off. Illustration: a bot receives "Are you open now, and what do I do if I need someone tonight?" at 9 pm. With the fact sheet above it answers with the opening hours, the out-of-hours instruction and the emergency line, in that order, and stops. Without the out-of-hours line on the sheet, a poorly set bot may invent one. That is why the sheet lists it explicitly, and why you should read the transcripts that arrive after closing time first.

What search tools and FAQ bots cost

Prices below are list prices from vendor pages; confirm before you budget.

The real cost is time: a person to write and review the fact sheet, and clinicians to verify citations. Budget an hour to write the sheet, another hour for testing, and fifteen minutes a month to review. For a wider budget view, see the first-spend budget order for a small practice.

Privacy and consent checks before either goes live

• Training use. Does the vendor use your inputs to train models? Get the answer in writing.
• Contract. If patient-identifiable information could reach the tool, you need the vendor's data-protection or business associate terms on your plan, not just a marketing page. See the BAA check by plan.
• Retention. How long are chat logs or queries kept, and can you delete them?
• Consent wording. If an FAQ bot records chats, say so on the page.
• Staff rule. Write one paragraph: what clinicians may paste into a search tool (de-identified context only unless the contract allows more).

If you want a longer list of vendor questions, what to ask before buying any AI tool for a medical practice is the right next read.

Two mistakes that show up in the first month

The bot that answers too much. A practice uploads its whole website, including a section about common conditions. The bot starts summarising that section when asked about symptoms. Fix: upload only the fact sheet, and keep the condition pages out.

The search tool nobody trusts. A clinician tries it twice, finds one wrong citation, and stops. Fix: agree beforehand what you are testing (say, drug interaction lookups) and judge it on twenty real questions over a month, not on a single miss.

Reading the first month's transcripts and lookups

After a month, compare against your tally. For the FAQ bot: how many chats ended with a correct answer, how many were passed to the phone line, and how many fixed-answer calls remain? Read a sample of ten transcripts every week for the first month. Look for any answer not on the fact sheet. For clinical search: ask each trial clinician how many lookups they ran, how many citations they opened, and whether any answer had been wrong or unsupported. If either tool saved no measurable time, switch it off. Neither is an obligation.

A short decision rule to finish: if your pain is calls and enquiries, start with the FAQ bot and the phone side; if it is clinicians stopping to look things up, trial a free search tool with a verification rule; if it is writing up consultations, look at scribes. Pick one, measure it for a month, and add the next only when the first has paid for its own attention.

Questions practices ask before choosing a medical chatbot

Can one chatbot do both clinical search and patient FAQs?

In practice no, and you should not want one to. Clinical search is built for clinicians, runs behind a login and may cite journals. A patient FAQ bot is public, limited to a fact sheet you approve, and must refuse clinical questions. Mixing them puts open-ended medical answers in front of patients.

Does a clinical search tool replace reading the guideline?

No. Treat the answer as a pointer to the source. Open the cited paper or guideline, check it says what the summary claims, and check it applies to your patient. The clinician stays responsible for every decision.

What should a patient FAQ bot never answer?

Anything about symptoms, test results, medication doses, whether something is urgent, or whether a person should come in. It should hand those to a human or to emergency instructions you wrote, and say clearly that it cannot give medical advice.

Who maintains the approved fact sheet?

One named person, usually the practice manager, with a clinician signing it off. Put a review date on it, check it monthly at first, and update it the same day opening hours, fees or services change.

Further reads

• AI Solutions for Medical Practices: Build, Buy or Hire Help? — Build, buy or hire help for a small practice.
• Is an AI Scribe Worth It for a Small Private Clinic? — If notes, not questions, are your real bottleneck.
• AI Scribe Costs Compared: What Small Clinics Pay in 2026 — What scribes cost, since many bundle a search feature.
• HIPAA-Compliant AI Receptionist: A BAA and Retention Checklist — Retention and contract checks for the phone side.
• Best AI Receptionist for a Medical Practice: What Each Type Does — The phone-side option if calls are the pain.
• Do Small Medical Practices Need an AI Consultant? — Whether a small practice needs outside help at all.
• AI Chatbot for Healthcare: A Small Clinic's Data and Consent Checklist — Twenty checks before a clinic puts an AI chatbot on its website: contracts, legal basis, disclosure, scope and logging.
• AI Chatbot for a Doctor's Website: Scope, Disclosure, Handover — A practice owner's set-up guide: scope sheet, disclosure line, hand-over rules, logging and named chatbot tools with costs.
• Midwife Software Compared: Notes, Booking, Billing and AI Tools — Five midwife software options checked on vendor pages for notes, consent, portal, billing, data location and AI claims, with a scoring sheet.
• AI Assistant for a Medical Practice: Build a Staff Policy Q&A — Turn your protocols into a staff Q&A assistant in an afternoon, with a 20-question test set and no patient data anywhere near it.
• AI Tools for Physicians: Seven Worth Paying For in Private Practice — Seven AI tools for a private-practice physician, scribes, clinical assistants, phones and claim checks, with what each does and what to verify.
• Patient Intake Automation in a Small Practice: Forms, AI Summaries — How a small practice sets up digital intake forms, consent capture and a clinician-checked AI summary, with retention and privacy rules.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI's help article on ChatGPT for Clinicians and OpenAI's launch post, Heidi Health pricing page, Freed pricing page, all checked 4 November 2026.