opensafely-core / opensafely-core/opencodelists
Medicines definition builder
@sebbacon is already working on this.
Since Sep 8, 2020.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
In the longer term we need to think about building a medicines definition/codelist builder in the same way that we build for clinical terms. Briefly out current methodology is
- we choose BNF codes terms to be in a codelist
- dm+d is the common language of EHRs in english primary care and core of OpenSAFELY meds software
- we utilise OpenPrescribing google BQ to match this to dm+d and generate a codelist via a SQL query
We have built up a library on OpenCodelists and another interim step would be to run off every section in BNF and put up on OpenCodelists with a "buyer beware" caveat.
Benefits building a definition builder would
a) allow anyone to build a medicines codelist (i.e. don't need access to BQ or have SQL skills)
b) have a clearer inclusion/exclusion interface
Not a benefit but we should give some thought how it might fit in with OpenPrescribing infrastructure like analyse page, dm+d browser etc and any potential future tools (e.g. hospital meds data).
In order to build we need a hierachy that makes sense to humans and computers! Both of the immediately obvious options have pros and cons.
| Meds coding system | Pros | Cons |
|---|---|---|
| BNF codes | Well defined categories that are clinically relevant, machine and human readable, a med can only appear in a single place, | not dm+d our common meds language, comprehensive for primary care meds but not for meds in secondary care, a med can only appear in a single place |
| NHS Dictionary of medicines and devices | Common language of opensafely EHRs, meds appear in multiple places | It does not contain a clinical hierarchy (see #177) |
I think ideally we would have both options available in a search function recognising limitations of both. There may be other hierarchies that could be useful. Can anyone suggest some?
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.
Assessment
This issue has not been assessed yet.