Running a private clinic on one patient record

Key points

On one patient record, the consult and the front desk write to the same history the patient sees in their Profile.⁶
In a survey of 8,122 US family physicians, only 8% reported an ideal experience receiving outside test results in their record.¹
53% of US health system finance executives named multiple disparate software platforms as a barrier to data-sharing rules.²
Every supplier that handles patient data needs its own written contract under HIPAA and UK GDPR, so count contracts as well as subscriptions.⁴⁵
On wai, every message, draft, approval and signature is written to one event log the clinic can export.⁷

Summary

Run the clinic on one patient record. AI drafts with the whole history in view, and the clinic holds one contract and one audit log. A single clinician who wants faster notes can start with the clinical workspace and add the front desk later on the same record.

Your clinic answers the enquiry, takes the deposit, writes the note and sends the letter from the same record, with nothing to re-key. Below is what one record gives the clinic on handoffs, contracts, audit and staff hours.

See it in your clinicThirty minutes on your own patients and doctors.

Request a demo

of 8,122 US family physicians report an ideal experience receiving outside test results in their record ¹

53%

of US health system finance executives cite multiple disparate platforms as a data-sharing barrier ²

38%

of OECD countries have no clinical standards or vendor certification for record systems ³

See one patient move from a WhatsApp enquiry to a paid booking, a signed note and a letter, all on their own record.

Request a demo See pricing

What one patient record gives a private clinic
Question	On one patient record	What the clinic gains
Where the patient lives	One record shared by consult, front desk and Profile	Nothing to reconcile
What AI sees when it drafts	The whole history, letters, bookings and payments	Drafts that already know the patient
Handoffs inside the clinic	None	No re-keying between desk and consult
Contracts	One supplier, with named sub-processors	One contract to review each year
Audit when a patient asks who did what	One exportable event log	The answer from a single log
Staff training	One interface	One system to learn
Cost to count	Subscription, payment processing, training	Re-keying hours off the total
Best fit	A front desk, several clinicians and online payment	A single clinician can start with notes
What to check before buying	Full export, hosting country and the approval model	Every answer in writing

One record for each patient

The clinical workspace, the front desk and the patient's own Profile read and write the same record, so there is nothing to reconcile.⁶ The note, the appointment and the invoice belong to the same patient from the first message.

Data that stays with the patient

In a 2024 survey of 8,122 US family physicians, the share reporting an ideal experience, where information arrives automatically and is easy to find and reconcile, ranged from 19% for encounter documents to 8% for test results from outside hospitals.¹ The authors found that policy had not yet translated into widespread interoperability.¹

In a Deloitte survey of 30 finance executives at large US health systems, 53% named multiple disparate software platforms as a barrier to meeting data-sharing rules.² Across OECD countries, 38% have no clinical standards or vendor certification for record systems, which limits how well they exchange data.³ On one record, the front desk and the consult share the patient's data from the start.

Count the full cost

Add five lines. Subscriptions, setup and integration fees, payment processing, weekly staff hours spent copying data between systems at their hourly cost, and training time.

To price the fourth line, ask the front desk to tally for one week every time they type something into one system that already exists in another, then multiply by the team's hourly cost. On one record, that re-keying inside the clinic comes off the total.

One contract and one audit trail

In the US, a covered entity may let a business associate handle protected health information only with satisfactory assurance, documented in a written contract.⁴ In the UK, the ICO states that a controller using a processor must have a written contract, and processors need written contracts with their own sub-processors.⁵ Count the contracts and sub-processor lists the clinic reviews each year.

When a patient or regulator asks who saw a record and who sent a message, the answer comes from one log. On wai every message, draft, approval and signature is written to one event log the clinic can export.⁷

AI drafts with the whole record in view

A front desk reply drafted on one record already knows the last letter and the next appointment. Codes drafted from the signed note need no re-keying, and the patient's Profile shows the letter the moment it is signed. The clinician or the team approves each draft before it goes anywhere.

Starting with one part

A single clinician who wants faster notes can start with the clinical workspace alone. The guide on how to choose an AI medical scribe covers that decision, and the first check is that every note and letter exports in a format another system can read.

With two or more clinicians, a front desk and patients paying online, one record carries each patient from enquiry to invoice. See how that looks on an AI scribe for a whole clinic.

Where to start

List every tool that touches a patient, with its monthly cost, the data it holds and the contract behind it. Run the one-week re-keying tally at the front desk and price it. Then map one patient from first message to paid invoice and mark every point where data crosses between systems.

Bring that map to a demo and watch the same patient run on one record. To consolidate, follow the switching checklist step by step.

Bring your current tool list and see one of your patient's days mapped onto one record.

Request a demo See pricing

Frequently asked questions

How do we judge each part of one platform?

Judge each surface on its own measures, such as minutes in notes, time to reply and booking conversion, then count the re-keying the clinic no longer does.

Can we start with one part of the platform?

Yes. Start with the clinical workspace or with booking and payment, and add the front desk later on the same record.

What about the systems we already use?

Booking reads each clinician's busy times from Google Calendar, Outlook or Apple Calendar, so patients are only offered open times. It reads busy times only and does not write into a clinician's own calendar. Signed notes and letters can also be exported into other systems.

What should we ask about reliability?

Ask for the availability target, the incident process and a tested export. One supplier means one party to hold to account.

How do we count total cost?

Add subscriptions, setup, payment processing, weekly re-keying hours at staff cost and training time. wai prices are published on the pricing page.

Where is the data held on one platform?

wai hosts each clinic's records in its own country, under that country's rules. We set this up with your clinic.

Sources

Every patient on one record, from first message to paid invoice

Fifteen minutes with a clinician who uses wai every day, walking one of your own patients' days from enquiry to invoice. We reply within one working day.

Partner with us

See it on your own patients, then build it with us

Thirty minutes on your own patients, doctors and rules, in your market. We reply within one working day, and the clinics that partner with us early shape what we build next.

Request a demo Partner with us

See what wai does between the visits

Run the whole clinic on one patient record, from first message to signed letter