opensafely-core / opensafely-core/opencodelists
Simple reusable high cost drugs medication builder
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
Currently our process for high cost drugs is to build the list locally in a csv and upload.
@myatesrheum has made a code builder in Stata and code/explanation is available here. Briefly you feed it a string of the generic name, brand name and assign any matches a VTM dmd code.
@myatesrheum has made codelists for all our drugs in current study but it would be great to reuse this code in future to allow anyone to create the codelists they require.
| Option | Pros | Cons | |
|---|---|---|---|
| Make the code easily discoverable for reuse | Easy and can sit in technical documentation for the moment? | Code is stata so requires some to have stata installed | |
| As above plus write additional code in R | Easyish - @AnnaB45 has made a start on R code that could be used for job R is openly | Still requires someone to have stata or R | |
| Write in python plus/minus the interface on OpenCodelists | Would be nicest and easiest for future users | Time! |
I think the first option is best for now as we have all codelists for current studies have been made and we have no polans for additional studies outside of the broad group of drugs in use.
Any further thoughts?
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
Read the Stata code and explanation linked from immunosuppressant-meds-research issue 29, then compare them with analysis/creating_adalimumab_code_list.R. Clarify which reuse option is being pursued and document or implement the chosen builder so future users can create the required codelists without reconstructing the existing study-specific process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100