Program User Group Meeting Minutes
August 3, 2001


Date: August 3, 2001
Time: 9:00 am
Location: Rockledge 2, Rooms 9116/9112
Chair: Mr. Burdette W. Erickson
Next Meeting: September 7, 2001, Rockledge 2, Rooms 9116/9112, 9:00 am

Action Items

1. (All) Determine how many program directors use the ICO module and obtain feedback about their experience, including a problem list. Mr. Erickson estimates that 10-33% of the program directors on campus currently use ICO.

2. (All) Provide input to Derrick Tabor and the Type 5 ESNAP subcommittee on how program officials do their jobs.

3. (IC representatives) If your IC provides grantees supplemental instructions for completing progress reports, send a copy of the instructions to Derrick Tabor and the Type 5 ESNAP subcommittee.

4. (Derrick Tabor and ESNAP subcommittee) Make a list of design issues for SNAP.

5. (Derrick Tabor and ESNAP subcommittee) Obtain input from grants management officers about the accuracy of time and effort reporting by PIs.

6. (Derrick Tabor) Conduct a meeting with ePUG volunteers within the next two weeks to discuss the draft MC 4444 Monitoring Grant Progress Reports.

7. (Krishna Collie) Bring a matrix of ICO users to the September 7 ePUG meeting.

8. (Krishna Collie) Invite Oracle developer Michael Martin to attend the September 7 ePUG meeting to discuss development of the IMPAC II Program module.

9. (Michael Martin) At the September 7 ePUG meeting, discuss the viability of creating a pop-up window that displays all NIH grants for each PI and provides links to all outside support. Each PI would be required to update this information.


Presentations and Discussion Topics

1. ICO Survey from NIAID - Dr. Opendra Sharma (See Attachment A)
Dr. Sharma presented a list of ICO problems compiled by Blanche O'Neill during her survey of NIAID program officers. The following issues were highlighted:

a. At NIAID, the system often is unstable and freezes, requiring users to shut down and restart. During the subsequent discussion of this problem, other institutes reported fewer problems. Institute-specific time-out settings or bandwidths could be responsible for some of the problems.

b. After a user selects the approval check box, it is impossible to edit, correct, or resume entry of a project summary. Users sometimes cannot complete the summary in one sitting and need to be able to continue at a later time.

c. NIAID would like to add word processing capabilities or be able to activate Word or WordPerfect from the project summary section. Users are hampered by the lack of a spell check function and also experience inconsistent transfer of punctuation characters between word processing applications and ICO. Mr. Erickson noted that NCI's shadow system enables users to access Word when entering supplementary information.

d. Users would like program notes to be part of the permanent record. The original author of the program notes should be able to edit them; currently, once the notes are saved, no changes can be made.

e. The size of the sign notes section should be increased. Although the program notes section provides additional space, it is inefficient to enter information in two sections. It would be more useful to have a single text-entry area for both brief and long documents.

f. Incorporation of streaming video or other computer-based instruction would help first-time and infrequent users to use the system more efficiently.

g. Users would like to be able to reverse a signoff.

In the discussion following Dr. Sharma's presentation, Mr. Erickson stressed that by documenting user responsibilities and current functional area process flows, ePUG can help design user-friendly tools that reflect users' needs. If a system is difficult to use or does not help users to perform their required tasks, then it will not be accepted or used.

Data integrity is another vital aspect of system acceptance. Serious data problems in the IMPAC I system have created user mistrust. The eRA project has awarded QRC a contract to verify data integrity and recommend procedures for safeguarding data reliability in IMPAC II.

Each institute has its own business practices, and most institutes have an investment in shadow systems. System requirements must reflect business practices and may help make those practices more efficient. Making ICO and shadow system functionality available across NIH will aid in the development of the IMPAC II Program module critical design features. Extension systems eventually may be tied into the IMPAC II database to ensure data accessibility.

To encourage institute buy-in to IMPAC II, eRA must build an enterprise system that enables users to obtain and modify inter-related information across functional areas like Peer Review and Grants Management. Users need automatic email or a tickler system that informs the next person in the grants approval process when a step has been completed. For example, when a program officer approves a grant, the system should automatically inform Grants Management of this action so that the next step in the process can be performed.

Because all data eventually will be in IMPAC II tables, it is necessary to determine any critical data elements that are not already there, and then consider how best to enter and retrieve this information. After population tracking is incorporated into the ICO module, program directors will be required to use it and IMPAC II.

2. Report from the Type 5 ESNAP Subcommittee - Dr. Derrick Tabor (See Attachments B and C)

a. Web links to information about Program Officer responsibilities
ePUG must ensure that the new Program module enables program directors to fulfill their legal obligations. For additional information on the laws and regulations governing Program Officer responsibilities, Dr. Tabor recommended the links available on the NIH Grants Policy Statement (10/98) web page at http://grants.nih.gov/grants/policy/nihgps/master_list.htm and on the GrantsNet web page at http://www.hhs.gov/grantsnet . Dr. Caban noted that the Project Officers/Program Officers Forum (POPOF) web page at http://odoerdb2.od.nih.gov/oer/committees/popof/popof.htm also provides information.

