opensafely-core / opensafely-core/opencodelists
Can we handle items that are removed from dm+d or BNF?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
Sometimes, items are removed from the dm+d or the BNF. (This may also happen to ICD-10 and other coding systems.)
In the dm+d, if a product is replaced by another product, the new product has a link to the old product's ID.
It would be good if old items were still searchable, and could be mapped to from BNF codes.
This would require us to keep records of removed items forever, which is a small-medium architectural change, and would require us to find historical dm+d and BNF data. We have incomplete historical data from past OpenPrescribing imports, but this wouldn't contain all removed codes.
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
No files, tests, or entry points are named. Start by tracing the existing dm+d and BNF import paths and search or mapping behavior, then assess the historical data available from past OpenPrescribing imports; done means removed items remain searchable and BNF codes can map to them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100