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

Modifying the determination of peers for comparison

Open
#515 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The document here was discussed at dev board on 2025-06-25, having taken into account DS team comments on the document. The plan agreed on was that the population-based model peers should be as described in that document, but for schemes, the current peer set would be retained for now.

However, we should look to take up the medium level option in the future:

"⭐ Medium effort (preferred method)

Generate a simple, clear methodology for determining peers, which will be applicable across all geography types (e.g. just based on demographics of patients). Publish this and replace the current peers with those chosen by this method.

The risk here is that schemes may not want their peers to alter as they have workflows set up internally to report against a fixed set of comparators. We would need to communicate thoroughly. A method simple enough to apply to all our geography granularities may be viewed as over simplistic by some, and thus, again, not appropriate for the creation of valid comparator sets. "

This issue is to capture this to ensure it is not forgotten about!

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.

Research direction

Start with the linked “Demand modelling peers” document and the 2025-06-25 dev board decision. Define a simple peer-selection methodology applicable across geography types, then assess how it would replace the current peer sets while accounting for scheme reporting workflows and communication needs.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.