#473: PCORnet CDMv3 SAS prep-to-research Readiness
-------------------------+----------------------------
 Reporter:  bzschoche    |       Owner:  lv
     Type:  enhancement  |      Status:  assigned
 Priority:  major        |   Milestone:  data-domains3
Component:  data-stds    |  Resolution:
 Keywords:               |  Blocked By:  381, 486
 Blocking:               |
-------------------------+----------------------------
Changes (by dconnolly):

 * type:  task => enhancement


Old 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      ||06/15/16
> ||Indiana U Regenstrief ||03/01/16
> ||Marshfield Clinic     ||Completed DQ
> ||Med Coll Wisconsin    ||03/31/16
> ||U of Minnesota AHC    ||03/31/16
> ||U of Missouri HC      ||06/30/16
> ||U of Nebraska         ||3/15/16
> ||University of Iowa    ||TBD
> ||University of Kansas  ||~~DQ sent 2/2/16~~ March 16
> ||UT San Antonio        ||03/16/16
> ||UT SW Med Ctr         ||DQ sent 2/2/16
> ||UW Madison            ||03/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:

 prep-to-research readiness is evaluated in two steps:
   1. Diagnostic Query
      - official distribution is via popmednet
      - [https://github.com/PCORnet-DRN-OC/PCORnet-Diagnostic-Query
 PCORnet-DRN-OC/PCORnet-Diagnostic-Query] SAS code is available on github
      - results are due back to DRN-OC March 25th (see comment:24 for
 timeline details)
   2. Data Characterization
      - official distribution is via popmednet
      - [https://github.com/PCORnet-DRN-OC/PCORnet-Data-Characterization
 PCORnet-DRN-OC/PCORnet-Data-Characterization] SAS code is available on
 github
      - results are due back to the DRN-OC April 8th (comment:24)

 Diagnostic Query (DQ) requirements:

  - CDM v3.0 with SAS data types
  - All 15 tables present
  - Demographic, Enrollment, Encounter, Diagnosis, Procedures, Vital, and
 Harvest tables populated

 Data Characterization requirements:
  - Successful diagnostic response, i.e. 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 the [https://pcornet.imeetcentral.com/drnoc-
 workgroups/doc/42875655/w-DataCharacterization Data Characterization
 wiki])


 The DRN shares schedule and tracking info via imeetcentral:
  - [https://pcornet.imeetcentral.com/drnoc-workgroups/file/43823210/
 Timeline Phase II Diagnostic and Data Characterization Queries.xlsx]
  - [https://pcornet.imeetcentral.com/drnoc-workgroups/file/43982772/ phase
 II high-level tracking.xlsx]

 Research readiness (as opposed to prep-to-research readiness) should
 follow in one or more separate tickets. One reference on the whole process
 is a 5 Oct 2015 DRN OC presentation (ticket:266#comment:10); the Data
 Characterization wiki may have more up-to-date materials.

--

Comment:

 replacing out-of-date schedule in ticket description with pointer(s) to
 definitive info.

--
Ticket URL: 
<http://informatics.gpcnetwork.org/trac/Project/ticket/473#comment:32>
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

Reply via email to