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

Explain the baseline adjustment in a short example

Open Beginner friendly
#703 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Maybe in the explanatory box, add something like:
"This adjustment accounts for activity numbers (admission or attendance) that maybe under or over counted at the hospital trust. It relates to Hospital Episodes Statistics (HES) data (from providers) via Secondary Users Service (SUS). The adjustment required is the Percentage adjustment to the baseline data currently extracted for your trust for each POD/specialty.

For example, if our baseline data showed you had 10,000 general surgery admissions, but your local data shows you had 12,000, you may want to add in these 2000 'missing' admissions before modelling. To do this, you could move the slider beside the 'General Surgery' heading to the right until the label in blue reads '2000'. The 'relative change' then shows you the multiplier which will be used to increase the counts of this activity type in the data. In this instance this would be 12,000 / 10,000 = 1.2.

Please provide the reason for your adjustment and cite an evidence base.

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 by locating the explanatory box in the Shiny app and read the surrounding guidance for baseline adjustments. Add the supplied hospital admissions example and evidence-base reminder, then run the app and confirm the explanation renders clearly beside the relevant adjustment controls.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.