Every consultation starts with the same questions. What brings you in. When did it start. What are you taking.
Those questions are necessary. They tell the doctor what to ask next. In a busy clinic they also eat the minutes that should go to care.
The problem
For a doctor seeing dozens of patients a day, a real share of each consultation goes on collecting basic information, reading past records and working out the patient's context before the clinical conversation can start.
Patient volumes go up. Consultation time does not go up with them. So patients wait longer, doctors get less time each, and hospitals carry longer cycles and inconsistent documentation.
The journey today
Register. Wait. Enter the room. Explain the symptoms. Answer the basics. Wait again while the doctor reviews the history. Then begin the actual consultation.
It works, but the patient repeats information that could have been collected earlier, and the doctor spends consultation time switching between the conversation, the records and the documentation. Everyone is busy and not all of the time is being used well.
How it works
Scan
The patient scans a QR code on the queue receipt, which opens a secure session on their phone. There is no application to download. They are already in the clinic and already holding the device, so the friction is close to zero.
Retrieve
The system pulls relevant history from connected systems: the hospital information system, electronic medical records, and FHIR ready national health records where those exist. Previous diagnoses, known allergies, chronic conditions and current medication come forward on their own rather than being searched for mid consultation.
Collect
The assistant gathers the rest through a guided chat. The patient describes symptoms in their own words and the follow up questions adapt to the answers. Someone reporting fever and body aches may be asked about duration, cough, recent travel, exposure, severity and hydration.
Summarise
What was collected and what was retrieved become one structured summary for the doctor. Chief complaint, symptom duration, relevant medical history, known allergies, risk indicators, context from previous records, and suggested follow up questions.
What it looks like for one patient
Sarah, 35, arrives with fever and body aches. Dr Adrian sees more than thirty patients a day and would normally review her records while she explains her symptoms from the beginning.
Instead she scans the code on her queue receipt. The assistant asks about the fever, how long it has run, whether there is a cough, where she has travelled. The system surfaces a previous seasonal flu record and a penicillin allergy from her history.
Within a few minutes the doctor has a summary before the consultation starts, and can open on assessment and diagnosis rather than on intake.
What changes
For patients, less repetition. For doctors, faster understanding and more of the appointment spent on treatment. For hospitals, more consistent documentation and shorter consultation cycles.
The result is not AI replacing the doctor. It is AI preparing the doctor. Healthcare runs on trust and judgement, and the right place for this technology is in front of that, taking the administrative work off the clock.
Why it is on this site
The chat is the easy half. Reading from medical records, keeping the session private, and knowing exactly what the assistant is allowed to touch is the half that takes the time and decides whether it can be deployed at all.
That is the same argument BuildPad makes about business applications. The visible part comes quickly either way. What sits behind it is what takes the months.

