CFAR Progress Report Instructions & Examples

Total Page:16

File Type:pdf, Size:1020Kb

CFAR Progress Report Instructions & Examples

Revised 10/29/15 CORE B: DEVELOPMENTAL CORE List all leadership positions as applicable. Director(s): Associate Director(s): Assistant Director(s):

See also the Appendix Guidance for additional information about required reporting information for Core B I. Narrative for Current Reporting Period (no more than 5 pages)

A. Highlights The purpose of section I.A is to provide a short big picture, “elevator speech” overview of Core B’s key NIH- related successes over the last year. Highlighted information includes, but is not restricted to:  the number of junior investigators, and senior investigators new to AIDS, assisted,  major current activities of the Core (e.g., mentoring, RFA topics, career development, and etc., as applicable)  table of pilot applications submitted, funded, not funded, and etc.

Funding Investigator Name Title Amount Funded/Not Funded Mechanism*

*Pilot Award (round 1, round 2), Administrative Supplement, and etc. (feel free to list specific funding mechanisms at your CFAR)

B. Progress in Meeting Core B Specific Aims List each of Core B’s Specific Aims, and describe new progress made since the last progress report was submitted. Use quantitative language when possible and make the value added explicit. Do not use examples that have been reported before unless you have new information.

C. Changes to Core B Made During the Current Reporting Period Report here any changes that were made to Core B leadership, specific aims, services and activities, and/or policies and procedures. For each change reported, make it clear to NIH readers: a) what the impetus for the change was and b) what benefit(s) have come from making the change.

D. Future Plans Describe the Core’s plans for next year: For any planned alteration (including, but not restricted to, changes in leadership, specific aims, services and activities, or policies and procedures) describe the change, the reason for the change, and the expected benefits of the change.

[Type text] [Type text] [Type text] Plans Based on Input from a Formal Evaluation Process Focus on plans that are grounded on advice received from advisory committees, Core user feedback, and/or an evaluation of the Core. Plans Based on Other Impetus Focus on plans that are the result of an impetus other than input from an evaluation process.

II. Other Core Information (Does not count towards page limits)

Core Users The purpose of section II.A is to quantify the number of CFAR Users by Category served by Core B during the current reporting period. Core B Users in the Current Reporting Period NIH Funding Category Number NIH AIDS PI 1: NIH Independent Investigators (AIDS) Bringing into AIDS 2: NIH Independent Investigators (non-AIDS) 3: NIH New Investigators AIDS-research Pipeline 4: CFAR Users with no prior non-CFAR NIH funding

Total

NIH Special Emphasis Category Number 5: Recipients of Core B awards 6: Recipients of CFAR Supplement funds

C. Other Core B Activities

The purpose of the table below is to classify and quantify the number served for any Core B activity other than already described above Provide details of activities in Appendix C.1 (“Other Core B Activities”)

Activity (examples below) Number Served Travel Awards 3 Application Development Support 2 Poster design tutorials 9

III. New Publications Describing Work Supported by the Core (Does not count towards page limits) To the extent possible, Core B staff should try to follow up with previous awardees for new publication since the last reporting period. Data provided should include new (i.e. published during the current reporting period) publications that describe work supported by the relevant developmental award or NIH supplement.  List new publications that are linked to the CFAR base grant here.  For each citation, follow the format below.  Provide citations in alphabetical order by first author, bold face CFAR authors.  Do not attach copies of actual publications. 1. [Citation] PMID number

Revised 10/29/15 PMCID number:

IMPORTANT NOTE: In order to comply with NIH Public Access Policy, (http://publicaccess.nih.gov) any peer-reviewed manuscripts that arise from NIH funds, including Core B-funded projects, MUST be submitted to PubMed Central upon acceptance. Once a manuscript is properly submitted to PubMed Central, the corresponding author will receive an NIH Manuscript Number and, eventually, a PubMed Central ID (PMCID).

Please note that a PubMed ID (PMID) is not the same thing as a PubMed Central ID (PMCID).

Across the CFAR, publications are tied to your CFAR only by a PMID or NIH Manuscript Number. If a publication does not have either number your CFAR will not receive credit for the support provided to work described in that publication.

Furthermore, any Core B-funded publication that is out of compliance with the Public Access policy (i.e. does not have a PMCID number) places renewal of that CFAR’s annual award at risk.

MyNCBI Report The MyNCBI report requirement is specific to Core B. 1. After completing the Core B template, convert the finished document to a pdf. 2. Include a MyNCBI report for all publications listed in Section III above. 3. Upload the combined pdf to section B.2 of the “Core B” component in the RPPR application.

[Type text] [Type text] [Type text]

Recommended publications