This is day 3 of it running here at UMN with no signs of stopping yet. I'm
hoping it will be done by COB, but only time will tell.

On Thu, Nov 2, 2017 at 9:01 AM, Verhagen, Laurel A <
verhagen.lau...@marshfieldresearch.org> wrote:

> This was one of the longest running for Marshfield as well.
>
>
>
> Thanks,
>
> Laurel
>
>
>
> *From:* Gpc-dev [mailto:gpc-dev-boun...@listserv.kumc.edu] *On Behalf Of 
> *Debbie
> Yoshihara
> *Sent:* Thursday, November 02, 2017 8:47 AM
> *To:* Phillip Reeder; Hillary Sandoval; 'Brittany Zschoche';
> gpc-dev@listserv.kumc.edu
>
> *Subject:* Re: [PCORnet CDRN PMs] Fwd: PCORnet Front Door HFpEF (FD0053)
> PMP2 Request Distribution
>
>
>
> Hi Phillip,
>
>
>
> Yeah, just for reference, we run SAS against our Netezza files.
>
> It took 21 hours clock time.
>
> Since we have a hard reboot every 24 hours, this query
>
> just made it.  And I agree, it's one of the longest running
>
> queries.
>
>
>
> --- Debbie
>
>
>
>
>
> Debbie Yoshihara
>
> Informatics Specialist
>
> Biomedical Informatics Services - SMPH-IT
>
> Institute for Clinical and Translational Research (ICTR)
>
> School of Medicine and Public Health, UW-Madison
>
> matrixed employee of UW Health
>
>
> ------------------------------
>
> *From:* Gpc-dev <gpc-dev-boun...@listserv.kumc.edu> on behalf of Phillip
> Reeder <phillip.ree...@utsouthwestern.edu>
> *Sent:* Thursday, November 2, 2017 8:33:11 AM
> *To:* Hillary Sandoval; 'Brittany Zschoche'; gpc-dev@listserv.kumc.edu
> *Subject:* Re: [PCORnet CDRN PMs] Fwd: PCORnet Front Door HFpEF (FD0053)
> PMP2 Request Distribution
>
>
>
> For those who have successfully completed this query, how long did SAS
> take to complete?  Its been running for 24 hours here at UTSW and seems to
> be making progress so I don’t want to kill the process.  There were files
> created at 5:00AM and log entries at 8:30, so I know it’s still alive.  But
> this is by far the longest running SAS query I’ve run.
>
>
>
> Phillip
>
>
>
> *From: *Gpc-dev <gpc-dev-boun...@listserv.kumc.edu> on behalf of Hillary
> Sandoval <hsando...@kumc.edu>
> *Date: *Wednesday, November 1, 2017 at 9:36 AM
> *To: *'Brittany Zschoche' <gpc-site...@listserv.kumc.edu>, "
> gpc-dev@listserv.kumc.edu" <gpc-dev@listserv.kumc.edu>, "
> 'gpc...@listserv.kumc.edu'" <gpc...@listserv.kumc.edu>
> *Subject: *FW: [PCORnet CDRN PMs] Fwd: PCORnet Front Door HFpEF (FD0053)
> PMP2 Request Distribution
>
>
>
> Hello everyone,
>
>
>
> Just a reminder that if you received a request to complete query
> fd0053_pmp2_wp003 and have not responded yet, please respond by COB
> tomorrow. If you are unable to do this you can still respond up until
> 11/10, but your data will not be included in the report provided to the
> requestor.
>
>
>
> Please see below for details. From my records, I believe Marshfield, Iowa
> and MU have already completed this.
>
>
>
> Thank you,
> Hillary
>
>
>
> *From:* PCORnet DRN OC [mailto:dr...@pcornet.org <dr...@pcornet.org>]
> *Sent:* Wednesday, November 1, 2017 9:11 AM
> *To:* PCORnet Query Fulfillment <q...@pcornet.org>
> *Subject:* [PCORnet CDRN PMs] Fwd: PCORnet Front Door HFpEF (FD0053) PMP2
> Request Distribution
>
>
>
> Dear PCORnet colleagues,
>
> As a reminder, we are requesting responses to the Front Door Heart Failure
> with Preserved Ejection Fraction (HFpEF) query (fd0053_pmp2_wp003) by *COB
> Tomorrow, November 2nd* in order to be included in the report. Sites that
> are unable to respond by November 2nd will still have until Friday,
> November 10th to respond to the query, however their data will not be
> included in the report that will be provided to the requester.
>
> Many thanks to the sites that have already submitted their responses.
>
> For general questions, please contact the DRN OC at dr...@pcornet.org.
>
> For questions specific to the query, please contact the Query Fulfillment
> team at q...@pcornet.org.
>
> Best wishes,
>
> The PCORnet DRNOC and Query Fulfillment Teams
>
>
>
> ---------- Forwarded message ----------
> From: *PCORnet DRN OC* <dr...@pcornet.org>
> Date: Fri, Oct 27, 2017 at 10:32 AM
> Subject: PCORnet Front Door HFpEF (FD0053) PMP2 Request Distribution
> To:
> Cc: PCORnet Query Fulfillment <q...@pcornet.org>
>
> Dear PCORnet colleagues,
>
>
>
> The Query Fulfillment team is pleased to announce the distribution of the 
> *Front
> Door Heart Failure with Preserved Ejection Fraction (HFpEF) (FD0053)*
> query request. For specific details about this request, please see the 
> *Request
> Details *section below.
>
>
>
> This query request will be distributed as a PCORnet Modular Program 2
> (PMP2) package on October 27, 2017. The full workplan and metadata are
> available here: https://pcornet.imeetcentral.com/p/ZgAAAAAAkfHa
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__pcornet.imeetcentral.com_p_ZgAAAAAAkfHa&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=XNXVzdAKFbVvmixJkc4Uon8-2xZmQNDn2dtO-RyxD38&m=AMnaUtz3GYBCuhcu_QS0jHQd2yGAht_8lBUvo-BSmH0&s=bLWe5Mgupljm-NKd1mPYdRXnGJNrtyFmNFamkpAym2s&e=>
>
>
>
> A response to this request will count as 17 queries.
>
>
>
> *Who is the requester?*
>
> Adam Devore, Duke University and AstraZeneca
>
>
>
> *How will the results be used?*
>
> AstraZeneca is considering the development of a Pragmatic Clinical Trial
> (PCT) among Heart Failure patients and is interested in the feasibility of
> using PCORnet for this future study. The results of this query will be
> provided to the requester at the PCORnet level (i.e. aggregated across all
> DataMarts). The number and names of responding DataMarts will be included
> in the report. If the requester develops future plans for a PCT and would
> like DataMart-level data to aid in site identification, the Coordinating
> Center will contact each DataMart for approval prior to sharing their data. 
> *DataMarts
> will have 10 business days to respond, but the Coordinating Center requests
> responses by November 2, 2017, as the report for this query will be
> generated at that time due to requester deadlines.*
>
>
>
> The Coordinating Center may reuse Network & CDRN-level aggregate data for
> internal planning & to inform potential funding/research opportunities.
>
>
>
> *Has this request gone through the Network collaboration Request process?*
>
> No (for more information on request designations see Front Door Queries
> document here
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__pcornet.imeetcentral.com_p_aQAAAAAC-2D20J&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=XNXVzdAKFbVvmixJkc4Uon8-2xZmQNDn2dtO-RyxD38&m=r776hHyivvC0iJAFp3PQL2YEGxlKzYB_pw0SSNXkAJ0&s=eFbDClza7wMB75ZGqEz7VSA6tcIZhcQ1neCyLCIWMEM&e=>
> )
>
>
>
> *Who is eligible to receive the query?*
>
> All DataMarts that have been approved on either Cycle 1, 2, or 3 of Data
> Curation (full tracker available here
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__pcornet.imeetcentral.com_p_aQAAAAAC5cuA&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=XNXVzdAKFbVvmixJkc4Uon8-2xZmQNDn2dtO-RyxD38&m=r776hHyivvC0iJAFp3PQL2YEGxlKzYB_pw0SSNXkAJ0&s=ldntwPI0bbgDxpLxswkFQsEgLD84nitJd-UM1qPkQhE&e=>)
> will receive the query for the opportunity to respond.
>
>
>
> *What is the timeframe?*
>
> Eligible DataMarts will receive the query on October 27, 2017 and
> responses will be due on November 10, 2017. *Please note that although
> DataMarts will have 10 business days to respond, the Coordinating Center
> urges Network Partners to respond by November 2, 2017, as the report for
> this query will be generated at that time due to requester deadlines.*
>
>
>
> *Query distribution*
>
> The query will be distributed to eligible DataMarts via the PopMedNet
> Query Tool. An email notification via the tool will be sent to the DataMart
> Administrator and any other users with enabled notifications when the query
> is distributed. Detailed instructions for query execution can be found in
> the workplan document here: https://pcornet.imeetcentral.com/p/
> ZgAAAAAAkfHa
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__pcornet.imeetcentral.com_p_ZgAAAAAAkfHa&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=XNXVzdAKFbVvmixJkc4Uon8-2xZmQNDn2dtO-RyxD38&m=AMnaUtz3GYBCuhcu_QS0jHQd2yGAht_8lBUvo-BSmH0&s=bLWe5Mgupljm-NKd1mPYdRXnGJNrtyFmNFamkpAym2s&e=>
>
>
>
> *Request Details*
>
> The Front Door HFpEF (FD0053) query request will examine counts of unique
> patients age 0-89+ with:
>
>    - *HF_ONLY:* A diagnosis code for heart failure with preserved
>    ejection fraction (HFpEF)
>    - A diagnosis code for HFpEF AND
>
>
>    - *HF_DIAB:* A diagnosis code of diabetes in the five years prior to
>       the index event, including same-day diagnoses
>       - *HF_HYP:* A diagnosis code of Hypertension in in the five years
>       prior to the index event, including same-day diagnoses
>       - *HF_MI:* A  diagnosis code of myocardial infarction in the 1825
>       days prior to the index event
>       - *HF_CABGPCI:* A diagnosis code of either coronary artery bypass
>       grafting OR percutaneous coronary intervention in the 1825 days prior to
>       the index event
>       - *HF_STRKTIA:* A diagnosis code of either stroke OR transient
>       ischemic attack in the 1825 days prior to the index event
>       - *HF_AFIB:* A diagnosis code of either atrial fibrillation OR
>       flutter in the five years prior to the index event, including same-day
>       diagnoses
>       - *HF_HF1IP:* A diagnosis code of heart failure with an encounter
>       type of IP in the 180 days prior to the index event
>       - *HF_HF1ED:* A diagnosis code of heart failure with an encounter
>       type of ED in the 180 days prior to the index event
>       - *HF_HF1EI:* A diagnosis code of heart failure with an encounter
>       type of EI in the 180 days prior to the index event
>       - *HF_HF1OS: *A diagnosis code of heart failure with an encounter
>       type of OS in the 180 days prior to the index event
>       - *HF_HF2IP:* A diagnosis code of heart failure with an encounter
>       type of IP in the 365 days prior to the index event
>       - *HF_HF2ED:* A diagnosis code of heart failure with an encounter
>       type of ED in the 365 days prior to the index event
>       - *HF_HF2EI:* A diagnosis code of heart failure with an encounter
>       type of EI in the 365 days prior to the index event
>       - *HF_HF2OS:* A diagnosis code of heart failure with an encounter
>       type of OS in the 365 days prior to the index event
>       - *HF_HF3IP:* A diagnosis code of heart failure with an encounter
>       type of IP in the 1825 days prior to the index event
>       - *HF_HF3ED:* A diagnosis code of heart failure with an encounter
>       type of ED in the 1825 days prior to the index event
>       - *HF_HF3EI:* A diagnosis code of heart failure with an encounter
>       type of EI in the 1825 days prior to the index event
>       - *HF_HF3OS:* A diagnosis code of heart failure with an encounter
>       type of OS in the 1825 days prior to the index event
>       - *HF_HF4IP:* A diagnosis code of heart failure with an encounter
>       type of IP in the 365 days after the index event
>       - *HF_HF4ED:* A diagnosis code of heart failure with an encounter
>       type of ED in the 365 days after the index event
>       - *HF_HF4EI:* A diagnosis code of heart failure with an encounter
>       type of EI in the 365 days after the index event
>       - *HF_HF4OS: *A diagnosis code of heart failure with an encounter
>       type of OS in the 365 days after the index event
>       - *HF_ACE:* An RxNorm_CUI code for ACE Inhibitors within the day
>       before or after the index event
>       - *HF_ARB:* An RxNorm_CUI code for Angiotensin Receptor Blockers
>       within the day before or after the index event
>       - *HF_SV: *An RxNorm_CUI code for Sacubitril-valsartan within the
>       day before or after the index event
>       - *HF_SPIRO:* An RxNorm_CUI code for spironolactone in within the
>       day before or after the index event
>       - *HF_BB:* An RxNorm_CUI code for beta blockers within the day
>       before or after the index event
>       - *HF_LOOP:* An RxNorm_CUI code for loop diuretics within the day
>       before or after the index event
>       - *HF_DIGO:* An RxNorm_CUI code for digoxin within the day before
>       or after the index event
>       - *HF_INS:* An RxNorm_CUI code for insulin within the day before or
>       after the index event
>       - *HF_SGLT:* An RxNorm_CUI code for SGLT2 inhibitors within the day
>       before or after the index event
>
> All codes for this request were defined by the Front Door team in
> collaboration with the PI. The query period for this request is
> 1/1/2014-12/31/2016. All counts will be stratified by age, sex, race, and
> Hispanic.
>
>
>
> For general questions, please contact the DRN OC at dr...@pcornet.org.
>
>
>
> For questions specific to the query, please contact the Query Fulfillment
> team at q...@pcornet.org.
>
>
>
> Best wishes,
>
>
>
> The PCORnet DRN OC and Query Fulfillment teams
>
>
>
> --------------------------------------------------------------------------
>
> Query Fulfillment for the PCORnet Distributed Research Network Operations
> Center
>
> QF Email: q...@pcornet.org
>
> QF Wiki: https://pcornet.imeetcentral.com/p/aQAAAAAClFkW
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__pcornet.imeetcentral.com_p_aQAAAAAClFkW&d=DwMF-g&c=KNVzINr6WAqWApikNSnyDeOu0ck0iFwcrMz92MxUhIs&r=A2PXk2ZGVGBzoEOQMwrrboZc0kb2NWGliRjTa4b3xxXo7HiAVoZaxWlIgfPM_ia9&m=KtxOjIES0qtVE7j-1oNWKkz8VYo0eCdYYe8aKaVM6ng&s=WKPflD5AGtz3ZC7ybBA4Kq0tBYHd48Zkgmmi_wOf_rQ&e=>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "PM_CDRN" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pm_cdrn+unsubscr...@pcornet.org.
>
>
> ------------------------------
>
> *UT** Southwestern*
>
> Medical Center
>
> The future of medicine, today.
>
>
> ------------------------------
> 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
>
>


-- 
Andrew Hangsleben
Developer/Analyst
Academic Health Center - Information Systems
<http://hub.ahc.umn.edu/ahc-information-systems>
University of Minnesota
Phone: (612) 625-1285
Email: hangs...@umn.edu
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to