Platform overview
Five themes. One connected workflow.
Letters, results, requests and monitoring enter one shared engine; Reedley prepares the work with its evidence; clinicians review and decide; the record of what happened stays.
- Thirteen capabilities across clinical intelligence, medicines, documents, monitoring and operations.
- One status per capability: in the build, illustrative or planned.
- Every demonstration runs on synthetic data, labelled.
Thirteen capabilities, five themes
5 in the development build · 8 illustrative demonstrations
What each status means
- In the development build · synthetic dataThe workflow runs in Reedley’s development build on synthetic patients. The demonstration on this site is a scripted reconstruction, not the build itself: illustrations based on the development build; some frames show intended behaviour the build does not yet have. No practice uses it and no live record is connected.
- Illustrative demonstration · intended workflowA scripted demonstration of how the workflow is intended to work. Parts of it are not built yet.
- PlannedDirection of development. Nothing exists in the build yet, and no date is given.
Clinical Intelligence
Questions, context and reviews drawn from the record, every line with its source.
Ask Reedley
Questions about one patient, answered with their sourcesIn the development build · synthetic dataOpenClinical IntelligencePatient Context
What is new since the last review, linked to sourceIn the development build · synthetic dataOpenClinical IntelligenceMedication Review
Medicines, results and letters assembled for a reviewIllustrative demonstration · intended workflowOpenMedicines and Prescribing
Medication changes, shortages and requests, laid out for the prescriber’s decision.
Medication Reconciliation
Letter against record, differences ready for reviewIllustrative demonstration · intended workflowOpenMedicines and PrescribingMedicines Shortages
The patient and product factors a prescriber weighsIllustrative demonstration · intended workflowOpenMedicines and PrescribingComplex Medication Changes
Specialist letters structured into instructions, questions and plansIllustrative demonstration · intended workflowOpenMedicines and PrescribingPrescription Requests
Each request shown with the context a prescriber needsIn the development build · synthetic dataOpenDocuments and Workflows
Letters turned into evidenced work, and one worklist that carries it to the end.
Monitoring and Population Health
Results, shared care and practice-wide monitoring, followed through to evidence.
Results and Monitoring
Results linked to why they were requested and followed upIllustrative demonstration · intended workflowOpenMonitoring and Population HealthShared Care
Responsibility, monitoring and outstanding actions for high-risk medicinesIllustrative demonstration · intended workflowOpenMonitoring and Population HealthPopulation Surveillance
Practice-wide medicines monitoring work, leading to named patientsIllustrative demonstration · intended workflowOpenOperations and Governance
Where clinical work waits, who owns it, and the record of who decided what.
Practice and PCN Intelligence
Where clinical work is waiting, and whether it finishesIllustrative demonstration · intended workflowOpenOperations and GovernanceSafety and governance
Human review, evidence, audit and the work still aheadDesign commitments, work in the build and independent evidence, kept apartOpenOne workflow beneath every capability
Identified, reviewed, assigned, actioned, verified, closed.
Every item of work travels the same six stages once, with a named owner. A person’s report moves an item to actioned; verification comes from the record where Reedley can read it; where it cannot, a named person’s structured statement is accepted today, and that rule is under review.
Illustrative · one item travels the lifecycle onceSynthetic example
Funmilayo ADEYEMI NHS 999 000 0069
Renal function (U&E) 1–2 weeks after the dose change
Investigation · administrative
Show all eventsHide the event list(6)
- 4 Oct 2026 · 10:05ReedleyIdentified from ¶3 of the clinic letter: “recheck renal function in 1–2 weeks”.Source passage cited (¶3). Depends on the ramipril dose change being recorded.
- 4 Oct 2026K. AHMED, clinical pharmacistEvidence checked against the letter and the record; task accepted.
- 4 Oct 2026K. AHMED, clinical pharmacistOwner: Admin team · window 11–18 Oct, 1–2 weeks after the dose change recorded 4 Oct.
- 5 Oct 2026Admin teamU&E requested 5 Oct.Reported by the owner · not yet proven.
- 14 Oct 2026 · 09:12Reedley · from pathology as received in the record (Simulated)Pathology result received into the record.Result received 14 Oct 09:12 · test completed · not yet reviewed (Simulated).A received result is not a reviewed result. Designed to stay open until a clinician’s review is recorded (the development build closes it on receipt).
- 14 Oct 2026 · 16:10Reedley · from the clinical record (Simulated)Clinician review recorded in the clinical record.Reviewed by K. AHMED 14 Oct 16:10 (Simulated).Shows that a review was recorded, not what it concluded. Reedley does not interpret results.
Awaiting a named person’s review.
Owner and due date to be set.
The owner arranges the blood test and records what was done.
Waits here until a result is received from pathology.
A separate review item goes to K. AHMED, due today.
Closed · completed after the review was recorded.
Illustrative concept · not clinical rules · source checks are simulated; automatic checking needs approved access to each source.
See it with your own work in mind.
Tell us your role and the workflows you care about, and we will walk you through them on synthetic data.