Minute Book, home
Coroner’s reportPrevention of future deaths · 2024-0269

“Multiple witnesses indicated that the Risk Assessment Tool on the online system (EPJS) is…”

Dated 17 May 2024, from the coroner for Inner North London. Sent to 3 organisations or people.

A coroner wrote this report after an inquest, to warn the organisations below about a risk of further deaths.

Read the full report on judiciary.uk

How this works

The 56-day response deadline

All responses published

Replies were due by 12 Jul 2024.

Organisations that receive a report must reply to the coroner within 56 days, saying what they will do or why they will do nothing. We show whether a response is published on judiciary.uk; a reply may have been sent and not yet published.

  1. Report dated17 May 2024
  2. Deadline12 Jul 2024
  3. Published on judiciary.uk20 May 2024
  4. Today23 Oct 2026

Watch this report

We’ll email you when a response is published on judiciary.uk, or when the 56 days to reply end with none published there yet. Free, and you can stop with one click.

Next we ask your name, then send a link to confirm and create your free account. Already have an account? Sign in

Responses from each recipient

The coroner’s concerns

– Multiple witnesses indicated that the Risk Assessment Tool on the online system (EPJS) is not used in line with policy (i.e. that a new assessment in that tool is undertaken at the time of each admission/discharge/major risk event etc.), and, if updated, may only be updated in so far as additional narrative is added to the last such narrative in a previously completed assessment. Further, the evidence was that rather than be used for a detailed assessment per the indicators set out in the tool at the time of each relevant event, it was reviewed to instead access any past assessment in order (only) to establish quickly a benchmark against which the gauge a patient’s current presentation when considering their risks. The detailed indicators informing the risk assessment were not updated. Although it was submitted that patient risk was nonetheless assessed and recorded in the EPJS, and acknowledged that benchmarking/comparison is useful, I am concerned that: (1) if the risk indicators set out in the tool are not systematically reviewed or reconsidered, then the assessment of risk that follows will then be based on incomplete, and therefore misleading, information; and (2) absent the above, and dating of revisions within a compound document, it is not clear on what indicators any assessment is in fact based (3) to the extent the risk assessment is used as a benchmarking tool, the impression given to the most recent viewer is then likely to be incomplete and misleading; (4) the apparent current use of the tool to establish a point of benchmarking/comparison is in any event lost where the compound narrative assessments are not clearly dated and signposted ; (5) if the detailed patient assessment is instead placed as a new entry in the general chronological notes, the usefulness of the tool as a clear, well signposted, dated assessment and documentation of the patients of risk(s), is lost, requiring a reviewer to instead review the general chronological log of entries on the EPJS where it is not required to be articulated in the same terms, and may be more difficult to identify in a longstanding patient.

An extract. Read the full report, including the circumstances of the death, on the Courts and Tribunals Judiciary website.

Source
judiciary.uk, Prevention of Future Deaths reports, 2024-0269
Added to Minute Book
8 Oct 2026
Reuse
We show short extracts and link to the original. We don’t host the full report.

Something wrong, such as a date or who it was sent to? Report a mistake

Is this report about someone close to you? You can ask us to remove names from our pages.

Contains public sector information licensed under the Open Government Licence v3.0. Source: Courts and Tribunals Judiciary, judiciary.uk. Open Government Licence v3.0

Ask about this report

AI

Summaries and questions, with page references. Pro and above.

Sign in to use