The Cohort Runner runs a cohort against your own practice data and shows you who is in it. Instead of opening a specific KPI, search or audit and running it from inside that editor, you pick a source from one place, run it, and keep the result open while you run the next one.
It is an à-la-carte package — see Platform tiers and à-la-carte packages.
What you can run
Pick a source at the top of the page:
- KPI flow — a KPI built in the KPI designer
- QOF indicator — the current QOF business rules (v61)
- EMIS search — browse your search folders as they are actually structured, plus two shortcuts: Live searches (the current released view) and Published (the curated published area)
- Semantic audit — a semantic audit search
Running and comparing
Choosing a source opens a results tab. Tabs stay open, so you can run several cohorts and compare them side by side rather than losing the previous answer each time you run something new.
For each run you can see the count, a breakdown, or the patient list, and pick which practices to include when your account covers more than one.
Snapshots, sharing and export
- Snapshot — save a point-in-time capture of a result, so a number quoted in a meeting can be reproduced later even after the underlying data moves on.
- Share — a snapshot can be opened as a read-only link.
- CSV export — export the result from the run panel.
What the numbers are based on
Runs execute against the patient data already ingested for your organisation — the same data behind your Local-data dashboards. You only ever see your own organisation's patients: every run is scoped to the practices your account can access, and a run with no accessible practice is refused rather than widened.
If your practice's data has not finished its first ingest, cohorts will run but return nothing — see Data protection and where the data comes from.
Access
The Cohort Runner appears in your menu when your organisation holds the Cohort Runner package. If you can't see it and think you should, ask your organisation admin — or see Why can't I see a feature?.
Related articles
Related Articles
Getting started with dashboards
The Dashboards menu is where you benchmark your organisation and explore performance data. All the benchmark views are built from published NHS data — aggregate figures with no patient-identifiable information — so they work for every account, ...
Getting started with Medicus Dashboards
Resources → Medicus Dashboards lets you assemble custom dashboards for Medicus from QOF indicators — build the view you actually want in your clinical system, save it in Nexus, and regenerate it whenever the contract changes. Building a dashboard New ...
What is Nexus?
Nexus, from Primary Care IT, is a primary care intelligence and clinical tooling platform for NHS general practice. It brings together, in one place: Benchmarking dashboards — compare your practice, PCN or ICB against peers and the national picture ...
Getting started with Medicus Searches
Resources → Medicus Searches is the search builder for Medicus sites: design patient searches and activity reports here — with code lists, dates, demographics and logic — then export them as upload-ready XML for Medicus, instead of writing them in ...
Finding your way around
Everything in Nexus is reached from the header at the top of the app. What you see depends on the packages your organisation holds and your role — menus you are not entitled to are simply not shown. The header menus Resources — everything your ...