I made a few clarifications and added in updates. Attached and linked: 
https://docs.google.com/document/d/1TeyNvy1Nj-4U5pOKye8jndRAAB2Xs9eDIsuFBxdMeuU/edit?pli=1

Thanks, Susan!

Laurel

From: gpc-dev-boun...@listserv.kumc.edu 
[mailto:gpc-dev-boun...@listserv.kumc.edu] On Behalf Of Susan Morrison
Sent: Wednesday, December 10, 2014 11:26 AM
To: Dan Connolly; gpc-dev@listserv.kumc.edu
Subject: Re: GPC Meeting Notes for December 9th

Thanks.  I appreciate it!

Sincere Regards,
Susan Morrison
Database Analyst
Office of Academic Information Systems (AIS)
UT Southwestern Medical Center
6303 Forest Park.| Suite BP4.100 | Dallas, TX  75390-9106
214-648-4293
susan.morri...@utsouthwestern.edu<mailto:teresa.bos...@utsouthwestern.edu>



From: Dan Connolly <dconno...@kumc.edu<mailto:dconno...@kumc.edu>>
Date: Wednesday, December 10, 2014 at 11:08 AM
To: Susan <srdmorri...@gmail.com<mailto:srdmorri...@gmail.com>>, 
"gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>" 
<gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>>
Subject: RE: GPC Meeting Notes for December 9th

Thanks for taking notes, Susan.

Minute guidelines are in 
#12<https://informatics.gpcnetwork.org/trac/Project/ticket/12>:

Google docs seems to work well...

  *   copy the agenda into a google doc
  *   authorize the chair to edit it
  *   authorize everybody else to read it
  *   the chair can screen-share it during the meeting as notes are taken

     *   while other things are being screen-shared, participants can still 
look at the notes

  *   clean it up a bit after the meeting
  *   send a full-text copy to the mailing list
I hope to refine that a bit...

While the scribe should make an effort to take notes, don't sweat it too much 
if you miss something. The chair is responsible to check that essential things 
get recorded. Google docs lets us do this in real time. The meeting 
participants can help too (lately, we let everybody edit, not just read).

--
Dan



________________________________
From: 
gpc-dev-boun...@listserv.kumc.edu<mailto:gpc-dev-boun...@listserv.kumc.edu> 
[gpc-dev-boun...@listserv.kumc.edu<mailto:gpc-dev-boun...@listserv.kumc.edu>] 
on behalf of Susan Morrison (via Google Docs) 
[srdmorri...@gmail.com<mailto:srdmorri...@gmail.com>]
Sent: Wednesday, December 10, 2014 10:17 AM
To: gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>
Subject: GPC Meeting Notes for December 9th
Susan Morrison<mailto:srdmorri...@gmail.com> has attached the following 
document:
[Image removed by sender. Document]
GPC Meeting Notes for December 9th
[Image removed by sender.]The minutes are attached. I am just finding that the 
protocol was to share the minutes as I entered them though the document was 
shared. I noted it being done previous minutes but did not know it was 
standard. Most of the staff here is out this week or working from offsite. 
Please make any modifications as needed. Do we have the minute guidelines 
posted anywhere?

Best Regards,
Susan Morrison
Database Analyst
UT Southwestern Medical Center
214-648-4293
susan.morri...@utsouthwestern.edu<mailto:susan.morri...@utsouthwestern.edu>









Google Docs: Create and edit documents online.

[Image removed by sender. Logo for Google Docs]<https://drive.google.com>


________________________________

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.

Attachment: GPCMeetingNotesforDecember9th.pdf
Description: GPCMeetingNotesforDecember9th.pdf

_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to