Safety and governance
Integration and compatibility, without the partner language.
Reedley is designed for UK primary care, including workflows around EMIS Web and SystmOne. No integration with either exists or is claimed today. This page explains what that means, and how it would change.
Statements reviewed 14 November 2026. Reedley is in development; nothing here describes a live service.
Today
The Reedley build runs against a simulated clinical system. It declares what each kind of integration route could and could not do, so that the product never assumes a capability a supplier has not provided. There is no connection to EMIS Web, EMIS-X or SystmOne, and no supplier has approved, endorsed or partnered with Reedley.
Product names are used only to describe the environments Reedley is designed for. We do not use supplier logos.
Routes to approved integration
The main national route for third-party software to integrate with GP clinical systems in England is IM1 (Interface Mechanism 1) pairing. It has defined stages — initiation, unsupported test, supported test, assurance and live — and requires evidence including a supplier conformance assessment, a DCB0129 safety case and hazard log, and a DPIA.
NHS England states that IM1 pairing does not include AI-specific technical assurance. Reedley would need to carry and evidence that assurance itself, and deploying organisations would assess it locally.
What integration would and would not allow
From our research of published documentation, with every item to be confirmed directly with suppliers:
- Reading patient demographics, medications and parts of the record is documented for both systems in various forms. Item-level detail is unconfirmed.
- Filing documents into the record is documented for some routes.
- Writing to the medication record — adding, stopping or changing a medicine — is outside Reedley’s design: Reedley does not write to the medication record and does not claim to. Whether any supplier route would permit it is not established on current evidence; no application has been made.
- Pathology results: we have not found a documented route for a third party to receive results directly, so Reedley’s design reads results once they have been received into the practice’s clinical record (alongside, never instead of, the practice’s own review of every result), with approved access.
Permissions, data sharing and human authorisation
- Any integration would act under the practice’s instructions as data controller, with a data processing agreement and the practice’s own DPIA.
- Access would be limited to the scopes the practice and supplier approve, and each Reedley role would see only what it needs.
- Reedley never writes to the medication record; a task or coded entry is handed to the clinical system only where a route allows it and a named person decides, and in the build that is simulated. Whether any supplier route would permit medication write-back is not established on current evidence; no application has been made.
Status ladder
Where integration stands.
We will move up this ladder publicly, one evidenced step at a time.
- 1Designed forReedley is designed around workflows in EMIS Web and SystmOne practices, using a simulated clinical system in development.Current
- 2Enquiry madeFormal enquiries to the relevant supplier and national programmes. Not yet made.
- 3Access granted for testingFor example, initiation of IM1 pairing with access to a mock or test environment.
- 4AssuredAssurance completed for a defined scope, such as IM1 “Recommended to Connect”.
- 5Live with a practiceRunning for a practice under a governed pilot, for the assured scope only.