My mistake. We just submitted the DCQ, which requires the annotated data dictionary.
Justin On Thu, Apr 28, 2016 at 12:26 PM, Verhagen, Laurel A < verhagen.lau...@mcrf.mfldclin.edu> wrote: > Justin, > > The Diagnostic Query (DQ) shouldn't require the Annotated Data > Dictionary... just the Data Characterization Query. Did James indicate > otherwise? > > Thanks, > Laurel > > -----Original Message----- > From: GPC Informatics [mailto:d...@madmode.com] > Sent: Thursday, April 28, 2016 12:22 PM > To: bzscho...@kumc.edu; Verhagen, Laurel A; jd...@umn.edu; > dconno...@kumc.edu; b...@uthscsa.edu; ngra...@kumc.edu; mprit...@kumc.edu; > nate.apa...@cerner.com; mo...@health.missouri.edu; campb...@unmc.edu; > kwa...@uwhealth.org; ashok.mudgapa...@unmc.edu; jmcc...@unmc.edu; > m...@wisc.edu; jay.peder...@unmc.edu > Cc: gpc-dev@listserv.kumc.edu; darcy.lou...@duke.edu > Subject: Re: [gpc-informatics] #473: PCORnet CDMv3 SAS prep-to-research > Readiness > > #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: | > -------------------------+---------------------------- > > Comment (by jdale): > > UMN submitted the DQ results today (4/28/16) minus the ETL annotated > data dictionary. In all the chaos of trying to get the query to run we > overlooked it. We verified with James Topping from Duke it was ok to > submit the results right now and the ETL document when complete. > > Our previous issues were definitely related to writing the SAS temp > files to network storage vs local. We increased the size of the local > disk to accommodate the large SAS temp files and that made all the > difference. > > -- > Ticket URL: < > https://urldefense.proofpoint.com/v2/url?u=http-3A__informatics.gpcnetwork.org_trac_Project_ticket_473-23comment-3A55&d=BQICaQ&c=KNVzINr6WAqWApikNSnyDeOu0ck0iFwcrMz92MxUhIs&r=A2PXk2ZGVGBzoEOQMwrrbqse0CnDMUgS4P3-3HOTSAwE8Vfvoc1Wm0NCYFbuU-_5&m=0kO7xHBpQhRLAiWz9dsSQ3ypUjJXaihjed7X3XahWYA&s=Oze0gEDZPiTyLhGMxLzL9Si0_Z0HdI95qyeaZzWovN0&e= > > gpc-informatics < > https://urldefense.proofpoint.com/v2/url?u=http-3A__informatics.gpcnetwork.org_&d=BQICaQ&c=KNVzINr6WAqWApikNSnyDeOu0ck0iFwcrMz92MxUhIs&r=A2PXk2ZGVGBzoEOQMwrrbqse0CnDMUgS4P3-3HOTSAwE8Vfvoc1Wm0NCYFbuU-_5&m=0kO7xHBpQhRLAiWz9dsSQ3ypUjJXaihjed7X3XahWYA&s=9Lon3fWbAi1nkYOw0iBP98r6jvRhcli72ak9KmLKp2Q&e= > > Greater Plains Network - Informatics > > ______________________________________________________________________ > The contents of this message may contain private, protected and/or > privileged information. If you received this message in error, you should > destroy the e-mail message and any attachments or copies, and you are > prohibited from retaining, distributing, disclosing or using any > information contained within. Please contact the sender and advise of the > erroneous delivery by return e-mail or telephone. Thank you for your > cooperation. > _______________________________________________ > Gpc-dev mailing list > Gpc-dev@listserv.kumc.edu > http://listserv.kumc.edu/mailman/listinfo/gpc-dev >
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
