An ENT scribe should know where the conversation ends. Audiograms, scope media, device output, and registry submissions have their own source systems and reviewers. A safe pilot checks whether the draft preserves that boundary. If a result was not spoken or supplied through an approved path, it should not appear as fact.
Three lanes, one signed record
At the end of a busy clinic session, the signed note may refer to information that began in different places. Split the pilot into three lanes before judging the prose:
| Lane | Examples | Scribe acceptance rule |
|---|---|---|
| Conversation | Symptoms, history, goals, instructions discussed | Draft with speaker and time context intact |
| Observed and stated | Clinician-spoken examination or procedure finding | Include only what the clinician actually states |
| Device or source record | Audiogram, scope media, imaging report, prior procedure record | Cite the source in the note only when the clinician supplies or verifies it |
The lane label does not need to appear in the final note. It belongs in the test worksheet, where it exposes unsupported jumps.
The silent-result case catches overreach
Give the reviewer a synthetic encounter with an audiogram in the source system. Do not mention one of its values during the recorded conversation. If the draft supplies that value anyway, stop and trace how it arrived.
Then reverse the case. Have the clinician state a verified result, its date, and the source. The draft should preserve all three without implying the scribe independently read the study. Run the same drill with a scope finding and a prior procedure record.
This is a better trial than counting how many ENT terms the product spells correctly. Vocabulary is visible. Provenance failures hide inside fluent sentences.
Connectivity is a separate capability
Device, media, and registry connectivity are contract-and-demonstration questions, not benefits to infer from the words “AI” or “EHR.” Ask the vendor to name the supported product, data path, implementation owner, and current status. The federal Health IT Playbook recommends common demo scenarios and testing tied to the practice’s needs (ASTP/ONC Health IT Playbook). If the vendor cannot show the required path with representative data, treat the answer as no.
Patient Square does not claim Reg-ent connectivity, registry submission, audiogram ingestion, scope-media handling, or device integration. Those gaps are disqualifying when the practice needs the scribe to own them. They are not disqualifying when the real job is drafting the spoken visit beside an existing specialty system.
A six-row pilot log beats a polished demo
Use two rows for each lane: one ordinary case and one exception. Record the source expected, what the draft produced, the correction made, who reviewed it, and whether the failure would have been obvious during signing.
Add contract controls to the same packet. HHS describes covered entities and business associates as carrying defined responsibilities for protected health information (HHS covered entities and business associates). Ask where visit data goes, which vendors receive it, how access is logged, how long each artifact remains, and what the practice can export or delete.
Repeat the same six cases after configuration changes. A stable log exposes unsupported changes faster than another polished demo.
Keep the product claim narrow
Patient Square is an AI clinical platform. Its AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Practice Copilot can work alongside an existing EHR or use the bundled Patient Square EHR, named AI Copilot EHR on the pricing page, from the Copilot tier. Annual US pricing is $79 per physician per month for Assist and $119 for Copilot (Patient Square pricing).
It does not claim the ENT-specific capabilities named above. We think that honesty makes the evaluation easier: keep the specialty system for device, media, and registry work, then test whether the scribe reduces the spoken-documentation burden without blurring sources.
Use the EHR integration checklist to document the handoff and the HIPAA, BAA, and consent guide for the privacy review.