130 likes | 288 Views
Research Unit Liaison Meeting. April 30, 2012. eRPM System Updates. SF424 Grants.gov: Version 2.0 released on 04/28/12 NIH validations updated to support: Administrative supplements Can submit NIH funding supplements electronically, as part of NIH pilot program.
E N D
Research Unit Liaison Meeting April 30, 2012
eRPM System Updates SF424 Grants.gov:Version 2.0 released on 04/28/12 • NIH validations updated to support: • Administrative supplements • Can submit NIH funding supplements electronically, as part of NIH pilot program. • Grants. gov validation rules (v.5.0) • New supported form: Budget Information for Construction Programs (SF-424C) V.2.0
eRPM System Updates Tentative Release Date: 05/12/12 Release 2.2 – what’s coming: New date field and business process change: • Published sponsor deadline • To record the submission date set by the sponsor • Sponsor Deadline • Date unit expects proposal to be sent to the sponsor
eRPM Training Updated • PAF eLearning course: • Pre-requisite for instructor-led • Covers system basics • Instructor-led course: • Covers business processes • More specific • Shorter (4 hours) http://www.umich.edu/~eresinfo/erpm/training.htm • Course changes based on your feedback: • Grants. gov (e.g., field mapping from PAF) • Processes: • States & their associated activities • Request ORSP action vs. post a comment • Hardship • Post award: PAN/PAC
COI Project Update PHS Requirements: What U-M Needs To Do: Develop a new business process that includes: A comprehensive disclosure system Management tools for COI committees: input, review, tracking, and archiving Tracking for research personnel after award A means for public reporting Training • Key investigators must disclose ALLfinancial interests. • Disclosures completed annually and within 30 days of a change. • Significant financial interests reviewed in relation to ALL U-M responsibilities (not just research). • U-M determines relatedness to proposed research. • U-M manages significant financial interests beforePHS funding awarded. • U-M makes financial conflicts of interest (FCOI) and management plans available to the public.
COI Project Update The COI Project Teams have been working on: • Unit determines who discloses: • Faculty with PHS funding • All faculty • Faculty & staff • No change for units already using M-Inform • Updating PAF to capture project personnel: • Who are responsible • Who need to disclose/have disclosed • COI committees & staff developing a management plan process & template that facilitates reporting of Financial Conflicts of Interest (FCOI): • By individual • By project • By outside entity Capture data in eRPM Manage in Conflict Admin Disclose in M-Inform “Responsible” = person required to contribute knowledge or who conducts original work independently (i.e., requiring little/no supervision) for the project. E.g., design the study protocol or methodology; analyzes and interprets data or results.
COI Project Update • Unit agreement to use one disclosure form for U-M • Form updated based on unit feedback: • Three (3) General Questions • If answer “yes” to general questions, subsequent questions used to provide details • Definitions and examples included, with links to U-M resources
COI Project Update • In PAF, Personnel question to be updated to capture who is responsible for proposal. • If PHS-funded, those responsible must disclose in M-Inform. • eRPM feeds PHS data to M-Inform at time proposal submitted.
COI Project Update • New: PAF displays disclosure status for those responsible. • U-M can’t award the project until all disclosures are completed, evaluated, and managed if conflict identified.
COI Project Update Who is working on the project: COI Unit Contacts • LSA: Jim Burkel, Peggy Westrick • Medical School: June Insco • Nursing: Mary Martinowicz • OVPR: Curt Smitka • Pharmacy: Bruce Mueller, Susan Johnson • Public Health: Sharon Kardia • Public Policy: Marcy Brighton • Rackham: John Godfrey • Social Work: Ruth Dunkle, Jorge Delva, Scott Stanfill, Candace Terhune-Flannery • SNRE: Michael Moore, Lara Nelson • University Audits: Sherry Cogswell, Jennifer Vitale • University Library: Robert Campe, Anne Beaubien • Architecture & Urban Planning: Linda Mills • Business School: Sally Sivrais • Dearborn: Martin Hershock, Drew Buchanan • Dentistry: Charlotte Mistretta, Mary Jo Gray • Education: Elizabeth Moje • Engineering: Elizabeth Wagner, Bekah Ashley • Flint: Terry Van Allen • Information: Becky O’Brien • ISR: James Jackson, Anna Schork • Kinesiology: Elizabeth Tropiano • Law School: Christina Luo • Life Sciences Institute: Liz Barry, Erin Stephens Roles & Responsibilities: • Represent unit in decision-making; provide timely feedback/approval for project milestones. • Review deliverables describing key decisions about system design and process. • Advise the project team on system functionality related to each release, including future enhancements. • Communicate project decisions, share deliverables, etc. to prepare unit for the upcoming change.
COI Project Update COI Unit Contact Action Items: • Finalize disclosure audience for unit • Faculty with PHS funding only, or • All faculty, or • Faculty & staff • Identify who fulfills M-Inform roles
COI Project Update Next step: Change Management Research ULs: COI Project Team Develop a communication package for COI Unit Contacts/Research ULs: Overview of change (infocast) OVPR web page (one-stop resource) Communication template M-Inform role assignments Resources Action items M-Inform training eRPM training updates • Help COI Unit Contacts to raise unit awareness: • PHS regulation deadline • Outside interest disclosure: • COI policy (to be updated for PHS regulation) • M-Inform use • Annual disclosure timeframe • Provide unit-based context