OHDSI / OHDSI/FeatureExtraction
Operator concept_id is not considered for measurement values
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 74
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
Since CDM supports operator_concept_id for measurement table it makes sense to consider it while covariate construction.
Currently, if for example '>6' and '<=6' are met for some measurement id data, both are treated as '6' for covariate.
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 file or test is named. Trace the measurement covariate construction path and inspect how measurement values are normalized when operator_concept_id is present. Use cases such as >6 and <=6 for the same measurement ID to verify that operator distinctions are preserved when the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100