OHDSI / OHDSI/CommonDataModel

CDM Source

Open
#674 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

General Convention
Dominant language
HTML
Stars
1.1k
Forks
508
Avg merge
1h 30m
Merged PRs (30d)
3

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue's description of the CDM_SOURCE table and review the linked CDM_SOURCE documentation. Compare the stated multi-feed convention with the current documentation and ETL specifications; done means the convention and any limitation on linking CDM records to source records are documented clearly.

Written by the indexing model from the issue text.

Assessment

Domain
databases, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.