CQC performance and CQC actions (Local data)

CQC performance and CQC actions (Local data)

The Ardens CQC search set, run against your practice's own clinical data and grouped under the five CQC key questions (Safe, Effective, Caring, Responsive, Well-led). It is delivered as two dashboards, sold separately, which link to each other when you have both:

  • Dashboards → Local data → CQC performance — *where are we at risk?*
  • Dashboards → Local data → CQC actions — *who needs what doing?*

Because these read clinical data, they are available only to users registered to your organisation, and every patient-level view is recorded in the clinical access audit.

CQC performance — where are we at risk?

A daily performance summary: every clinically confirmed search is computed automatically each day and shows clear (no patients flagged) or N outstanding of M (x%) — the proportion of the relevant register (for example, patients overdue bloods *of everyone on methotrexate*), with the change since the previous day. *Run* recomputes any search on demand.

If you also hold CQC actions, this page summarises actions needed ("12 need blood tests, 5 need blood pressure checks…"), and *Work through them* opens the actions dashboard.

CQC actions — who needs what doing?

Everyone needing each action across all searches at once, with the reason why (which search, how overdue). Tick the patients (all selected by default) and send booking invites or propose a recall activity for the whole batch — a patient overdue the same bloods on two medicines appears once, with both reasons.

Each requirement shows as a coloured chip: amber when it is past its monitoring window, red when it has never been done or is substantially overdue (past a longer "very overdue" threshold, where a search defines one).

Check against live data

Your worklists are built from an overnight extract, so a test done this morning still appears as outstanding. Check against live data asks your clinical system directly, for the patients you have selected, whether a qualifying entry now exists — and anyone confirmed done is shown in green ("done *date* · live"), marked *Already done — clears from this list at the next extract*, and removed from the selection so the next batch of invites cannot chase them.

Two deliberate limits:

  • It only ever moves someone from *outstanding* to *done* on positive evidence — a coded entry inside the monitoring window. If the live record cannot be read, the patient is matched unsuccessfully, or nothing is found, they stay outstanding and the chip says why.
  • The verdict is held until the extract catches up. It survives a reload, and disappears by itself once the overnight data lands (usually together with the patient dropping off the list).

Reading the live record is a clinical record access, and is recorded in the audit like any other patient-level view.

CrCl reviews (DOAC)

For the CrCl reviews (DOAC) action the view also shows each calculation input (creatinine, eGFR, weight) with its freshness, and tabs to work by what is missing (all inputs present · just weight · just U&E · both). *Calc* computes the creatinine clearance (Cockcroft-Gault) from the record for one patient on the spot. Calc all ready does the same for every selected patient whose inputs are current: it calculates all the results in one pass, shows them together with any DOAC dosing alerts and the exact code each would record, and — after you review, untick any you don't want, and confirm — records the coded results back into each patient's clinical record. Patients without an NHS number still show their result but cannot be recorded automatically.

Where your practice has signed off the DOAC renal thresholds, a result below the licensed range for the anticoagulant the patient is taking raises a review alert, and a result inside a dose-review band asks you to confirm the dose — with the current dose from the record shown alongside.

The per-search worklist

*Patients & actions* on any search (from CQC performance) opens that search's worklist (names and NHS numbers), sorted most out of date first, showing for each patient:

  • one column per requirement (for example U&Es, LFTs, BP, Weight, FBC for a DMARD search) — the last date each was done, with how many days ago; a date **outside the monitoring window — or *never* — shows red**. The dates are precomputed by the daily run, so the page opens instantly; *Recompute now* refreshes them live;
  • their next booked appointment, including the date, time and which practice member it is booked with;
  • their previous communications — the last SMS coded in the clinical record, plus booking links and recall activities sent from Nexus.

From there, generate booking links (for example, blood-test booking for a medication-monitoring search) or propose a recall activity (letters and messages through the communications pipeline).

What the statuses mean

These searches flag *possible* risks — patients who may need monitoring bloods, a medication review, a missing safeguarding code and so on. So:

  • clear — the search found no patients. Nothing outstanding.
  • N outstanding of M (x%) — the search found patients to review, shown against the size of the relevant register. This is a worklist, not a judgement: review each patient before acting.
  • ▲ / ▼ — the change since the previous day's computation.
  • approx — the count was computed with an approximation (the reason is shown when you hover). Treat it as indicative — this applies to "clear" too: an approximate zero is not a certified all-clear.
  • An error means the search could not run — usually a code group that is not yet available. Nothing is silently shown as zero.

One honesty note on communications: SMS messages sent from some clinical systems are not always written back to the coded record, so "none recorded" means none *recorded*, not necessarily none sent.

Coverage — and honest gaps

Only searches that have passed clinical review appear; newly ingested searches show as "awaiting clinical review" until confirmed. Responsive and Well-led show as genuinely uncovered: evidence about access, complaints, governance and staffing lives outside the clinical record, and this dashboard does not pretend otherwise.

What "on a medicine" means

Many searches run within a drug register — "on warfarin", "on a DOAC", "on methotrexate". A patient counts as on a medicine when they have an open authorisation for it and it has been issued in the last 3 months.

Both halves matter. A prescription that was never formally discontinued stays open in the clinical system indefinitely — every one-off acute script does, and so do superseded repeats. Counting those as current would put patients who stopped a medicine years ago onto a monitoring worklist that says they are overdue a blood test they no longer need.

The trade-off runs the other way too: someone whose repeat lapsed more than three months ago drops out of the register, even if the reason it lapsed is the very monitoring the search is chasing. If a patient you expect to see is missing, check when their prescription was last issued.

If your clinical system's feed does not include prescription issues, the three-month test cannot be applied — so it isn't. Those registers fall back to "has an open authorisation", they will include patients who stopped the medicine, and the search is marked as computed with approximations. We would rather show you a list that is too long and say so than quietly report "clear" because we cannot see the data.

Availability

Both are paid, practice-level add-ons — the free tier is unaffected and permanent — and both require your practice's clinical data feed, the same one behind the local QOF dashboards.

  • CQC performance is part of the Governance & Compliance package.
  • CQC actions is part of the CQC Action Management package. Recording results back into the record and checking against live data also need your clinical system's live connection to be enabled.

You can hold either on its own: with performance only you see the counts, percentages and trends but not the patient lists; with actions only you get the worklists and recall tools without the key-question overview. Your organisation admin can review packages under Account & billing.

    • Related Articles

    • QOF — live (Local data)

      Dashboards → Local data → QOF — live shows every QOF indicator computed directly from your practice's own clinical data, refreshed daily after the overnight data feed. Unlike the benchmarking dashboards (public, published data), this view is ...
    • Childhood immunisations (Local data)

      Dashboards → Local data → Childhood immunisations shows every child under 5 registered at your practice against the QOF childhood vaccination schedule — who has had each vaccination, whose is due or overdue, whether an appointment is already booked, ...
    • Multi-KPI patients (Local data)

      Dashboards → Local data → Multi-KPI patients lists the patients who appear on several QOF indicators' outstanding worklists at once — the highest-leverage recall list in the building, because one contact can tick several boxes. What's on it Each ...
    • Data protection and where the data comes from

      Two kinds of data, kept apart Published NHS data powers the benchmark dashboards, Funding & equity, Find a GP and AI Insights. It is public, aggregate data — QOF results, GP Patient Survey, workforce and payments publications, CQC ratings and so on — ...
    • Data quality (Local data)

      Dashboards → Local data → Data quality is the honesty page behind the local QOF numbers: it shows how fresh your ingested clinical data is, where the feed drops information, and any anomalies that change how the dashboards should be read. What's on ...