Wow.. the mailing list widget really doesn't like you, does it, Steffani? Hm... it looks like you sent to gpc-dev-boun...@listserv.kumc.edu ; the normal place to send is gpc-dev@listserv.kumc.edu .
Anyway... thanks for getting this info! -- Dan ________________________________ From: Roush, Steffani <roush.steff...@marshfieldresearch.org> Sent: Tuesday, November 17, 2020 11:29 AM To: gpc-dev-boun...@listserv.kumc.edu <gpc-dev-boun...@listserv.kumc.edu> Subject: GPC Network Progress Report Feedback and Questions Hi Everyone, Here are our questions/concerns regarding the network progress report and DRNOC's responses: Concerns with how metrics are calculated: * Shut downs in health systems due to COVID-19 affected data latency/patient counts in the March-April timeframe. Is this still being counted against sites? If not, can DRNOC address this concern? o DRNOC: We understand and see that pattern at many sites. We provided PCORI that context to keep in mind as they review the data. * Query responsiveness metrics are being calculated based on the date the query was approved vs. when the query was returned. Does it still count against sites if they return a query on time but it is not reviewed/approved by DRNOC until after the due date? What about instances where the queries were returned on time, but there was an issue identified (error in log or wrong attachment sent)? Sites do not feel this should be counted against them. o DRNOC: Metrics on if a data curation submission was "on time" is from when an "approvable" package was submitted, not when it was approved. So if a site submits their response on the due date, and there are no issues, they are counted as on time even if the approval email does not go out for a few days. However, if the site responds on the due date with issues that must be remediated, they are considered late until the respond with a package that has no issues. o SLR: Requesting clarification on this line from item above: However, if the site responds on the due date with issues that must be remediated, they are considered late until the respond with a package that has no issues. Does this mean that if a site turns around revised query responses after the due date, their response is not counted as late? o DRNOC: Query response metrics are based on when the site responds. * PRO CM Table not populated - Additional guidance on this table would be appreciated. Without studies that explicitly use this table it is hard to justify populating for some sites. Populating this table requires months of work for data that is not otherwise leveraged. o DRNOC: PCORI requested feedback on the population of all tables and we provided them context as to why certain tables may be less prioritized by sites to participate. * Obs Gen and Obs Clin Tables not populated - comments similar to the statement above. Dev team acknowledges that obs clin will be populated from here on out due to the deprecation of the vitals table. o See above General Comments * Responsiveness to PopMedNet queries: It would be helpful if naming conventions between this report and what is seen in the Datamart Client were consistent. It is hard to match up what is represented here to what was submitted otherwise. o DRNOC: Noted * Network Studies: it would be helpful to have PI listed. It is hard to keep track of which study is which in this report. One example is the BP Control study listed on page 7. There are multiple BP studies going on in the network at the same time and it's hard to differentiate in this report. o DRNOC: This section is being updated and will have all 3 Aims of BP control in next report. * General comment: A dashboard that is updated regularly (weekly?) with this information would be helpful. Sites would like to see how they are scoring during the reporting period so that issues can be addressed if needed. o DRNOC: Please see iMeet for QI reports that are updated ~monthly and as needed o Link: https://pcornet.imeetcentral.com/pcornetbenchmarks/doc/WzIsNDg1Mzc5NjVd/ o Additional Info: Query metrics that are found on iMeet are based on site responding by the due date with data in final report. So both criteria need to be met, which doesn't fully align with Progress Report Metrics. Steffani Roush Research Programmer Analyst Senior | Office of Research Computing and Analytics Marshfield Clinic Research Institute Office: 715-221-6442 | Ext: 1-6442 ______________________________________________________________________ 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
