Thanks for being patient!

For now I am emailing the notes while I keep trying to move them to Google docs 
(while maintaining the formatting).


1.       Convene, take roll, review records and plan next meeting

a.       Meeting ID and access code: 817-393-381; call +1 (571) 317-3131

b.      roll: all 10(12) DevTeams represented? KUMC*, CMH*, UIOWA*, WISC, MCW*, 
MCRF*, UMN*, UNMC*, UTHSCSA, UTSW*, (MU), (IU)

c.       today's scribe: Given the light agenda, Bhargav to try covering the 
scribe responsibilities as well.

d.      Next Meeting June 30?; scribe volunteer - Laurel, from MCRF has kindly 
volunteered.

                                                               i.      What 
cool stuff is going on at your site that you'd like a little time to present? 
(Alex - has databuilder post-processing script ready to present?) - Next week's 
chair could follow-up with Alex.

2.       milestone:survey-redcap-als

a.       REDCap configuration details: Bhargav to demo the process if need be.

                                                               i.      Ref: How 
to set up GPC ALS REDCap 
Survey.<https://informatics.gpcnetwork.org/trac/Project/ticket/208#comment:5>

                                                             ii.      Details 
on how to verify configuration: From: Bhargav Adagarla  Sent: Tuesday, June 16, 
2015 5:44 PM To: '[email protected]' Subject: Setting up your site 
level REDCap project for GPC ALS survey

                                                            iii.      If you 
send the correct screenshots before the meeting tomorrow, please feel free to 
skip the meeting.

                                                           iv.      For 
completion, please be ready to share your screen after you have logged into 
your institutional REDCap.

                                                             v.      (Mark) 
MCW: We plan to print the patient specific survey links and study id on the 
each page of the survey using mail merge.

1.       (Bhargav) KUMC: This might be best as we have had users tear out the 
survey identifiers making the response un-linkable. We are not printing the 
study id on the survey as the users as the survey link will suffice to identify 
the patients.

                                                           vi.      (Teresa) 
UTSW:  We are doing it using email and we have over 36 responses already. For 
clinical validation we made sure the clinician understood which fields to edit 
and it was simple.

                                                          vii.      (Supreet) 
UMN: Do we need to get study ids or survey links from KUMC?

1.       (Bhargav) KUMC: No. The process is set up so you do not have to get 
the study ids or links from us. You will manage them both in your REDCap 
project.

b.      Heard back with screenshots from: UTHSCSA (Sergio Duncan), KUMC 
(self-certified), UTSW (Teresa, already collecting responses), MCRF (Laurel), 
WISC (Lisa)

c.       Pending:

UIOWA (Prakash, already set up. To send screenshots)

MCW (Mark, next week)

UMN (Supreet, to send screen shots by next week)

UNMC (Busy with breast cancer. But will send screenshots once they have set up 
the project)

3.       milestone:data-sec-check (Due in 7 days)

a.       #80 assessment of GPC vs. data privacy and security standards - 
responses to 
survey<https://redcap.gpcnetwork.org/redcap_v6.2.2/DataExport/index.php?pid=24&report_id=11>,
 missing CMH

                                                               i.      Rita has 
sent that to compliance. Will follow-up today.

Attendees:
[cid:[email protected]]


Regards,
Adagarla, Bhargav Srinivas

_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to