The-Strategy-Unit / The-Strategy-Unit/open-plan-docs
Align definitions of acuity in classification register with nhp_data
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 1
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 14
Description
Definitions here https://github.com/The-Strategy-Unit/nhp_data/blob/38c68b59715daea218f4eea1e00cd381bbd41cb8/src/nhp/data/raw_data/ecds.py#L58-L64
What's the best way to do this - just link to nhp_data? otherwise we risk having it defined in two places - need to remember to update both if anything changes
this is used in CLASS_AE_MINOR, CLASS_AE_MAJOR and CLASS_AE_RESUS
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the classification register's acuity definitions with src/nhp/data/raw_data/ecds.py lines 58-64 in nhp_data. Trace where CLASS_AE_MINOR, CLASS_AE_MAJOR and CLASS_AE_RESUS are defined or documented, then determine how the register should reference the authoritative definitions. Done means the definitions are aligned without requiring updates in two places.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100