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.

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

Map OMOP data to inpatient_episodes table #28

Open
razekmh opened this issue Sep 26, 2024 · 1 comment
Open

Map OMOP data to inpatient_episodes table #28

razekmh opened this issue Sep 26, 2024 · 1 comment
Assignees
Labels
design Design, scoping and ToR work

Comments

@razekmh
Copy link

razekmh commented Sep 26, 2024

Extract data from the example OMOP data to fill the inpatient_episodes table from the validate article. This is a split from #17

Please feel free to assign yourself to the issue. Please the respective branch for development.

@razekmh razekmh added the design Design, scoping and ToR work label Sep 26, 2024
@AngharadGreen AngharadGreen self-assigned this Oct 2, 2024
@AngharadGreen
Copy link

AngharadGreen commented Oct 4, 2024

  • For this issue I have used the updated OMOK v0.3.0 to generate OMOP mockVisitOccurrence and mockProcedureOccurrence tables as these tables can be mapped to the RAMSES inpatient_episodes table.
  • For the RAMSES inpatient_episodes table the variables admission_method, last_episode_in_encounter, consultant_code and main_specialty_code are difficult to map to the OMOP CDM - I am looking into this in more detail to determine what OMOP tables would be appropriate to map to, as these variables must not contain missing data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Design, scoping and ToR work
Projects
None yet
Development

No branches or pull requests

2 participants