Automating New Patient Onboarding and Medical Histories
Ask any practice manager where the first ten minutes of a new patient appointment go and you will hear the same story. The patient arrives, is handed a clipboard, ticks “no” to everything because the pen is bad and the waiting room is busy, and then sits down in the chair. The dentist reads the form, spots an anticoagulant, asks three follow-up questions, and the slot is already running behind.
This post makes one argument. Of all the front desk automation on offer, pre-appointment digital medical histories save the most chair time, and they only do so if flagged answers reach a clinician before the patient walks in. Reminders, online booking and recall are all worth having. None of them touches the clinical part of the visit. A good digital history does.
Why this beats the other automations
Consider what the common front desk tools actually save.
| Automation | Typical saving | Who benefits |
|---|---|---|
| SMS appointment reminders | Fewer DNAs (often 2 to 4 percentage points) | Diary, not chair |
| Online booking | 5 to 10 minutes of phone time per booking | Reception |
| Automated recall | More bookings filled | Revenue |
| Pre-appointment digital history | 5 to 8 minutes of chair time per new patient | Clinician and patient |
Those figures are rough and vary by practice. But the logic holds: reminders and recall fill the diary, whereas a digital history shortens the appointment itself. Five minutes saved on a 30-minute NHS new patient exam is a sixth of the slot.
Run the numbers for a practice taking 25 new patients a month. Six minutes saved each is 150 minutes, two and a half hours of clinical time a month, or 30 hours a year. At an NHS UDA value of around £28 and an assumed three UDAs of throughput per hour of chair time, that is in the region of £2,500 a year recovered, before counting the private patients who would otherwise overrun. Subscription costs for most tools sit well below that. Adjust for your own contract and mix, but the direction is rarely in doubt.
What a good digital history actually does
A PDF emailed to the patient is not automation. It is a clipboard with extra steps. A proper tool does four things:
- Sends a link by SMS or email at booking, with a reminder 48 hours before.
- Branches the questions. Answer “yes” to heart conditions and it asks which, when, and what medication.
- Captures consent and contact details so reception stops retyping them.
- Writes into the clinical record (or at minimum produces a PDF attached to it) and flags risk answers.
The fourth point is the whole game. Collecting the data is easy. Making someone read the dangerous bits is the hard part.
The tools UK practices are using
Most practice management systems now have a native option or a partner. Dentally has digital forms built into its patient portal. SOE and Software of Excellence’s Exact users can use Patient Forms through their wider ecosystem. Carestream Dental’s R4 and Denplan-adjacent workflows lean on third-party partners. Dedicated products such as Dental Channel, Cliniko-style forms in smaller practices, Practicegenius, and Pearl-adjacent intake tools sit alongside general form builders. Check the current integrations list with your own PMS vendor before you buy, because this changes quickly and a form that cannot write back to your record means someone retyping it.
A reasonable test: ask the vendor to show you a patient who answers “yes” to “Are you taking blood thinners?” and show you exactly where that appears for the dentist. If the answer is “it’s in the PDF”, keep looking.
The flagging rule that makes it work
Here is the condition in the angle: flagged answers must route to a clinician before the visit, not at the visit.
If the form is only read in the chair, you have moved the data entry but not the delay. The dentist still discovers the bisphosphonate history with the patient watching, and the extraction plan changes on the spot. If the flag lands the day before, the dentist can book a longer slot, ask the GP for an INR, or move the appointment.
A workable flag list for general practice:
- Anticoagulants (warfarin, apixaban, rivaroxaban, edoxaban)
- Bisphosphonates or denosumab (MRONJ risk)
- Prosthetic heart valve, previous infective endocarditis
- Immunosuppression, chemotherapy, radiotherapy to head and neck
- Pregnancy
- Latex or penicillin allergy
- Uncontrolled diabetes, recent MI or stroke
- Needle phobia or “extremely anxious”
What routing looks like
Here is a plain-text example of the daily digest a practice might set up, sent to the clinician at 4pm the day before:
Tomorrow's new patients: flagged answers
09:00 Mr D. Okafor (Dr Patel)
FLAG: apixaban 5mg BD, started March
FLAG: penicillin allergy (rash)
Action: check bleeding plan, avoid amoxicillin
09:30 Mrs L. Brennan (Dr Patel)
No flags.
10:00 Ms S. Hughes (Dr Patel)
FLAG: alendronate 70mg weekly, 6 years
Action: confirm no extractions planned; MRONJ discussion
That is a two-minute read. It replaces the chair-side conversation that would otherwise take six.
Assign it to a named person. In most practices the nurse or practice manager prints or forwards it, and the clinician initials it. If nobody owns it, it quietly stops happening by week three.
A worked example
A four-surgery mixed NHS and private practice in the Midlands took about 40 new patients a month. Before digital forms, new patient exams ran at an average of 38 minutes against a 30-minute slot. After switching to pre-appointment links, completed by roughly 80 percent of patients before arrival, average new patient time fell to 32 minutes. The practice manager added a rule: anyone who had not completed the form 24 hours out got a phone call from reception.
The result was about 4 hours of recovered clinical time a month across the team. More usefully, in the first quarter the digest caught two patients on anticoagulants that previously would have been found in the chair, and one patient on IV bisphosphonates scheduled for an extraction. All three plans were changed in advance.
(This is an illustrative composite based on typical outcomes, so use your own audit data to set expectations.)
Practical pitfalls
Older patients and digital exclusion. Around one in ten UK adults are still offline. Keep a paper fallback and let reception complete the form by phone. Do not make a digital-only rule in an NHS practice.
Patients who say “no” to everything. Branching helps, but you still need the clinician to confirm verbally. Treat the digital form as a first pass that shortens the conversation, not a replacement for it.
Data protection. Medical histories are special category data under UK GDPR. You need a data processing agreement with the vendor, confirmation of UK or EU data hosting, and the tool listed in your DSP Toolkit submission and privacy notice. Ask who the sub-processors are. Your DPO or the practice’s compliance lead should sign it off before launch, not after.
Annual updates. The value does not stop at new patients. Send a short update form to existing patients 48 hours before their recall exam, asking only “has anything changed?” That catches new medication before it matters.
Clinical accountability. The dentist remains responsible for the history. The software helps, but the CQC will still look for evidence that a clinician reviewed and signed it. Make sure your tool records who confirmed it and when.
How to roll it out in a month
Week one: pick your flag list with your clinicians and write it down. Week two: configure the form and the routing, and test with staff using fake patients, including the anticoagulant case. Week three: switch on for new patients only. Week four: audit. Count completion rates, minutes saved on a sample of ten appointments, and how many flags were actioned before the visit.
If completion sits under 60 percent, the problem is usually the link timing or a clumsy mobile layout, not patient reluctance. Send it earlier, shorten it, and test it on an old phone.
Start with new patients, get the digest working, and only then think about where else automation might fit. The wider picture of reminders, online booking and recall is covered in our guide to front desk and recall automation, and most of it is worth doing once the history sits properly in your workflow.