Unite measurement into observation (or observation into measurement)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
Assignment of concept to a table requires maintenance. (domain of a concept). It is a burden that can be avoided and has no major value.
Most ETLs start with a unified table anyway and split based on athena concept domain.
Unifying those 2 tables would make the model better.
It would also harmonize better with other standards (e.g., FHIR that relies on Observation resource).
It would allow simpler thinking for Oncology extension and image extension.
It is hard to explain to folks where the boundary of measurement and observation exactly is.
Implementation can be gradual where a view is created of a unified table such that existing data pipelines can be somewhat re-used.
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
The issue names the measurement and observation tables but no files or tests; begin by reviewing their definitions and the existing data pipelines that depend on them. Determine whether a unified table or compatibility view is intended, and document the agreed boundary and migration criteria before implementation.
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
- Needs clarification
- Newbie friendliness
- 25/100