Dan, thank you for the notes. Sorry, we have a recurring bi-weekly Wed 9am meeting. We should be on the call next week.
- Glenn Medical Informatics Senior Analyst CTSI – Clinical & Translational Science Institute [email protected] (414) 805-7239 From: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Reply-To: Greater Plains Collaborative Software Development <[email protected]<mailto:[email protected]>> Date: Wednesday, January 15, 2014 at 11:19 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Notes for review RE: GPC dev, stds teleconference Weds Jan 15 9am (also available as ticket:12#comment:1<http://informatics.gpcnetwork.org/trac/Project/ticket/12#comment:1>, as something of an experiment, since trac wiki syntax is a convenient way to edit hypertext) 1. Convene, take roll, review agenda * agenda<http://www.mail-archive.com/[email protected]/msg00005.html> from Dan Connolly Tue, 14 Jan 2014 08:35:47 -0800 Present: * @KUMC.EDU * Dan Connolly, GPC Software Lead (DC) * agenda + future telconference time(s) * @UNMC.EDU * Jim Campbell (JC) * agenda + meeting w/Epic Liaison Jan 21st * Hubert Hickman * @UTSOUTHWESTERN.EDU * Phillip Reeder * Lindsay Cowell or was it Wendy something?, site PI. WG member for stds * @MCRF.MFLDCLIN.EDU * Laurel Verhagen, project coordination for tech dev team * @wisc.edu / @UWHEALTH.ORG * Tom Mish, project manager * Nathan Wilson, ontologist * Keith Wanta, lead technical engineer * Deborah Yoshihara, lead query person. also DBA * @UMN.EDU * Michelle Coady, Chief of staff for informatics area * Supreet Kathpalia JC: do we have screen sharing? DC: not today DC: GPC's gotomeeting setup should be available in the future. KUMC also has Adobe Connect JC: gotomeeting sounds great 1. Note Public Records DC: meeting notes will be on the public web see gpc-dev<http://www.mail-archive.com/[email protected]/> for review of meeting record 1. Introductions see above 1. Epic liason (#13<http://informatics.gpcnetwork.org/trac/Project/ticket/13>): call Jan 21 JC: we have a call with Nancy Smiter from Epic to propose working methods and request effort from Epic. contact me (Jim) if you want to join ... Tue, Jan 21 1pm Nick: central time? DC: yes. DC: Jim, would you please send a message just about that meeting? ACTION JC: send invitation to Epic liaison call 1. Teleconference time (#11<http://informatics.gpcnetwork.org/trac/Project/ticket/11>) DC: I'm out of office 22 Jan, Jan 29 ... how about Tue Jan 21 11am? Lindsay: can't do then JC: can do then Hubert: OK Madison: 11am better than 9am for Tue DC: see trac issue to appear (#11<http://informatics.gpcnetwork.org/trac/Project/ticket/11>) 1. HackathonOne<http://informatics.gpcnetwork.org/trac/Project/wiki/HackathonOne> DC: Let's see how many of you have filled out the registration form... DC: agenda<http://informatics.gpcnetwork.org/trac/Project/wiki/HackathonOne#Agenda> is still rough ... Jim, I have made no tangible progress on use cases yet ?: meeting times? DC: conservatively, plan for 2 whole days. We may shorten the 2nd day. JC: so we start 1st thing Mon Jan 24? Can you confirm that, Dan? ACTION DC: confirm HackathonOne<http://informatics.gpcnetwork.org/trac/Project/wiki/HackathonOne> start time 1. standard data model (#10<http://informatics.gpcnetwork.org/trac/Project/ticket/10>) JC: I sent out a set of slides (Wednesday, January 15, 2014 6:57 AM) that are a work in progress... JC: slide 4 shows how instance relates facts JC: work items include 1. making sure we have SNOMED CT, LOINC in our [EHR] systems ... ... that our extracts will grab those... DC: that's required eventually [for prospective trials] but not for April milesone<http://informatics.gpcnetwork.org/trac/Project/milestone/mcconaughy> discussion of google docs presentation linked from: * toward a GPC/PCORI standard data model<http://www.mail-archive.com/[email protected]/msg00007.html> Dan Connolly Tue, 14 Jan 2014 22:51:38 -0800 [scribe missed lots while participating in the discussion] JC: the cardinality relationships are more clear to me now. JC: as to workplan... ... as we agree on the standard model, we'll [hard to capture] ... standard terminologies... clarity... [hard to capture] JC: I'm not sure about Marshfield [as opposed to Epic] JC: likewise Children's mercy [in Missouri] JC: for Epic sites, we should be able to [use a common approach] JC: I expect we can make that concrete on a per-domain basis [diagnoses, meds, ...] Supreet: goal would be have the same modifiers? ... ours might be different at this point JC: [missed] DC: yes, to the extent it's necessary to answer questions from breast cancer etc. groups, we'll need to align these details. I expect coordination on modifiers will be necessary. Lindsay: it makes sense to me ... next step would be to talk with Phillip, our i2b2 lead @UTSOUTHWESTERN.EDU Supreet?<http://informatics.gpcnetwork.org/trac/Project/ticket/12?>: SNOMED ... at KU Med? DC: 0 so far... UMN has more; see msg on snomed at UNMC<http://www.mail-archive.com/[email protected]/msg00004.html> JC: meaningful use 2 requires it, so we're all working toward it ?: we have an effort with SNOMED and flowsheet data. Very interested in recommendations in this area JC: Epic has laid out a reasonable plan; there's a document we can share among Epic customers * Meaningful Use Terminology Mapping Guide Last Revised: July 3, 2013 Based on the Final Rule for Stage 2 of Meaningful ?: How about sharing via epic userweb, and pointing to it from GPC proceedings? JC: yes, I was going to suggest that DC: meanwhile we can ask our Epic liaison if they'll make it world-readable JC: I wonder about Marshfield... Laurel Verhagen: I believe we have a 10am call on that. ... we've done quite a bit of ontology work toward Meaningful use 2 JC: so, Dan, it seems this ... common model is a reasonable way forward JC: sounds like we'll work with a core document such as we've begun, and a 2nd document will be a domain by domain workplan JC: should we use google docs or the wiki [attachments, I think he meant] DC: pick your poison... exchanging .ppt files is awkward, but google docs requires a google account Madison: we're cool with google docs DC: as to a work plan, that's where my trac suggestion<http://www.mail-archive.com/[email protected]/msg00002.html> comes in. Hubert: can anybody access trac? DC: yes. anybody in the world can read it. GPC participants can write to it. Use the registration form<http://informatics.gpcnetwork.org/trac/Project/register> to create an account DC: The mechanism that limits write access to GPC participants is: I get notified when an account is created, so I can block non-GPC accounts. DC demonstrates the TracRoadmap<http://informatics.gpcnetwork.org/trac/Project/wiki/TracRoadmap>, with milestone:mcconaughy<http://informatics.gpcnetwork.org/trac/Project/milestone/mcconaughy> for the April deliverables, and the related tickets JC: as to tracking work across sites? DC: I can see at least two ways: 1. one ticket that gets handed from site to sites 2. 10 tickets, one for each site JC: so how can we see how each site is doing? DC: we could create a component for each site [see TracTickets<http://informatics.gpcnetwork.org/trac/Project/wiki/TracTickets>] JC: so maybe I could sketch a plan... DC: yes, trac is good at spreadsheet import/export ACTION JC: distribute plan spreadsheet for comment
