#473: PCORnet CDMv3 SAS Readiness -----------------------+---------------------------- Reporter: lv | Owner: lv Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h1 Component: data-stds | Resolution: Keywords: | Blocked By: Blocking: | -----------------------+---------------------------- Changes (by dconnolly):
* cc: darcy.louzao@… (added) Old description: > Specifically, can you verify/update the date at which each data partner > will be ready to receive the Diagnostic Query (DQ), for which the > requirements are: > > • CDM v3.0 with SAS data types > • All 15 tables present > • Demographic, Enrollment, Encounter, Diagnosis, Procedures, Vital, and > Harvest tables populated > > ||Site ||SAS CDM v3 Readiness Date/DQ Status > ||Children's Mercy ||TBD > ||Indiana U Regenstrief ||3/1/16 > ||Marshfield Clinic ||Completed DQ > ||Med Coll Wisconsin ||3/31/16 > ||U of Minnesota AHC ||3/31/16 > ||U of Missouri HC ||6/30/16 > ||U of Nebraska ||3/15/16 > ||University of Iowa ||TBD > ||University of Kansas ||DQ sent 2/2/16 > ||UT San Antonio ||DQ sent 2/2/16 > ||UT SW Med Ctr ||DQ sent 2/2/16 > ||UW Madison ||3/14/16 > > > Additionally, please keep the following points in mind for future > planning: > 1. We will send the Diagnostic Query based on the dates you provide (I > will check-in the week prior to sending to verify readiness) > 2. We will request a response in ~2 weeks > 3. Requirements for the next step, Data Characterization, are: > • Successful diagnostic response, ie. no exceptions noted (in the > workplan they are described as “unexpected conditions”) > • Locked/static data > • Will need to submit an ETL ADD with their query response (the template > is on our Data Characterization wiki) New description: ''Laurel reporting on behalf of Darcy Louzao:'' Specifically, can you verify/update the date at which each data partner will be ready to receive the Diagnostic Query (DQ), for which the requirements are: • CDM v3.0 with SAS data types • All 15 tables present • Demographic, Enrollment, Encounter, Diagnosis, Procedures, Vital, and Harvest tables populated ||Site ||SAS CDM v3 Readiness Date/DQ Status ||Children's Mercy ||TBD ||Indiana U Regenstrief ||3/1/16 ||Marshfield Clinic ||Completed DQ ||Med Coll Wisconsin ||3/31/16 ||U of Minnesota AHC ||3/31/16 ||U of Missouri HC ||6/30/16 ||U of Nebraska ||3/15/16 ||University of Iowa ||TBD ||University of Kansas ||DQ sent 2/2/16 ||UT San Antonio ||DQ sent 2/2/16 ||UT SW Med Ctr ||DQ sent 2/2/16 ||UW Madison ||3/14/16 Additionally, please keep the following points in mind for future planning: 1. We will send the Diagnostic Query based on the dates you provide (I will check-in the week prior to sending to verify readiness) 2. We will request a response in ~2 weeks 3. Requirements for the next step, Data Characterization, are: • Successful diagnostic response, ie. no exceptions noted (in the workplan they are described as “unexpected conditions”) • Locked/static data • Will need to submit an ETL ADD with their query response (the template is on our Data Characterization wiki) -- Comment: attribute ticket description to Louzao 5 Feb and add to cc. -- Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/473#comment:5> gpc-informatics <http://informatics.gpcnetwork.org/> Greater Plains Network - Informatics _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev