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

Should the OMOP visit_start_date be defaulted if it is absent in the source CDM? #53

Open
cyaghmour opened this issue Jun 25, 2020 · 2 comments
Open

Should the OMOP visit_start_date be defaulted if it is absent in the source CDM? #53

cyaghmour opened this issue Jun 25, 2020 · 2 comments
Labels
Map Validation Issues deferred after Mapping Validation process requiring follow-up / refinement

Comments

@cyaghmour
Copy link
Collaborator

If the source CDM does not provide visit/encounter start date, should the mandatory OMOP field visit_start_date be set to a default value? If so, what value?
Or, should the visit/encounter record from the source be ignored?
@cyaghmour cyaghmour added the Map Validation Issues deferred after Mapping Validation process requiring follow-up / refinement label Jun 25, 2020
@shastak
Copy link
Collaborator

shastak commented Jun 25, 2020

For TriNetX and ACT this issue was resolved based on the CDM SME input. N3C will ignore the record when visit/encounter start date is missing in the TriNetX and ACT.

@kmkostka
Copy link
Contributor

I would adopt this convention for PCORNet too. It will set off a Data Quality flag if you have visits that are not valid dates.

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
3 participants
@cyaghmour @shastak @kmkostka