Key points
- An embedded scribe is a feature of the record system the clinic runs. An independent platform keeps its own record and connects outward.
- Embedded fits one record system kept for years. Independent fits work that runs on from the note, across more than one system or site.
- Portability is settled in the contract. Ask for a full export in a structured, commonly used, machine-readable format and written exit terms before signing.4
- On wai, letters, booking and the patient's Profile run from one record, and signed notes and letters export into any system.5
Summary
An embedded scribe fits a clinic keeping one record system for years that wants faster notes inside it. An independent platform fits a clinic that wants letters, the front desk and the patient's own record to run from the signed note, across more than one system or site. Either way, put the export format and exit terms in the contract.
The right architecture leaves every consultation finished and every record able to move with the clinic. Decide where the scribe lives first, then read the feature list.
See it in your clinicThirty minutes on your own patients and doctors.
Request a demoSee a consultation run through to the front desk on one platform, and an export of a signed note, in fifteen minutes.
| Question | What a strong answer shows | What to ask |
|---|---|---|
| Where the note lands | A signed note arriving where clinicians read it | Show it live, on a real consultation |
| How much of the clinic is covered | Letters, coding, front desk, booking and the patient record drafted for approval | Which tasks after the consultation are drafted |
| Who sets the roadmap | Recent releases you can see | What shipped in the last three months |
| More than one site or system | One record across sites while each keeps its own system | Show a patient seen at two sites |
| Clinicians in several practices | Templates and history that travel with the clinician | Can a clinician keep templates when they move |
| Export at exit | A full, structured, machine-readable export on a set timetable | Format, timetable and cost, in the contract |
| Audit trail | An event log you can export | Export the log for one patient, today |
Two architectures
An embedded scribe is a feature of the record system the clinic already runs, drafting the note into the chart under that system's contract and release schedule.
An independent platform keeps its own record and connects to the systems around it, so the signed note carries on to letters, coding, booking and the patient's own record.
When embedded fits
Embedded is the shortest path to faster notes inside one record system the clinic plans to keep. There is one supplier to review, and the note lands where clinicians already read it.
When an independent platform fits
An independent platform fits when the clinic runs more than one system or site, or when the work after the note matters as much as the note. Clinicians who work across several practices keep their templates, and the clinic chooses its scribe while keeping its record system.
On a whole-clinic platform, letters, codes, follow-up and booking start from the signed note on the same record, and the front desk picks up each task without retyping it. Running the clinic on one platform covers the wider decision.
Portability is an exit question
The portability test is the same for both architectures. The ICO describes data portability as providing personal data in a format that is structured, commonly used and machine-readable.4 Ask every supplier to show that export on a real record before signing, and put the format and timetable in the contract.
In the US, the Cures Act defines information blocking as a practice likely to interfere with the access, exchange or use of electronic health information, and applies it to developers of certified health IT as well as providers.2 HL7 FHIR is the standard for exchanging healthcare information electronically, so ask which FHIR resources each supplier reads and writes.3
What reaches the clinician before the visit
The US Office of the National Coordinator reported that 70% of hospitals engaged in all four domains of exchange at least sometimes in 2023, and 43% did so routinely.1 Among routinely interoperable hospitals, 92% had the clinical information they needed from outside providers at the point of care, against 33% of the rest.1
Score each option on what reaches the clinician before the visit and on what leaves the clinic after it.
One record for the whole clinic on wai
wai is an independent platform on one record, which the consultation, the front desk and the patient's own Profile all read. Signed notes and letters export into any system the clinic keeps.5 wai is built to connect to US hospital record systems over FHIR R4, to read a patient's history before the visit. We set up your clinic's connection with you.
For groups, data rights, portability and exit terms are agreed in the contract.6 The clinician signs every clinical document, and the team approves every patient message before it is sent.
Where to start
List every system the clinic runs today and every task that follows a consultation, from the letter to the receipt, and score each option on the table below.
Then ask each supplier for a live export of a signed note and its letter, the FHIR resources it reads and writes, and its exit terms in writing. Our guide to switching without losing records shows how to test the exit before you need it.
Bring a list of the systems your clinic runs. We show what wai covers, what it connects to and how an export looks.
Frequently asked questions
Is an embedded scribe safer for data protection?
The questions are the same for both, covering where data is hosted, who processes it, what is logged and how it leaves at exit. Embedded means one fewer supplier to review.
Will an independent scribe write into our record system?
That depends on the system and the supplier. Ask to see a signed note arrive in your record, live, and ask which FHIR resources it reads and writes.3
How do we keep our records portable?
Ask for a full export that is structured, commonly used and machine-readable, see it run on a real record, and put the format, timetable and cost in the contract.4
We run two sites on different systems. Which fits?
One record and one front desk can span both sites while each site keeps its own system, which is where an independent platform fits.
Does wai need our existing record system?
wai keeps its own clinical record, which the consultation, the front desk and the patient's Profile all read. Where a clinic keeps another system alongside it, signed notes and letters export into that system.5
How does wai price an independent platform?
The platform's prices are published on the pricing page. wai Admin is priced per location and starts with a demo and a scoped pilot.
Sources
- 1Office of the National Coordinator for Health IT, Everson, Barker and Gabriel, 2024Raising the Bar on Interoperability, a decade of data show that sometimes is not good enoughRead 14 October 2026Read source
- 2Office of the National Coordinator for Health IT, US Department of Health and Human Services, 2026Information BlockingRead 14 October 2026Read source
- 3HL7 International, 2023FHIR Overview, Release 5Read 14 October 2026Read source
- 4Information Commissioner's OfficeRight to data portabilityRead 14 October 2026Read source
- 5wai, 2026IntegrationsRead 14 October 2026Read source
- 6wai, 2026wai for clinic groups and chainsRead 14 October 2026Read source
Every consultation finished, with records the clinic can take anywhere.
Fifteen minutes on your own systems, showing what wai covers and how your records leave. 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.
See what wai does between the visits