The-Strategy-Unit / The-Strategy-Unit/nhp_inputs

Draft wording to explain the implications of setting the waiting list option for a specialty

Open
#689 0 comments 0 reactions 1 assignee View on GitHub

@StatsRhian is already working on this.

Since Jun 23, 2026.

documentation
Dominant language
R
Stars
2
Forks
1
Avg merge
15h 39m
Merged PRs (30d)
6

Description

Dev board asked me to show them the wording that would explain the effects of the interim fix to the WL module when their horizon year is set before or after the target year, since the change to activity may be unintuitive. I drafted the below, but we then paused work to 'relitigate' the proposed methodology. If the same caveat is needed when the module is built, @StatsRhian will modify the text below and @DCEW will take it to dev board for sign off before the module is released.

"To clear a waiting list, more activity needs to be undertaken in addition to the
usual activity, for a period of time. After that period, the rate of activity
can reduce to a steady state as it only needs to clear newly-added patients.

When you use this module, if your model horizon year would occur before the target
waiting list reduction year, your predicted activity rates will be inflated to
account for the increase needed to clear the backlog. If your horizon year would
fall after the target year, the horizon year's predicted activity rate will be
lower than it has been before as it only needs to match the rate at which new patients
are added to the list.

To summarise;

  • where horizon year < target, activity will be increased
  • where horizon year > target, activity will be low (possibly lower than current rates)"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.