Annual Data Use Report definition

Annual Data Use Report. A report submitted to the DAC on the anniversary of access approval summarizing the analysis of NIH genomic datasets obtained through the Data Access Request and any significant findings derived from the work. Approved User: Post-DAC approval will include the PI, collaborators at the home institution who are named in the “Senior/Key Person Profile” portion of the DAR, the IT Director or designee named in the “Senior/Key Person Profile” portion of the DAR, and trainees or staff to these investigators. Contributing Investigator: The researcher who submitted the genomic dataset to dbGaP. Data Access Request: SF 424 (R&R) cover pages and requested attachments, if any. Data Derivative: any data including individual-level data or aggregate genomic data that stems from the original dataset obtained through dbGaP. Excepted from this term is summary information that is expected to be shared through community publication practices. Final Data Use Report: A final report submitted to the DAC at the conclusion of the approved access period when no additional access is sought, or when leaving an institution. This report should summarize the analysis of GWAS datasets obtained through the Data Access Request and any significant findings derived from the work.
Sample 1Sample 2Sample 3
Annual Data Use Report. A report submitted to the NIH on the anniversary of access approval summarizing the analysis of NIH genomic datasets obtained through the Data Access Request and any significant findings derived from the work. Approved User: In addition to the PI, approved users may include the PI, collaborators at the home institution who are named in the “Senior/Key Person Profile” portion of the DAR, the IT Director or designee named in the “Senior/Key Person Profile” portion of the DAR, and trainees or staff to these investigators. Contributing Investigator: The researcher who submitted the genomic dataset to dbGaP. Data Access Request: SF 424 (R&R) cover pages and requested attachments, if any. Data Derivative: any data including individual-level data or aggregate genomic data that stems from the original dataset obtained through dbGaP. Excepted from this term is summary information that is expected to be shared through community publication practices. dbGaP Approved User Code of Conduct: A short summary highlighting key principles and practices agreed to by all research investigators requesting access to NIH genomic data from dbGaP. The elements within the Code of Conduct reflect the Terms of Access in this agreement. Failure to abide by the Code of Conduct as agreed to at the time a dbGaP Project Request is submitted may result in revocation of access to any and all approved data sets.
Sample 1Sample 2Sample 3
Annual Data Use Report. A report submitted to the DAC on the anniversary of access approval summarizing the analysis of NIH genomic datasets obtained through the Data Access Request and any significant findings derived from the work. Approved User: Post-DAC approval will include the PI, collaborators at the home institution who are named in the “Senior/Key Person Profile” portion of the DAR, the IT Director or designee named in the “Senior/Key Person Profile” portion of the DAR, and trainees or staff to these investigators. Contributing Investigator: The researcher who submitted the genomic dataset to dbGaP. Data Access Request: SF 424 (R&R) cover pages and requested attachments, if any. Data Derivative: any data including individual-level data or aggregate genomic data that stems from the original dataset obtained through dbGaP. Excepted from this term is summary information that is expected to be shared through community publication practices.
Sample 1Sample 2

Examples of Annual Data Use Report in a sentence

  • It is agreed that the Annual Data Use Report will be shared with the NIH within the context of a renewal Data Access Request, or via a letter signed by the Institutional Signing Official and the Approved User.

  • Approved Users agree to send the Annual Data Use Report prior to the anniversary of the Approved Access Date assigned by the DAC and specified within the manifest file provided to Approved Users by the NIH Data Repository at the time that data access is provided.

  • Approved Users thus agree to provide a brief Annual Data Use Report on the research specified within the DAR submitted with this DUC.

  • In the area of payments, other donors are also active, however their attention is mainly focused on e-money operations.

  • Motors Corp., 460 F.3d 231, 234 (2d Cir.2006) (citation and internal quotation marks omitted).

  • The additional lighting proposed would not be in conformity with the City’s Zoning Ordinance.

  • It is agreed that the Annual Data Use Report will be shared with the NIH within the context of a renewal Data Access Request, or via a letter signed by the Institutional Signing Official and the Approved User.Annual Data Use Reports should be submitted to:Note that any inadvertent or inappropriate data release incidents should be reported to the JAAMH Data Access Committee according to the agreements and instructions under Term 6.

  • This information will be used by the JAAMH Data Access Committee staff for program evaluation activities, and may be considered by the NIH GWAS Governance committees as part of the NIH effort to provide ongoing oversight and management of all NIH genomic data sharing activities.Approved Users thus agree to provide a brief Annual Data Use Report on the research specified within the DAR submitted with this DUC.


