mirror of
https://github.com/RADar-AZDelta/Rabbit-in-a-Blender.git
synced 2026-03-23 20:37:03 +00:00
[GH-ISSUE #85] Source_to_concept_id, mogen niet in source_to_concept in omop komen #50
Labels
No labels
bug
cannot reproduce
duplicate
enhancement
experiment
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
RADar-AZDelta/archived-Rabbit-in-a-Blender#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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!
@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.