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

TriNetX Vital Status / Death Date mapping ignored #51

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

TriNetX Vital Status / Death Date mapping ignored #51

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

Comments

@DaveraGabriel
Copy link
Collaborator

Mapping validation session / review determined that Vital Status would be ignored. Matvey Paluchuk stated he believed this field would be very sparsely populated in most cases. Subsequent mapping validation session (for ACT) regarding vital status data determined that this decision should be revisited for TriNetX.

OMOP has 2 fields to capture death date. Depending on the data, may need to parse into following fields:
Death.death_date
Death.death_datetime
If death_Date is NULL in, we cannot create a OMOP record in death table. SEE Vital_Status comment.

@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
Labels
Map Validation Issues deferred after Mapping Validation process requiring follow-up / refinement TriNetX CDM
Projects
None yet
Development

No branches or pull requests

1 participant