b. Subcommittee recommendations
Dr. Tabor presented recommendations from subcommittee meetings held on June 25 and July 26. The following points were raised during discussion of Attachment B:

  • PIs must be able to attribute publications to specific grants and must be able to enter more than one grant source for each publication.
  • PIs must be able to differentiate between summer and academic year support.
  • Program officials increasingly seek to minimize meaningless time and effort input. PIs often do not have a bookkeeping system and may "invent" figures.
  • More discussion is needed to address monitoring and recruitment/retention issues for clinical use of human subjects. The use of a retention check box or flag was discussed.
  • Input from program officials is needed to make the Type 5, especially the significance section, more useful and to address the specific data that should be included in progress reports.

    c. Discussion of Consensus Proposed Changes to SNAP Business Process
    The Commons Working Group (CWG) will discuss the consensus changes to the SNAP business process on August 18 in Portland, Oregon. The following points were raised during discussion of Attachment C:

  • There will be no changes to the abstract at this time, although it eventually will be replaced by the Type 2.
  • The progress report is still needed. In a compromise with OER, ePUG agreed on a required submission time of 45 days prior to the anniversary date of the grant.
  • One participant suggested that new functionality could allow PIs to enter time-stamped comments about research accomplishments through the Commons. The National Science Foundation system includes this option.
  • Each user must maintain locator information and citations through the Commons. It would be useful to have the system extract citations from the progress report and insert them into the profile.
  • Standardization of citations would be useful.


    3. NIH Policy Manual Chapter for Monitoring Grant Progress Reports - Mr. Bud Erickson (See Attachment D)
    Mr. Erickson distributed copies of the "Monitoring Grant Progress Reports Policy" chapter from the NIH Policy Manual. The proposed checklist in the appendix to this chapter specifies the information that program officials need from progress reports. Mr. Erickson would like to see a portal established to this checklist from ICO. Discussion centered on the following issues:
    Appendix 1, Grant Project Performance Monitoring Report
    Page 1, item 1: This item could be reworded as follows: "Has anything of extraordinary significance occurred? If so, explain."
    Page 1, item 3: The information in this item could be misused.
    Page 1, item 6: Add "new sites" to the following sentence: "Are there changes/concerns regarding the user of human research subjects?"
    Page 1, item 8: This item may need to be reworded.


    4. IMPAC II Program Portal and Module - Krishna Collie

    a. Program Module Objectives
    A two-phase development process will result in the design and deployment of a web-based tool that meets the needs of the Program Officer community. The Program business area focuses on human interaction and on the monitoring of key indicators.
    The short-term solution to meeting Program needs is to develop a portal that provides easy access to needed functions. In the long-term, an IMPAC II Program module will be developed.
    The following aspects of the Program business area will be incorporated in the new portal and module:

  • Grant cycle
  • Portfolio management
  • Program planning and evaluation
  • Signoff responsibility
  • IC-level planning
  • Management IC program

    b. Program Module Development - Phase One - Portal
    In Phase One, a web-based portal will be designed using J2EE architecture. The portal will provide Program staff with localized, customized links to the applets they use most often. With a single logon, the portal will provide a one-stop, IC-specific gateway to program functions, IMPAC II, shadow systems, MEDLINE, and so on. Content management is key.
    JAD members currently are being solicited. A five-to-six month design period is anticipated. The CDR will be distributed to ePUG in November 2001.

    c. Program Module Development - Phase Two - IMPAC II Program module
    The new Program module will incorporate the best features of the ICO module and the institutes' shadow systems. Changes made to ICO will help determine the critical design requirements for the new module.

    Attendees

    Asanuma, Chiiko (NIMH)   Lederhendler, Israel (NIMH)   Strasburger, Jennifer (NCI)
    Caban, Carlos (OER)   Martin, Carol (NHGRI)   Swain, Amy (NCRR)
    Collie, Krishna (OD)   Monheit, Madeline (OD/OPAE)   Tabor, Derrick (NIGMS)
    Erickson, Burdette (NCI, Chair)   Paterson, Beth (NIDDK)   Wehrle, Janna (NIGMS)
    Gezmu, Misrak (NIAID)   Rumney, Christine (OD/OPAE, Recorder)   Young, Janet (NIAID)
    Hann, Della (OER)   Sharma, Opendra (NIAID)   
    Hudgings, Carole (NINR)   Sharrock, William (NIAMS)   

    Attachments
    A. ICO Survey from NIAID
    B. Suggestions and Remarks from Program Officials on the Type 5 Progress Report
    C. Consensus Proposed Changes to SNAP Business Process
    D. NIH Policy Manual Chapter for Monitoring Grant Progress Reports