1 / 16

Next-D Variable Extraction

This project involves extracting diabetes-related data using t-SQL extraction codes for translation in diabetes research. The Timeline includes date manipulation and un-shifting strategies for accurate data reporting. Relevant tables for extraction include Demographic, Encounter, Socio-Economics Status, Vital Signs, Diagnoses, Procedures, Death Cause, Prescription Medicines, Dispensed Medicines, Labs, and Health Outcome.

kjon
Download Presentation

Next-D Variable Extraction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Next-D Variable Extraction Natural experiments for translation in diabetes

  2. NextD Project Overview • Milestone: https://informatics.gpcnetwork.org/trac/Project/milestone/next-d • Table1: https://informatics.gpcnetwork.org/trac/Project/ticket/545 • Github Support site: https://github.com/kumc-bmi/nextd-study-support • t-SQL extraction codes for table 2-11 by Alona: https://www.dropbox.com/home/diabetes%20project%20(working%20docs)/NU_data%26codes/Codes (the codes include all appropriate filters whenever those are needed. If don’t have access to the dropbox, please contact Charon Gladfelter [charon.gladfelter@northwestern.edu]‎ )

  3. Extraction Plan • Timeline (tentative)

  4. Date Manipulation • Date unshifting* • NextD requires the Actual Dates • Dates un-shift strategy: • days_shift = real_birth_date – CDM_birth_date • XXXX_Date = XXXX_CDM_date + days_shift • Date blinding* (when reporting): always convert XXXX_Date to • XXXX_YEAR • XXXX_MONTH • XXXX_Days_from_FirstEncounter *should be applied for each table whenever it comes to Date variable

  5. Table 2 - Demographic • At patient level

  6. Table 3 - Encounter • All Encounters (not restricted to IP,ED,IS,OS,AV) • For NextD cohort defined in Table1 • With age at visit between 18 and 89 years old • Within study period (after 01-01-2010) • Include pregnancy encounters

  7. Table 11 - Socio-Economics Status (SES) • At patient level https://informatics.gpcnetwork.org/trac/Project/ticket/544 *https://github.com/bconnolly/nextd-study-support/blob/master/clinical_data_collection/LinkEHRAndGeocodedData.sql

  8. Table 5 - Vital Signs • All Eligible Encounters in Table 3 (exclude pregnancy encounters)

  9. Table 7 - Diagnoses • All Eligible Encounters in Table 3 (exclude pregnancy encounters)

  10. Table 8 - Procedures • All Eligible Encounters in Table 3 (Include pregnancy encounters)

  11. Table 9 – Death Cause • At patient level Optional for delivery Alona:”sites having not DEATH_CAUSE tables must not report them. Death date is in Table1. So, no worries about it as long as site report table 1 to us.”

  12. Table 4a - Prescription Medicines • All Eligible Encounters in Table 3 (exclude pregnancy encounters) Confirmed with Alona

  13. Table 4b - Dispensed Medicines • All Eligible Encounters in Table 3 (exclude pregnancy encounters) Confirmed with Alona

  14. All Eligible Encounters in Table 3 (exclude pregnancy encounters) Table 6 - Labs

  15. Table 10 – Health Outcome Remark: We are only asking for these measures from sites that are already calculating them (Definition Appendix C)

  16. Table 10 – Health Outcome (con’t)

More Related