More Definitions of Annual Data Use Report

Annual Data Use Report. A report submitted to the DAC on the anniversary of access approval summarizing the analysis of NINDS PDBP datasets obtained through the Data Access Request and any significant findings derived from the work. Approved User: Post-DAC approval will include the PI, collaborators at the home institution who are named in the “Senior/Key Person Profile” portion of the DAR, and trainees or staff to these investigators. Contributing Investigator: The researcher who submitted the PDBP dataset to PDBP DMR. Data Derivative: any data including individual-level data or aggregate PDBP data that stems from the original dataset obtained through PDBP DMR. Excepted from this term is summary information that is expected to be shared through community publication practices. Data Management Resource, PDBP-aka DMR. PDBP DMR Approved User Code of Conduct: A short summary highlighting key principles and practices agreed to by all research investigators requesting access to NINDS PDBP data from PDBP DMR. The elements within the Code of Conduct reflect the Terms of Access in this Data Use Agreement (DUA). Failure to abide by the Code of Conduct as agreed to at the time a PDBP DMR Project Request is submitted may result in revocation of access to any and all approved data sets. Final Data Use Report: A final report submitted to the DAC at the conclusion of the approved access period when no additional access is sought, or when leaving an institution. This report should summarize the analysis of PDBP study datasets obtained through the Data Access Request and any significant findings derived from the work.
Sample 1
Annual Data Use Report. A report submitted to the DAC on the anniversary of access approval summarizing the analysis of NIH genomic datasets obtained through the Data Access Request and any significant findings derived from the work. Approved User: Post-DAC approval will include the PI, collaborators at the home institution who are named in the “Senior/Key Person Profile” portion of the DAR, the IT Director or designee named in the “Senior/Key Person Profile” portion of the DAR, and trainees or staff to these investigators. Contributing Investigator: The researcher who submitted the genomic dataset to dbGaP. Data Access Request: SF 424 (R&R) cover pages and requested attachments, if any. dbGaP Approved User Code of Conduct: any data including individual-level data or aggregate genomic data that stems from the original dataset obtained through dbGaP. Excepted from this term is summary information that is expected to be shared through community publication practices. Final Data Use Report: A final report submitted to the DAC at the conclusion of the approved access period when no additional access is sought, or when leaving an institution. This report should summarize the analysis of genomic study datasets obtained through the Data Access Request and any significant findings derived from the work.
Sample 1

Related to Annual Data Use Report

  • Information Package means the most recent compilation of financial and other data with respect to the Failed Bank, including any amendments or supplements thereto, provided to the Assuming Institution by the Corporation on the web site used by the Corporation to market the Failed Bank to potential acquirers.

  • Line Information Data Base (LIDB) means a transaction-oriented database system that functions as a centralized repository for data storage and retrieval. LIDB is accessible through CCS networks. LIDB contains records associated with End User line numbers and special billing numbers. LIDB accepts queries from other network elements and provides return result, return error, and return reject responses as appropriate. Examples of information that Account Owners might store in LIDB and in their Line Records are: ABS Validation Data, Originating Line Number Screening (OLNS) data, ZIP Code data, and Calling Name Information.

  • Appendix Information means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in:

  • Compliance Statement is that certain statement in the form attached hereto as Exhibit B.

  • Monthly Report The meaning specified in Section 10.7(a).