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.

Sign up for GitHub

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

Jump to bottom

Preserving / aggregating raw and source data not mapped into single OMOP field #28

Open
DaveraGabriel opened this issue Jun 10, 2020 · 0 comments
Open

Preserving / aggregating raw and source data not mapped into single OMOP field #28

DaveraGabriel opened this issue Jun 10, 2020 · 0 comments
Labels
Map Validation Issues deferred after Mapping Validation process requiring follow-up / refinement

Comments

@DaveraGabriel
Copy link
Collaborator

Source data that are mapped into OMOP 5.3.1 can be preserved by aggregating into a single OMOP field. These source data should be delimited and can be identified with tags. Children's Hospital of Colorado created and stored JSON objects for this purpose. Another approach is to cerate an OMOP extension to store this data. Of issue: what is the best approach to aggregation and preservation of raw and source data on N3C OMOP instance?
@DaveraGabriel DaveraGabriel added the Map Validation Issues deferred after Mapping Validation process requiring follow-up / refinement label Jun 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Map Validation Issues deferred after Mapping Validation process requiring follow-up / refinement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DaveraGabriel