200 likes | 355 Views
SPIRiT Kickoff Meeting. TIES Overview. Associate Professor, Department of Biomedical Informatics, University of Pittsburgh, School of Medicine crowleyrs@upmc.edu. Rebecca Crowley. Outline. What is caTIES ? What is TIES? History System (with demonstration) Evaluation Deployment
E N D
SPIRiT Kickoff Meeting TIES Overview Associate Professor, Department of Biomedical Informatics, University of Pittsburgh, School of Medicine crowleyrs@upmc.edu Rebecca Crowley
Outline • What is caTIES? What is TIES? • History • System (with demonstration) • Evaluation • Deployment • Status Report at University of Pittsburgh • Other sites • Institutional Support and User Community • Work towards understanding requirements for a collaborative tissue network
What is caTIES? • An NCI and CTSI funded research project • An open-source application for creating large repositories of highly processed, highly indexed, concept-coded, de-identified clinical documents • Retrieval of paraffin-embedded remainder tissue • Built on the GATE architecture • De-identification component typically de-ID but others are possible • Utilizes NCI vocabularies and MMTx (as well as NegEx and other components developed at Pittsburgh) • User Interface developed with HCI methods • Honest Broker paradigm • Grid communications (Globus) and Security Infrastructure (GSI, Dorian) for communication among nodes
What is TIES? • Deployed UPMC-approved system for retrieving data and identifying and ordering tissue using surgical pathology clinical reports • Provides access to 1.7 million de-identified pathology reports, across all UPMC hospitals, from 1995-present, updated weekly and automatically from clinical systems • Close working relationship with Health Sciences Tissue Bank and Honest Broker human systems throughout University/UPMC • IT support, Training, Marketing activities • Currently has 100 users and 14 active protocols
History - 1 • 2001 - 2006 Shared Pathology Informatics Network • NCI Sponsored U01 (Collaborative Consortium) • Harvard, UCLA, Regenstreif, Pittsburgh • NLP tools, ideas, first demonstration of data-sharing • 2005 - 2008 caBIG • Large multi-CC contract/community developing architecture + open source, interoperable systems for cancer research community • caTIES code base • Security Architecture • Grid Communications • User Interface • Version 1 and 2 • Four institutions sharing some data, IRB protocol Penn-Pitt
History - 2 • 2006 – 2011 University of Pittsburgh CTSA Project (ongoing) • Deployed at University of Pittsburgh • Worked with Tissue Bank • Set up honest brokers • Policies and Processes • IRB issues • caTIES v3 • 2009 – 2014 caTIES NCI funded project (ongoing) • More autonomy • Stable, consistent release cycle • User community • New features
Deployment at University of Pittsburgh • Currently 100 users and 14 active protocols • Marketing through end-user lunches and other events (8 workshops – 113 total participants) • IT Support through ISD • Website for account requests • http://ties.upmc.com/ • Training of End-Users • User manual and Videos
caTIES Deployments Since January 2010… • 878 downloads • 200+ forum posts • 3,000 unique visitors to caTIES website • 2,000 pageviews/month on Sourceforge • 25 requests for caTIES demo accounts
Resources for Deploying Institutions • FTE Estimates • Sample Implementation Plan • Web Resources • Policies and Processes • Pitt/Penn IRB Submission • Training Materials • Marketing Materials • caTIES Office Hours after each release
User Community • Yearly caTIES user meeting • caTIESSourceForge site • http://sourceforge.net/projects/caties/ • User forums and listservs • Bug reports and feature requests • caTIES project website • http://caties.cabig.upmc.edu/ • Details and support for implementation
Developing a Collaborative Network • Many players (caBIG, iDASH, NCBCs etc) make this a moving target • Great deal of work, needed to develop network, was done as part of caBIG Security Project (Manion, Robbins, Weems, Crowley, Whitney) • Foundation of work by Becich et al in Tissue Sharing • Policies for internal operation AS WELL AS multi-institutional use of the system • Trust Agreement, Concept of Operations, Requirements for Governing Body, etc. • SPIRiT is a different animal and probably MUCH easier because entry does not need to be open-ended.
Challenges • Governance • Trust Fabric • IRB issues (especially training modules) • De-identification and HIPAA • Auditing and Risk Management • ‘Real’ deployments and ‘Real’ use cases • Size and scope, present and future • Funding this effort