Locum physicians live with a problem staff docs rarely think about: a different EHR at almost every assignment. An ambient AI scribe that works the same way regardless of the system underneath solves the part of the job that actually eats your evenings, the documentation. Patient Square listens during the visit, then hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes later. You review it, sign it, and paste it into whatever chart the facility uses. No integration, no IT ticket, no waiting for the site to set anything up.
Key takeaways
- A locum scribe should be EHR-agnostic, since you cannot count on the same system twice.
- Patient Square never connects to the EHR, so there is no per-site integration project to schedule.
- You copy or paste the finished note into Epic, athenahealth, eClinicalWorks, Elation, NextGen, or a legacy system.
- Notes belong to the practice you document for and can be exported or deleted anytime.
- The signing clinician stays legally responsible for the record, the same as with a human scribe.
From visit end to draft note in hand
Site IT projects to start documenting
Assist tier, per clinician, annual billing
Source: pricing and product behavior described on the pricing page.
Why locum work breaks EHR-tied documentation tools
A scribe built to plug into one EHR assumes stability you do not have. Staff physicians keep the same system for years, so a deep integration pays off. Locums churn. New facility, new login, new documentation rules, sometimes every few weeks. A tool that needs a site integration is a tool you cannot use on day one, which is exactly when you need it most.
Credentialing already burns your time. Every assignment means fresh privileging paperwork, a new badge, a new orientation. Adding “wait for IT to wire up my scribe” to that list is a non-starter. The whole appeal of locum work is mobility. Your documentation tool has to match it.
Then there is note portability. If your notes live inside one facility’s EHR-linked tool, they are stranded there when the contract ends. You want the opposite: a note you generate, review, and place into the chart yourself, so the record lands where it belongs and nothing follows you to the next site that should not.
How an ambient scribe fits a locum assignment
The flow is the same everywhere, which is the point. You start the visit, the scribe listens, and roughly two minutes after you finish it returns a draft. You read the note against what actually happened, fix anything that needs fixing, sign, and move the text into the chart.
Because Patient Square does not talk to the EHR, an unfamiliar system only slows the clicking, not the writing. You might spend your first morning at a new site hunting for where the note field lives in their build of eClinicalWorks. The note itself is already done. Paste, sign, next patient.
Audio is processed in memory and discarded the moment the note drafts. Nothing is recorded or kept. For a clinician rotating through facilities with different privacy cultures, that matters: there is no growing archive of visit recordings trailing you from contract to contract.
What a locum scribe must actually do
Not every ambient tool is built for someone who changes sites constantly. Here is what the job demands and how Patient Square lines up.
| Locum need | Why it matters | How Patient Square handles it |
|---|---|---|
| No per-site integration | You cannot wait on IT at each assignment | Scribe never connects to the EHR; copy or paste the note |
| Works on any system | Epic here, a legacy tool next month | System-agnostic by design |
| Portable, review-first notes | Records must land in the right practice | You review, sign, then place the note yourself |
| No retained audio | Different sites, different privacy expectations | Audio discarded once the note drafts |
| Fast turnaround | Short assignments, high volume | Draft back in about two minutes |
| Clear ownership | Notes are the practice’s, not yours to carry | Notes belong to the practice, exportable or deletable |
The pattern underneath all of it: the scribe stays out of the EHR and out of the site’s plumbing. That is what lets it behave identically whether you are covering an ED in one state or a rural clinic in another.
The prescription draft, and where your judgment stays
Alongside the note, the scribe produces a prescription draft. It writes out the drug, the dose, and the instructions you dictated, so the order you already decided on is typed for you rather than by you.
Read that carefully, because the boundary matters for locums especially. It is a draft. It never sends to a pharmacy. There is no e-prescribing, no pharmacy gateway, no SureScripts connection. The scribe does not screen for interactions, dosing, or contraindications; there is no automated check and no block. You are the one who reviews and prescribes through whatever ordering system the facility uses, and at a new site where you may not know a patient’s history cold, that read is entirely yours to make. The draft saves the typing; the safety check is you.
Same logic on the ICD-10 side. The scribe suggests codes based on what was said in the room. You confirm or change them. It structures the encounter; it does not diagnose, and it does not interpret images or studies. Related reading on that: how ICD-10 suggestions work.
When an EHR-agnostic scribe is the right call
If you were a staff physician on one system for a decade, a deeply integrated scribe might be worth the setup cost. For locum work, the calculus flips. You want zero setup and total portability, even at the price of copy-paste instead of auto-filing.
Some clinicians ask whether they should just learn each site’s built-in AI charting instead. Two problems with that. First, you would relearn a different tool at every assignment. Second, availability varies wildly, and plenty of the systems you will meet have no ambient scribe at all. We wrote more on that tradeoff in ambient scribe versus a new EHR and in why an ambient layer beats Epic’s built-in charting for many clinicians.
The copy-paste step is real, and worth naming plainly. You do move text by hand into the chart. In exchange you get a documentation tool that is the same on assignment one as assignment fifty, with no dependency on any facility’s IT calendar. For most locums, that trade is easy.
Setup between assignments
Setup is a login, not a project. There is nothing to install at the facility and nothing for their IT team to approve on the scribe side. Confirm the BAA with whoever the covered entity is for your engagement, set which practice your notes file under, and you are documenting on your first patient.
If you are weighing options, our guide on how to evaluate an AI medical scribe walks through the questions that matter, and the best AI medical scribes overview puts the category in context. On compliance specifics, the HIPAA, BAA, and consent page covers what to check before your first documented visit.
Ready to see it against your own workflow? Book a demo and bring the messiest assignment you can think of. We will show you the note coming back in about two minutes, on whatever screen happens to be in front of you.