COMPLIANCE FAILURE EVENTS Sample Clauses

COMPLIANCE FAILURE EVENTS. 3.1 Adherence to Submitted Deliverables Project Co will comply with the deliverables listed in Section 2.1, including:
Sample 1
AutoNDA by SimpleDocs

Related to COMPLIANCE FAILURE EVENTS

  • Reporting Violations a) When appropriate, faculty members will submit timely written communication to their immediate supervisor any condition that comes to their attention that may, in their judgment, pose a threat to the health or safety of any person associated with the District.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.

  • Compliance Audit LEA shall have the right but shall be under no obligation to conduct audit(s), from time to time, of Provider’s records concerning its compliance obligations as set forth in this Article V. Provider shall make such records and other documents available to LEA upon request.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • OFAC Compliance (a) Tenant represents and warrants that (a) Tenant and each person or entity owning an interest in Tenant is (i) not currently identified on the Specially Designated Nationals and Blocked Persons List maintained by the Office of Foreign Assets Control, Department of the Treasury (“OFAC”) and/or on any other similar list maintained by OFAC pursuant to any authorizing statute, executive order or regulation (collectively, the “List”), and (ii) not a person or entity with whom a citizen of the United States is prohibited to engage in transactions by any trade embargo, economic sanction, or other prohibition of United States law, regulation, or Executive Order of the President of the United States, (b) none of the funds or other assets of Tenant constitute property of, or are beneficially owned, directly or indirectly, by any Embargoed Person (as hereinafter defined), (c) no Embargoed Person has any interest of any nature whatsoever in Tenant (whether directly or indirectly), (d) none of the funds of Tenant have been derived from any unlawful activity with the result that the investment in Tenant is prohibited by law or that the Lease is in violation of law, and (e) Tenant has implemented procedures, and will consistently apply those procedures, to ensure the foregoing representations and warranties remain true and correct at all times. The term “

  • GAAP Compliance Contractor maintains an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles.

  • Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.

Time is Money Join Law Insider Premium to draft better contracts faster.