Skip to main content

Choosing Clinic Software

A Demo Script for Testing Clinic Software Before You Buy

A ready demo script for Indian clinics comparing software: real OPD scenarios to run, who should attend, what to record, red flags and how to score vendors fairly.

Bractis clinic guides · Updated · 5 min read

Short answer

A good clinic software demo follows your script, not the vendor's. Bring fictional patients and run your real day: a booked visit and a walk-in, a follow-up with history, a prescription with a correction, a bill with a partial payment, a report to share, a reminder to a consenting patient, a staff member with limited access, an internet drop, and a full data export. Have reception and a doctor operate the software themselves, record what worked and what needed workarounds, and score every vendor on the same sheet.

Why you need your own demo script

Software demos are designed to impress. The vendor shows the smoothest path through the best features, often with a perfect sample patient and a fast connection. Your clinic is messier: a walk-in arrives during a booking, a patient's phone number changes, a bill is part-paid, the internet drops at 7 pm. A demo script makes every vendor show how the software handles your real day, so you compare like with like.

This guide gives a script you can use with any vendor, including Bractis.

Who should attend

  • The receptionist who will register patients and take payments.
  • At least one doctor who will write prescriptions.
  • The owner or manager who will review collections and reports.
  • The person who handles IT, if you have one.

Ask the vendor to let your staff operate the software, not only watch. What looks easy when the vendor clicks can be confusing for a new user.

Prepare fictional patients

Never use real patient data in a demo. Prepare three or four fictional patients with names typical of your area, including one with a name that is often spelled differently, one child with a guardian, and one elderly patient with several chronic conditions and old reports.

The script

On a narrow screen, scroll the table sideways to see every column.

StepWhat to doWhat to watch
1. Booking and walk-inBook one patient, then register a walk-in in the same sessionSteps needed, how the queue shows both
2. Duplicate checkRegister a patient whose name is spelled differently from an existing recordDoes the system warn you? Can you correct it?
3. Follow-up with historyOpen the elderly patient's previous visit and reportsIs history easy to see during the consultation?
4. PrescriptionWrite a prescription for a common condition, then correct a doseSpeed, templates, legibility of the printout, how corrections are recorded
5. Child prescriptionPrescribe for the child using weightWeight field, dose display, guardian details
6. BillingBill a consultation plus a procedure, take a partial paymentHow the balance is shown and collected at the next visit
7. CorrectionChange a bill after paymentWho can do it, and whether the change is logged
8. ReportsAttach a lab report and share it with the patientChannels, consent, identity checks
9. ReminderSet a follow-up date and a reminder for a consenting patientMessage content, channel, opt-out
10. RolesLog in as reception and try to open clinical notesWhat each role can and cannot see
11. Internet dropTurn off Wi-Fi during a visit and continue workingWhat works, what waits, how sync is shown
12. ExportAsk for a full export of the sample dataFormat, completeness, how long it takes

What to record

For each step, note whether it worked, how many steps it took, any workaround needed, and questions to follow up. Take screenshots and keep sample printouts. Write exact answers to questions, such as "offline works for prescriptions but not billing", rather than general impressions.

Questions to ask during the demo

  • Which features shown are available in the plan we would buy?
  • Which features are in development or pilot, and when are they expected?
  • What does the price include, and what costs extra, such as SMS, WhatsApp, storage or users?
  • Where is our data stored, and who at the vendor can access it?
  • How do we get all our data out if we leave, and how long do we have?
  • What support is available during our OPD hours?

Ask for answers in writing after the demo.

Red flags

  • The vendor will not let your staff operate the software.
  • Features are shown that are not in the plan quoted.
  • Answers about data export or security are vague.
  • Offline claims that cannot be demonstrated.
  • Pressure to sign on the day with a discount.
  • No clear answer on what happens to data after cancellation.

Scoring vendors

Use one score sheet for all vendors. Score each step from 0 to 3, with notes. Add scores for support, data terms and price separately. Weight the steps that matter most to your clinic, such as prescriptions for a busy GP or billing for a procedure-heavy clinic. Discuss scores with staff before deciding; the receptionist's view on registration and billing is often decisive.

After the demo

Shortlist one or two vendors and ask for a trial with your own workflow. Check references from clinics similar to yours. Read the contract carefully before signing.

Data protection during demos

Do not share real patient lists, screenshots of your current system with patient data, or exports with vendors during evaluation. Under the DPDP Act, sharing patient data with a vendor you have not engaged is risky. Use fictional data only.

A worked example

A two-doctor clinic compared three vendors. Using the script, the receptionist found one system required re-entering a walk-in's details twice, another could not show a part-paid balance clearly at the next visit, and the third handled both well but had unclear export terms. The clinic asked the third vendor for written export terms and a two-week trial before deciding. The doctors said the script saved them from choosing on the basis of the best presentation.

Common mistakes

  • Letting the vendor run the whole demo.
  • Using real patient data.
  • Not testing corrections, roles or offline behaviour.
  • Comparing vendors on different scenarios.
  • Discussing price before features are verified.

Where Bractis fits

Bractis welcomes this kind of demo. Appointment requests are reviewed by reception, payment status is attached to each visit, roles limit access, and supported local work shows save and sync status. Ask the team to run your script and show what is supported today. Plans start at ₹999 a month plus GST.

Frequently asked questions

How long should a clinic software demo take?

About 60 to 90 minutes to run a full script with your staff.

Should staff attend the demo?

Yes. Reception and at least one doctor should operate the software themselves.

Can I use real patient data in a demo?

No. Use fictional patients only.

What is the most important thing to test?

The steps your clinic does most often, plus corrections, roles, offline behaviour and data export.

Run this in your own clinic

Bractis is clinic management software built for Indian OPDs: appointments, patient records, prescriptions, billing and follow-up in one place. You can try it in your own clinic before you decide.

Sources and review

Written by the Bractis editorial team for doctors and clinic owners in India. Rules, fees and prices change: check the linked primary sources before acting, and ask your CA or lawyer about your own case.