[GH-ISSUE #85] Source_to_concept_id, mogen niet in source_to_concept in omop komen #50

Closed
opened 2026-03-23 20:28:43 +00:00 by mirror · 1 comment
Owner

Originally created by @kdenturc on GitHub (Jul 1, 2024).
Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/85

Originally assigned to: @pjlammertyn on GitHub.

Source_to_concept aanpassen, gezien dit non-standard zijn, is geen mapping!

Originally created by @kdenturc on GitHub (Jul 1, 2024). Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/85 Originally assigned to: @pjlammertyn on GitHub. Source_to_concept aanpassen, gezien dit non-standard zijn, is geen mapping!
mirror 2026-03-23 20:28:43 +00:00
Author
Owner

@pjlammertyn commented on GitHub (Jul 2, 2024):

Kim, correct:

The source to concept map table is recommended for use in ETL processes to maintain local source codes which are not available as Concepts in the Standardized Vocabularies, and to establish mappings for each source code into a Standard Concept as target_concept_ids that can be used to populate the Common Data Model tables.

<!-- gh-comment-id:2202485750 --> @pjlammertyn commented on GitHub (Jul 2, 2024): Kim, correct: The source to concept map table is recommended for use in ETL processes to maintain local source codes which are not available as Concepts in the Standardized Vocabularies, and to establish mappings for each source code into a **Standard Concept** as target_concept_ids that can be used to populate the Common Data Model tables.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
RADar-AZDelta/archived-Rabbit-in-a-Blender#50
No description provided.