-
Notifications
You must be signed in to change notification settings - Fork 0
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
Project Meeting -- 07/29/2019 @ 15:00 #109
Comments
UPDATE: Thanks for being willing to take a look at these (listed in order from most to least confident):
For each query, would you mind taking a look at each logical statement and it’s corresponding code chunk (example shown below) just to make sure that I have properly covered it and didn’t do something silly? Logical Statement: age_criteria_1: Patient is 1460 days or older (age at earliest diagnosis of ADHD) age_criteria_1 AS (
SELECT co.person_id, cohort.standard_code_set AS code_set
FROM
{database}.person p,
{database}.condition_occurrence co,
{database}.ADHD_COHORT_VARS cohort
WHERE p.person_id = co.person_id
AND co.condition_concept_id = CAST(cohort.standard_concept_id AS int64)
AND cohort.phenotype_definition_number = 1
AND cohort.standard_code_set = {code_set_group}
GROUP BY
co.person_id, p.birth_datetime, cohort.standard_code_set
HAVING
DATETIME_DIFF(DATETIME(MIN(co.condition_start_datetime)), DATETIME(p.birth_datetime), DAY) >= 1460
) database and code_set_group are looped over when running the code from python. code_set_group is for each of the mapping strategies we are evaluating. The phenotype_definition_number is a number I have linked to all of the “ADHD codes”, this approached is utilized to help me keep track of all of the different codes. To help keep track of the different code chunks and how they are combined, I have added a logic table for each cohort, their “chunks” and how those should be combined. For example, here is the table for ADHD:
Closing this issue. Please re-open if there is anything that needs clarification. |
Meeting Date: 07/29/2019
Topic: Biweekly Meeting
Attendees: @mgkahn
Proposed Agenda:
The text was updated successfully, but these errors were encountered: