Russ and I got a chance to sync up after he was out of the office for most of
April. There are still too many things to juggle for me to feel that there's a
clear over-all plan, but we did manage to get a short list of priorities for
(almost) all sites:
1. KUMC
* federated query with manual term alignment
(#119<https://informatics.gpcnetwork.org/trac/Project/ticket/119>)
* make R Data Builder easier to install
(#87<https://informatics.gpcnetwork.org/trac/Project/ticket/87>)
2. CMH
* ramping up
3. UIOWA
* ?
4. WISC
* SAS service for miniSentinel analysis
(#117<https://informatics.gpcnetwork.org/trac/Project/ticket/117>)
5. MCW
* document, install R Data Builder
(#87<https://informatics.gpcnetwork.org/trac/Project/ticket/87>)
6. MCRF
* QA (#70<https://informatics.gpcnetwork.org/trac/Project/ticket/70>)
* full i2b2 cohort
(#36<https://informatics.gpcnetwork.org/trac/Project/ticket/36>)
7. UMN
* Hosting visit by Russ, Dan
8. UNMC
* Clarity ETL
(#64<https://informatics.gpcnetwork.org/trac/Project/ticket/64>)
* Data standardization leadership (e.g.
#114<https://informatics.gpcnetwork.org/trac/Project/ticket/114> milestone 2.7)
9. UTHSCSA
* Clarity ETL
(#74<https://informatics.gpcnetwork.org/trac/Project/ticket/74>)
* Cohort characterization tools using R Data Builder at KUMC
(#106<https://informatics.gpcnetwork.org/trac/Project/ticket/106>)
10. UTSW
* for federated query
(#119<https://informatics.gpcnetwork.org/trac/Project/ticket/119>):
* Nice labels for ER/PR receptor status in NAACCR tumor registry ETL
(#118<https://informatics.gpcnetwork.org/trac/Project/ticket/118>)
* Install R Data Builder
(#87<https://informatics.gpcnetwork.org/trac/Project/ticket/87>)
I updated the
DevTeams<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeam> page to
have a work by site
section<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams#WorkBySite>.
It also includes the all-work-related-to-a-site
report<https://informatics.gpcnetwork.org/trac/Project/report/10> that I have
showed you before as well as a more focussed work-owned-by-site
report<https://informatics.gpcnetwork.org/trac/Project/report/11>. In due
course, I hope to obsolete the manually curated list in favour of the automated
report by tweaking priorities or something, but in either case...
Jim is doing the agenda for May 6, and I haven't shared any of this with him
previously, so he's free to use these priorities or not for that meeting.
But in the weeks following, it would be great, each Monday when I/we prepare an
agenda, to find a fresh (i.e. less than a week old) update on each of your high
priority items in the ticket and/or in mail to gpc-dev. (separate messages for
separate tickets/topics, please; great big threads under "KUMC status this
week" would be a pain.).
For group discussions that you're leading, a succinct summary of the current
positions would be ideal. For tickets that are mostly just work at your site or
with a few other sites, a status update would be great.
And remember to either to re-assign or close a ticket when you've done all you
can do or plan to do on it.
Meanwhile, the "this meeting seems too short" comments at the end of our 29 Apr
meeting got me thinking... I've never been to a 2 hour teleconference that was
worth the time, but 90 minutes can work. My preference, though, is for the bulk
of the work to happen *between* meetings, and for the group meeting to mostly
be coordination, clarifying who has the ball on what etc. I also realized that
we don't have to have full-group weekly meetings at all. My habits from open
standards work need not apply.
--
Dan
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
