SHARING RESEARCH DATA Sample Clauses

SHARING RESEARCH DATA. The Contractor's data sharing plan, due date to be determined at contract award, is hereby incorporated by reference. The Contractor agrees to adhere to its plan and shall request prior approval of the Contracting Officer for any changes in its plan. BARDA endorses the sharing of final research data to serve health. This contract is expected to generate research data that must be shared with the public and other researchers. BARDA recognizes that data sharing may be complicated or limited, in some cases, by institutional policies, local IRB rules, as well as local, state and Federal laws and regulations, including the Privacy Rule (see HHS-published documentation on the Health Information Privacy at xxxx://xxx.xxx.xxx/ocr/privacy/index html). The rights and privacy of people who participate in BARDA- funded research must be protected at all times; thus, data intended for broader use should be free of identifiers that would permit linkages to individual research participants and variables that could lead to deductive disclosure of the identity of individual subjects.
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
SHARING RESEARCH DATA. The contractor’s data sharing plan, dated September 29, 2004 is hereby incorporated by reference. The contractor agrees to adhere to its plan and shall request prior approval of the Contracting Officer for any changes in its plan. The NIH endorses the sharing of final research data to expedite the translation of research results into knowledge, products, and procedures to improve human health. This contract is expected to generate research data that must be shared with the public and other researchers. NIH’s data sharing policy may be found at the following Web site: NIH recognizes that data sharing may be complicated or limited, in some cases, by institutional policies, local IRB rules, as well as local, state and Federal laws and regulations, including the Privacy Rule (see HHS-published documentation on the Privacy Rule at xxxx://xxx.xxx.xxx/ocrf). The rights and privacy of people who participate in NIH-funded research must be protected at all times; thus, data intended for broader use should be free of identifiers that would permit linkages to individual research participants and variables that could lead to deductive disclosure of the identity of individual subjects.
Sample 1
SHARING RESEARCH DATA. BARDA endorses the sharing of final research data to serve health. This contract is expected to generate research data that must be shared with the public and other researchers. BARDA recognizes that data sharing may be complicated or limited, in some cases, by institutional policies, local IRB rules, as well as local, state and Federal laws and regulations, including the Privacy Rule (see HHS-published documentation on the Health Information Privacy at xxxxx://xxx.xxx.xxx/hipaa/index.html). The rights and privacy of people who participate in BARDA-funded research must be protected at all times; thus, data intended for broader use should be free of identifiers that would permit linkages to individual research participants and variables that could lead to deductive disclosure of the identity of individual subjects.
Sample 1
SHARING RESEARCH DATA. The data sharing plan submitted by the contractor is acceptable. The contractor agrees to adhere to its plan and shall request prior approval of the Contracting Officer for any changes in its plan. The NIH endorses the sharing of final research data to expedite the translation of research results into knowledge, products, and procedures to improve human health. this contract is expected to generate research data that must be shared with the public and other researchers. NIH’s data sharing policy may be found at the following Web site: NIH recognizes that data sharing may be complicated or limited, in some cases, by institutional policies, local IRB rules, as well as local, state and Federal laws and regulations, including the Privacy Rule (see HHS-published documentation on the Privacy Rule at hxxx://xxx.xxx.xxx/xxx/). The rights and privacy of people who participate in NTH-funded research must be protected at all times; thus, data intended for broader use should be free of identifiers that would permit linkages to individual research participants and variables that could lead to deductive disclosure of the identity of individual subjects.
Sample 1
SHARING RESEARCH DATA. The data sharing plan submitted by the Contractor is acceptable. The Contractor agrees to adhere to its plan and shall request prior approval of the Contracting Officer for any changes in its plan. The NIH endorses the sharing of final research data to expedite the translation of research results into knowledge, products, and procedures to improve human health. This contract is expected to generate research data that must be shared with the public and other researchers. NIH's data sharing policy may be found at the following Web site: xxxx://xxxxxx.xxx.xxx/grants/guide/notice-files/NOT-OD-03-032.htm1. NIH recognizes that data sharing may be complicated or limited, in some cases, by institutional policies, local IRB rules, as well as local, state and Federal laws and regulations, including the Privacy Rule (see HHS-published documentation on the Privacy Rule at xxxx://xxx.xxx.xxxxxxxx. The rights and privacy of people who participate in NIH-funded research must be protected at all times; thus, data intended for broader use should be free of identifiers that would permit linkages to individual research participants and variables that could lead to deductive disclosure of the identity of individual subjects.
Sample 1

Related to SHARING RESEARCH DATA

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Development Records Each Party shall maintain complete, current and accurate records of all Development activities conducted by it hereunder, and all data and other information resulting from such activities. Such records shall fully and properly reflect all work done and results achieved in the performance of the Development activities in good scientific manner appropriate for regulatory and patent purposes. Each Party shall document all non-clinical studies and Clinical Trials in formal written study reports according to Applicable Laws and national and international guidelines (e.g., ICH, cGCP, cGLP, and cGMP).

  • Project Information Except for confidential information designated by the City as information not to be shared, Consultant agrees to share Project information with, and to fully cooperate with, those corporations, firms, contractors, public utilities, governmental entities, and persons involved in or associated with the Project. No information, news, or press releases related to the Project, whether made to representatives of newspapers, magazines, or television and radio stations, shall be made without the written authorization of the City’s Project Manager.

  • Program Development NWESD agrees that priority in the development of new applications services by XXXXX shall be in accordance with the expressed direction of the XXXXX Board of Directors operating under their bylaws.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!