Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide on naming of polymorphic columns in EPISODE_EVENT table. #20

Closed
mgurley opened this issue Dec 6, 2018 · 1 comment
Closed

Decide on naming of polymorphic columns in EPISODE_EVENT table. #20

mgurley opened this issue Dec 6, 2018 · 1 comment
Labels
Modelling
Milestone
Sprint 1

Comments

@mgurley
Copy link
Collaborator

mgurley commented Dec 6, 2018 •
edited
Loading

In the most current version of the Oncology/Episode of Care Combined Proposal #23, the polymorphic pair of columns that allow the EPISODE_EVENT table to reference any clinical event table are named 'event_id' and 'event_table_concept_id'. This diverges from the current OMOP naming convention for polymorphic column pairs:

  • NOTE.note_event_id, NOTE.note_event_field_concept_id
  • COST.cost_event_id, COST.cost_event_field_concept_id

Options:

  • EPISODE_EVENT.event_id, EPISODE_EVENT.event_table_concept_id
  • EPISODE_EVENT.event_id, EPISODE_EVENT.episode_event_field_concept_id
  • EPISODE_EVENT.episode_event_id, EPISODE_EVENT.episode_event_field_concept_id
@mgurley mgurley changed the title Decide on naming of polymophic columns in EPISODE_EVENT table. Decide on naming of polymorphic columns in EPISODE_EVENT table. Jan 11, 2019
@mgurley
Copy link
Collaborator Author

mgurley commented Jan 17, 2019

Decided on the following:
EPISODE_EVENT.event_id, EPISODE_EVENT.episode_event_field_concept_id

@mgurley mgurley closed this as completed Jan 17, 2019
@mgurley mgurley added this to the Sprint 1 milestone Jun 6, 2019
@mgurley mgurley mentioned this issue Jun 6, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Modelling
Projects
None yet
Milestone
Sprint 1
Development

No branches or pull requests
1 participant
@mgurley