[Proposal] add person_id to the cost table
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
The OMOP CDM is a person centric data model and all the "facts" have an associated person_id.... except for costs. To add up the costs for a person in v5.4 we have to join the cost table to every other domain table in the CDM. I would like to propose adding a person_id column to the cost table.
One use case is to easily add up total costs per person which of course is supported but is a verbose query requiring lots of joins just to get the person id for each cost record. I believe this would be a non breaking change that could be done in a minor version.
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
Review the OMOP CDM v5.4 cost table definition and the repository's DDLs first. Determine the schema and versioning implications of adding person_id; the work is done when the proposal has an agreed implementation scope and the affected definition and DDLs are updated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100