Create model for dissecting the sig field into computable structured data
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
This is a placeholder, so a proposal could be worked out:
Instead of the free text sig field (which may even be in a non-English language), we need to have the actual frequency information. So, 2 mL tablets 3 times a day" would become something like:
sig_amount - numeric (2)
sig_unit_concept_id - concept (concept_id for liquid units, most often "mL")
frequency - numeric (3)
frequency_unit_concept_id - concept (concept_id for "day")
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 reviewing the issue's proposed fields for replacing the free-text sig value with structured frequency data. No files, tests, or entry points are named, so the first step is to identify the relevant OMOP CDM model and establish the proposal. Done means an agreed model for representing amount, unit, frequency, and frequency unit, including non-English sig values.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100