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

CDM Source #674

Open
MaximMoinat opened this issue Apr 19, 2024 · 4 comments
Open

CDM Source #674

MaximMoinat opened this issue Apr 19, 2024 · 4 comments

Comments

@MaximMoinat
Copy link
Collaborator

How to populate the cdm_source table if the data is derived from multiple data feeds.

CDM or THEMIS convention?

CDM

Table or Field level?

Table

Is this a general convention?

Yes

Summary of issues

Populating cdm_source if the data is derived from multiple data feeds.

Summary of answer

If a source database is derived from multiple data feeds, the integration of those disparate sources is expected to be documented in the ETL specifications. The source information on each of the databases can be represented as separate records in the CDM_SOURCE table. Currently, there is no mechanism to link individual records in the CDM tables to their source record in the CDM_SOURCE table.

Related links

https://www.ohdsi.org/web/wiki/doku.php?id=documentation:cdm:cdm_source

Other comments/notes

NA

@clairblacketer
Copy link
Contributor

@MaximMoinat I would like to discuss this at an upcoming CDM WG meeting. If I am not mistaken, many of our tools expect only one record in the CDM Source table (like ARES Indexer) so I want to make sure we are clear on what the software is doing before we declare this.

@MelaniePhilofsky
Copy link
Collaborator

@clairblacketer and @MaximMoinat

At the University of Colorado, we insert one record per data source into the CDM_Source table. Each of these data sources have different source release dates. And I know other health systems combine records from different sources.

Let's discuss further in the CDM WG and then make sure we give guidance via CDM requirements and Themis conventions.

@clairblacketer
Copy link
Contributor

clairblacketer commented Apr 29, 2024

@MelaniePhilofsky agreed. The convention makes sense, I just want to make sure we are aligned across the community

@MaximMoinat
Copy link
Collaborator Author

MaximMoinat commented Apr 29, 2024

@MelaniePhilofsky Interesting, I did not realise this use case for cdm_source. But makes sense, to capture all sources in cdm_source. And although trivial, it is important to define this explicitly because tooling might misbehave otherwise.

Let's discuss in a meeting. I was set on the convention of having only one record in cdm_source, but maybe the tooling should allow this after all.

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

No branches or pull requests

3 participants