Summary
Writing back into EMIS Web or SystmOne runs through the IM1 partner route, the NHS-approved integration pathway for third-party clinical applications, alongside the EMIS Partner API. That approval is a process with a queue, not a switch, so the question to ask a supplier is not whether they integrate but whether they are already through it, for your system, in general availability today. The published evidence keeps finding that the absence of integration is what stops a scribe saving time.
The most reliable finding in the scribe literature is not about accuracy. It is that a draft which has to be moved by a person does not save the time the product claims, and the Cleveland Clinic evaluation published in Digital Health named the absence of EHR integration as the reason its efficiency gains never arrived.
In English general practice that means EMIS Web and SystmOne, and it means the IM1 partner route, which is the NHS-approved pathway for third-party clinical applications to work with those systems. NHS England's ambient scribing guidance calls integration with the electronic patient record an essential requirement rather than a nice to have.
This is the part of a procurement where a roadmap is most often mistaken for a product, so the questions below are deliberately blunt.
See it in your clinicAsk us what is in general availability today, and what is on a roadmap, as two separate answers.
Request a demo| What it is | What it actually means for a clinic |
|---|---|
| Copy and paste | No integration. The saving is the typing, not the workflow |
| Clipboard helper or browser extension | Fewer keystrokes, still a person moving the note |
| Structured write-back via IM1 | The note lands in the record under the right patient |
| Write-back with problem and coding | Lands filed rather than just present |
| Context aware | Knows which patient is open, so nothing is filed to the wrong record |
| Documents as well as notes | Referrals and letters from the same capture |
What IM1 is
IM1, the Interface Mechanism, is the approved route by which a third-party application works with a principal clinical system in English general practice. It covers both reading from and writing to the record, and it is the pathway a scribe needs if the note is to arrive in the chart rather than on a clipboard.
EMIS also operates a Partner API, a controlled interface for approved third-party software to interact directly with EMIS Web. Approval is a process involving the supplier, the principal system supplier and the practice, and it takes time that is easy to leave out of an implementation plan.
The practical consequence is that a vendor saying they integrate with EMIS is not answering the question. Ask whether they hold IM1 partner approval, for which capability, and whether it is live for practices today rather than in development.
Where the note lands matters more than that it lands
A note that arrives in the record as free text under the right patient is a large improvement on copy and paste. A note that arrives filed against the correct problem heading, with author and timestamp metadata intact and codes attached, is a different product.
Ask what happens to coding. Suggesting a code for a clinician to accept is common and useful. Writing the code into the record without review is a different thing and, since the MHRA guidance of 29 July 2026, a feature that starts to move a product toward being a medical device depending on how it is framed.
Ask about patient context. A scribe that knows which record is open in Consultation Manager cannot file to the wrong patient. One that does not is relying on the clinician to check, which is the sort of control that holds until a busy Friday.
Why this is the question that decides the time saving
The Cleveland Clinic study of ten primary care physicians, published in Digital Health in 2025, found the only statistically significant change was 15,398 fewer characters typed. Time outside scheduled hours rose by 13.7 minutes a day rather than falling, and the authors attributed the missing efficiency to the lack of EHR integration.
That is the clearest available warning that a good draft and a saved hour are different purchases. The draft was fine. It still had to be moved by a person, and the moving is where the time went.
So when a business case rests on documentation minutes, the integration question is the one that determines whether the case is real. Our guide to building the business case works through what the published evaluations actually measured.
What is already in the building
Accurx sits in around 98 percent of English GP practices, and its Scribe has been reported as writing back to SystmOne and EMIS records and generating referral letters, advice and guidance requests and follow-up messages from the same capture.
For a practice already running Accurx that is the lowest friction trial available, and it would be dishonest to pretend otherwise. Try what is already in the building first, then make anything else beat it on your own consultations. Our comparison is in Accurx Scribe vs wai.
Other products reach EMIS through the Partner API and write through Consultation Manager's native path. The detail differs and the question to ask is always the same, which is what is live today for practices like mine.
Six questions that settle it
Which principal systems, by name, in general availability today. Do you hold IM1 partner approval and for which capability. Does the note arrive filed against a problem, or as free text. Do you write codes, and does a clinician approve them first.
Then the two nobody asks. What happens when the integration fails mid-clinic, because it will, and does the clinician lose the note or keep it. And what does the audit trail look like in the record afterwards, since the entry has to show who authored and who approved it.
Ask for a demo in your own record system rather than in the vendor's sandbox. A sandbox has one patient open and no interruptions, which is not a Tuesday.
Where wai sits
wai is built for private practice, where the record is ours rather than a principal clinical system, so the note, the letters, the coding and the follow-up sit on one record without needing a partner route at all.
That is an honest advantage in the setting it was built for and an honest limitation outside it. A practice whose record lives in EMIS or SystmOne should be asking the six questions above of every supplier, and should weigh what is already installed before anything else.
If the answer for your practice is Accurx, buy Accurx. Clinicians still decide what enters the record.
Bring your record system and your workflow. Fifteen minutes, on what actually lands where.
Request a demoFrequently asked questions
How does an AI scribe write into EMIS Web or SystmOne?
Through the IM1 partner route, the NHS-approved pathway for third-party clinical applications to read from and write to a principal clinical system, and for EMIS also through its Partner API. Approval is a process involving the supplier, the principal system supplier and the practice, which takes time that implementation plans often omit.
What is IM1?
The Interface Mechanism, the approved route by which third-party software works with principal clinical systems in English general practice. It covers reading from and writing to the record. A scribe needs it if the note is to arrive in the chart rather than on a clipboard for someone to paste.
Why does integration matter more than accuracy?
Because a good draft that a person still has to move does not save the time the product claims. The Cleveland Clinic evaluation found time outside scheduled hours rose by 13.7 minutes a day and attributed the missing efficiency to the absence of EHR integration. The note was fine. The moving was the cost.
What should I ask about how the note is filed?
Whether it arrives as free text or filed against the correct problem heading with author and timestamp metadata, whether codes are written and whether a clinician approves them first, and whether the product knows which patient record is open. A scribe that does not know the patient context relies on the clinician to catch a misfile.
Which AI scribes already write back to EMIS and SystmOne?
Accurx Scribe has been reported as writing back to both and generating referral letters and follow-up messages from the same capture, and Accurx sits in around 98 percent of English GP practices. Others reach EMIS through the Partner API. Ask any supplier what is in general availability today rather than on a roadmap.
Does writing codes make a product a medical device?
Suggesting a code from terms explicitly mentioned, for a clinician to review, is named in the MHRA guidance of 29 July 2026 as not a medical device. A product that acts on the record without clinician review is in different territory. The distinction is set out in our page on the NHS requirements.
What happens if the integration fails during a clinic?
Ask, because it will. The question is whether the clinician loses the note or keeps it locally until the connection returns, and whether the failure is visible or silent. A silent failure that drops a consultation is a clinical safety hazard and belongs in your DCB0160 hazard log.
Sources
What lands where, on your system
Fifteen minutes on your workflows. If it is a fit we reply within 24 hours.
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