Skip to content

value_as_concept_id mapping rule creation for table Observation and Measurement #1008

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.

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

Open
2 of 3 tasks
AndrewThien opened this issue Apr 7, 2025 · 1 comment
Open
2 of 3 tasks

Comments

@AndrewThien
Copy link
Contributor

AndrewThien commented Apr 7, 2025

Is this the right issue type?

  • Yes, I'm planning work for this project team.

Summary

Based on the attached description from OMOP CDM, there can be some concepts in the domains Observation and Measurement which have one additional relationship Maps to value (apart from Maps to), and the concept_id_2 of this relationship for this concept will be mapped to the value_as_concept_id in the according OMOP table.

For more example, in the related issue #619: concept Z82.4 in vocab ICD10 has

  • Maps to to the concept 4167217 --> observation_concept _id
  • Maps to value to the concept 134057 --> value_as_concept_id in the observation table
    - NOTE: in case of Measurement domain, the concept_id_2 in the relationship Maps to value also needs to be in the Meas Value domain.
    - UI will show both "Maps to" And "Maps to value", and then we need a way to distinguish these.

Image
Image

Acceptance Criteria

  • Initial idea: For concepts with domains observation and measurement, check if they have a Maps to value relationship; if yes, add one more mapping rule to value_as_concept_id in the according table.

Confirm creation

  • This issue is ready
@prquinlan
Copy link
Contributor

I think the same can be true for clinical additions too?

This one needs more discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: MoreInfo
Development

No branches or pull requests

2 participants