[Proposal] Add "event_id" and "event_field_concept_id" columns to PROCEDURE_OCCURRENCE
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
I think the PROCEDURE_OCCURRENCE table is missing the option to link it to other tables and their primary keys. This would be similar to event_id and event_field_concept_id in tables such as MEASUREMENT or OBSERVATION.
A real-life example would be a procedure performed on a physical object or part of it (e.g. hemodialysis machine).
Let me know, what you think! :-)
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 comparing the PROCEDURE_OCCURRENCE definition with the MEASUREMENT and OBSERVATION tables, focusing on their event_id and event_field_concept_id columns. Review the issue discussion to determine whether links to physical objects fit the model; done requires an accepted design and corresponding model definitions, but the payload names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100