Skip to content

Best practice for mapping visit_detail_concept_id value #94

Discussion options

You must be logged in to vote

Thanks, @heschmidt04, for following up on this question!

@mkrile38 - thanks for the question! The visit_detail_concept_id field is reserved for concepts in the VISIT domain only, and we advise you to not use concepts from other domains in this field. Many different OMOP-related tools rely on proper domain association of concepts to work properly, and VISIT_DETAIL is no exception. If you have source descriptions without any reasonable match in the VISIT domain, it's possible that we can create CHoRUS specific concepts for VISIT_DETAIL events that match your descriptions. Let's plan to discuss further offline

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by jshoughtaling
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
standards question Item requires response and endorsement from StandardsTeam
3 participants