[Proposal] Add "event_id" and "event_field_concept_id" columns to PROCEDURE_OCCURRENCE

Open
#569 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
databases

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.

Description

2025 Symposium Proposal

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! :-)

Dominant language
HTML
Stars
1.1k
Forks
513
Avg merge
8d 3h
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OHDSI/CommonDataModel

All issues in OHDSI/CommonDataModel

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.