For PCN leadership
Consistent workflows across member practices.
Networks share pharmacists, rules and ambitions across practices with different habits and systems. Reedley is designed to support consistent workflows across member practices while keeping each practice as the boundary for its patients’ data.
The demo has three synthetic scenarios to choose from.
In practice
Shared roles. Separate data.
How a network would be designed: three member practices, each its own boundary, and a shared pharmacist team that works inside them only under a grant. Design intent for the parts that are not built.
- Practice-level separation (development repository)
- Role-based access · every attempt recorded (screens only)
- Append-only history
- Practice = data controller · DPA + DPIA per practice
- Own teams and routing, within the floors
- Practice-level separation (development repository)
- Role-based access · every attempt recorded (screens only)
- Append-only history
- Practice = data controller · DPA + DPIA per practice
- Own teams and routing, within the floors
- Practice-level separation (development repository)
- Role-based access · every attempt recorded (screens only)
- Append-only history
- Practice = data controller · DPA + DPIA per practice
- Own teams and routing, within the floors
Choose a practice, or point at one, to see a grant: by design, the only way a network role would reach a practice’s data (the mechanism is tested at the storage layer in the development build; no network view uses it). Nothing is pooled; no line leads to a clinical system.
Design intent · grant: Network pharmacist team → Practice 1 (synthetic) · purpose: medicines review · until 30 Nov 2026 · approved by the practice · every access would be recorded. Routed within the practice under this grant; nothing leaves it.
Design intent · grant: Network pharmacist team → Practice 2 (synthetic) · purpose: monitoring follow-up · until 14 Nov 2026 · approved by the practice · every access would be recorded. Routed within the practice under this grant; nothing leaves it.
Design intent · grant: Network pharmacist team → Practice 3 (synthetic) · purpose: discharge reconciliation · until 7 Nov 2026 · approved by the practice · every access would be recorded. Routed within the practice under this grant; nothing leaves it.
01 Shared rule packs
Rule packs designed to be versioned and owned by named clinicians, applied consistently across practices. Today: no named owner; needs clinical sign-off.
Practice-level separation in the development repository · Built · synthetic data · enforced by Reedley’s screens only; no authenticated user, not yet a security boundary; not a deployed production database
02 Shared roles, separate data
By design, network staff would work across practices only through explicit, scoped and time-bound grants (the mechanism is tested at the storage layer in the development build; no network view uses it). Choose a practice to see one grant.
03 Comparable completion
The same lifecycle and definitions in every practice, so completion means the same thing. A network view of it is design intent, not built.
Network-level views: planned, not built. No PCN-level numbers are shown because none exist.
04 Room to differ
Practices keep their own teams and routing, within the review-level floors (draft, awaiting CSO sign-off).
No practice uses Reedley yet · Tested on synthetic data only · No EMIS Web or SystmOne integration claimed
Designed for you
Built around how the work is really done.
Consistency
One lifecycle and one vocabulary across member practices.
Clear data boundaries
By design, the practice is the data boundary; network views are granted, never assumed.
Support for shared pharmacists
Work routed to network-employed pharmacists with the context they need in each practice.
Governed rules
Rule packs are designed to carry authority levels and named owners (none yet); practices cannot lower the review-level floors (draft, awaiting CSO sign-off).
Network questions
Where are the monitoring gaps across the network, and is work being finished?
Auditability
By design, every cross-practice access would be recorded with its grant and purpose. The grant mechanism exists in the development build and is tested at the storage layer; no network view uses it.
Honest status
Where the relevant capabilities stand.
As at 14 November 2026. Nothing here is in use with real patients.
| Capability | Status | Before real use |
|---|---|---|
| Practice-level separation in the development repository | Built · synthetic data | Enforced by Reedley’s screens only; no authenticated user, not yet a security boundary; not a deployed production database |
| Cross-practice scoped grants | Planned | Design intent (architected, ADR-011); not built |
| Versioned rule packs | Needs clinical sign-off | No national or ICB pack with a named owner yet |
| Network-level views | Planned | Designed to be expressible; not built |
| Live integration | Needs supplier approval | No integration exists or is claimed |
The platform pages use three public states for the same facts: “Built · synthetic data” and “Needs clinical sign-off” are in the development build (synthetic data; draft rules unsigned), “In development” is partly built, and every other status here is not built. An illustrative demonstration can show parts that are not built.
Not sure where to start? Take the five-question assessment
Can network staff see every practice’s patients?
No. By design, a network role would reach a practice’s data only through an explicit, scoped and time-bound grant that the practice approves, with every access recorded. The grant mechanism exists in the development build and is tested at the storage layer; no network view uses it. In the development build each practice’s synthetic data is kept separate, enforced by Reedley’s screens only; there is no authenticated user yet, so this is not yet a security boundary.
Could a network pilot Reedley?
Yes — we would welcome networks as pilot partners, starting with synthetic walkthroughs across member practices.
Does it work across EMIS Web and SystmOne practices?
The design is system-neutral, but no integration with either exists or is claimed yet.
Pilot interest
Help shape Reedley before it is finished.
We are looking for a small number of GP practices and primary care networks to work with us: first on synthetic walkthroughs, then — only with the right approvals, safeguards and agreements — on carefully governed evaluation.
- 01Register interestA short form. We reply personally to arrange a conversation. No commitment. Or request a demonstration
- 02Synthetic walkthroughYour team uses Reedley on synthetic patients and tells us what is wrong with it.
- 03Structured feedbackTimed tasks and short interviews, reported honestly, including what did not work.
- 04Governed evaluationOnly with a CSO-approved safety case (DCB0129), the practice’s DCB0160, an MHRA device determination, DSPT, a DPIA, a data processing agreement and supplier approvals in place.