wai alongside Practice Fusion, what moves and who moves it

What is built today, and what is not

wai has no native integration with Practice Fusion. No code in wai reads from Practice Fusion or writes to it, and nothing is synced between the two in the background. The integrations page lists the connections wai has live or built, and Practice Fusion is not one of them.

So the route today is the clinician's own hands, kept short. One click copies the signed note, one download gives the signed letter, and Practice Fusion stays the practice's chart, prescribing and billing system for as long as the practice wants it to.

None of that limits what runs in wai. The note, the letters, the front desk and the follow-up run there in full, and the chart of record stays where the practice keeps it.

A practice day alongside Practice Fusion

Take a 66-year-old seen for a blood pressure review at an independent internal medicine practice that charts and bills in Practice Fusion. The appointment sits in Practice Fusion as it always has.

In the room the clinician starts the capture in wai. wai drafts the note, and the clinician reads it in the problem-oriented view, corrects the home readings the draft had rounded, adds that the ankle swelling began after the last dose change, confirms the suggested ICD-10 code and signs.

One click copies the signed note as plain text, and the clinician pastes it into the patient's Practice Fusion chart. The new prescription is sent from Practice Fusion as usual. The medication change letter to the patient, drafted from the same visit and explaining the new dose and what to watch for, is signed in wai, downloaded as a PDF with the signature and attached to the chart.

The plan goes home in plain words, and wai sends the recall for the repeat kidney blood test in two weeks, approved by a person at the desk, then explains the result with the clinician's comment when it is back. This is an illustrative example, not a real patient.

The note and the letters, signed by the clinician

Nothing reaches Practice Fusion or the patient until the clinician signs it in wai. One captured note can be read as SOAP, problem-oriented, narrative, a bullet summary, a handover or in full detail, and the clinician copies the view that suits the chart. The copy is plain text, so it pastes cleanly into any note field.

Letters come from the same visit. A letter to the patient, referral letters that carry the questions for the specialist, results letters, medication change letters, fit-to-fly letters and medico-legal reports are drafted for the clinician to sign, and each signed letter downloads as a PDF with the signature.

Codes are suggested from the note, ICD-10 and SNOMED CT, each shown with the line of the visit it rests on, for the clinician to confirm. CPT codes and the E/M level stay with the practice's biller, because wai does not suggest them. For the wider picture, see clinic AI without replacing the EHR and how AI scribes connect to an EHR.

What can run in wai beside Practice Fusion

The front desk can run in wai while Practice Fusion keeps the chart. Calls, email, web forms and WhatsApp land in one thread per patient, replies are drafted in the practice's voice, and a person approves each one before it is sent.

Where the practice wants it, scheduling can move too. wai booking links read each doctor's Google, Outlook or Apple calendar, cancellations backfill from the waitlist and reminders go out. Deposits, invoices, memberships and payment links run through the practice's own Stripe account. Or the practice keeps scheduling in Practice Fusion and uses wai for everything after the appointment is made.

After the visit, results reach the patient with the doctor's own comment and a plain explanation of each marker, recalls go out for the review, the repeat test or the refill with each message approved by a person, and the patient app holds results, letters, messages and payments in the patient's language. Nothing is switched off on the first day. The AI scribe for private practice page covers the rest.

The patient's own language

wai works in 60 languages, among them English, Arabic, Spanish, French, Portuguese, Italian, Russian, Polish, Turkish, Urdu and Mandarin. English can be mixed in one visit with Spanish, French, Portuguese, Russian, Italian, Dutch, German, Hindi or Japanese, and the others are captured in that language. The signed note is written in English for the record, and the patient's summary can be translated into their language beside it, with emergency numbers kept exactly as written.

The evidence behind wai's method

The note is one part of the day the evidence measures. In a randomised trial of 238 outpatient physicians across 14 specialties at UCLA Health, the ambient scribe with a significant effect cut the time spent writing each note by about 41 seconds, against 18 seconds in usual care.³ At The Permanente Medical Group, 3,442 physicians used an ambient scribe across 303,266 encounters in its first ten weeks.⁴ wai is built on that finding, so it takes on the letters, the replies, the booking and the follow-up as well as the note.

A draft stays a draft until a person signs it. wai holds every draft until the clinician signs it, and every reply until a person at the practice sends it, which is also why the copy into Practice Fusion happens after signing and never before.

The patient's own language matters. In a systematic review of 33 studies, 76% found at least one outcome better when patient and physician shared a language other than English.⁵

Measured in a working clinic. At The Wellness in London, which runs on wai every day, every clinician has 15 hours a week back, as published in the customer story.⁶

Where to start

Week one, one clinician, Practice Fusion unchanged. Capture each visit in wai, sign the note, copy it into the chart and attach the signed letters as PDFs. Count the minutes from the end of each visit to a signed note in the chart. wai signs a business associate agreement with US practices before go-live.

Week two, add the front desk. Route calls, email, web forms and WhatsApp into wai, keep scheduling and billing where they are, and decide at the end of the fortnight whether booking links and deposits should move as well. The switching checklist covers what to agree first, and technical teams can read the developers and MCP page. Practices on other systems can read wai alongside Kareo or wai alongside Doctolib.

Frequently asked questions