opensafely-core / opensafely-core/opencodelists
Definition Builder feature request - Include/Exclude all at the level of Top Level Concepts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
When searching for a keyword, it is often obvious to me that I want to include/exclude all codes from a particular Top Level Concept e.g.
When I was building a list today of 'Care pathway landmarks for Cataract Surgery' codes, I wanted to include codes such as |Cataract surgery and children| but I didn't want any (disorder) codes.
To eliminate the codes from trees I knew I didn't want, I had the following clicks to make:
- (disorder) 16 times
- (finding) 2 times
- (Foundation metadata concept) 1 time
- (morphological abnormality) 2 times
- (observable entity) 1 time
- (organism) 1 time
- (physical object) 1 time
- (qualifier value) 2 times
Two things could have improved my speed of building the list
- if I could toggle the types of Top Level Concepts that I queried (for example, I know already that for my line of work, I almost never want to query (foundation metadata concept) (organism) (physical object) (qualifier value) codes, so would like to update my 'profile' with Search Preferences (that would have saved me 5 clicks in this keyword search)
- If there was a [+/-] button on the Top Level Concept so I could bulk exclude those codes (that would have saved me 18 individual clicks in dealing with this particular keyword's results alone)
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
Start by locating the Definition Builder and the Top Level Concept controls described in the issue, then review how keyword search results are selected. Done should include a way to include or exclude all codes under a Top Level Concept; the requested Search Preferences profile behavior is also addressed or clearly scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100