Notification of Possible Breach BA shall notify CE within twenty-four (24) hours of any suspected or actual breach of Protected Information; any use or disclosure of Protected Information not permitted by the Contract or Addendum; any security incident (i.e., any attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in and information system) related to Protected Information, and any actual or suspected use or disclosure of data in violation of any applicable federal or state laws by BA or its agents or subcontractors. The notification shall include, to the extent possible, the identification of each individual whose unsecured Protected Information has been, or is reasonably believed by the BA to have been, accessed, acquired, used, or disclosed, as well as any other available information that CE is required to include in notification to the individual, the media, the Secretary, and any other entity under the Breach Notification Rule and any other applicable state or federal laws, including, but not limited to, 45 C.F.R. Section 164.404 through 45 C.F.R. Section 164.408, at the time of the notification required by this paragraph or promptly thereafter as information becomes available. BA shall take (i) prompt corrective action to cure any deficiencies and (ii) any action pertaining to unauthorized uses or disclosures required by applicable federal and state laws [42 U.S.C. Section 17921; 45 C.F.R. Section 164.504(e)(2)(ii)(c); 45 C.F.R. Section164.308(b)].
Reportable Events Involving the Xxxxx Law Notwithstanding the reporting requirements outlined above, any Reportable Event that involves solely a probable violation of section 1877 of the Social Security Act, 42 U.S.C. §1395nn (the Xxxxx Law) should be submitted by Practitioner to CMS through the self-referral disclosure protocol (SRDP), with a copy to the OIG. If Practitioner identifies a probable violation of the Xxxxx Law and repays the applicable Overpayment directly to the CMS contractor, then Practitioner is not required by this Section III.G to submit the Reportable Event to CMS through the SRDP.
Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.
Notification of Delay The Design Professional shall immediately notify the City in writing if Design Professional experiences or anticipates experiencing a delay in performing the Professional Services within the time frames set forth in the Task Order. The written notice shall include an explanation of the cause for, and a reasonable estimate of the length of, the delay. If in the opinion of the City, the delay affects a material part of the Task, the City may exercise its rights under Sections 2.5-2.7 of this Agreement.
Notice of Possible Withholding Under FATCA The Issuer shall notify each Agent in the event that it determines that any payment to be made by an Agent under the Notes is a payment which could be subject to FATCA Withholding if such payment were made to a recipient that is generally unable to receive payments free from FATCA Withholding, and the extent to which the relevant payment is so treated, provided, however, that the Issuer’s obligation under this Clause 7.1.6 shall apply only to the extent that such payments are so treated by virtue of characteristics of the Issuer, the Notes, or both.
Definition of Reportable Event For purposes of this CIA, a “Reportable Event” means anything that involves:
Return or Destruction of PHI At termination of this Agreement, Business Associate hereby agrees to return or destroy all PHI provided by or obtained on behalf of Covered Entity. Business Associate agrees not to retain any copies of the PHI after termination of this Agreement. If return or destruction of the PHI is not feasible, Business Associate agrees to extend the protections of this Agreement to limit any further use or disclosure until such time as the PHI may be returned or destroyed. If Business Associate elects to destroy the PHI, it shall certify to Covered Entity that the PHI has been destroyed.
Notification of Non-Compliance If Seller is unable to comply with the obligations stated in this Section, Seller shall promptly notify Apple, and Apple may take any one or more of the following actions: (i) suspend the transfer of Confidential Data to Seller; (ii) require Seller to cease processing Confidential Data; (iii) demand the secure return or destruction of Confidential Data; and/or (iv) immediately terminate this Agreement.
Reportable Events No such Employee Benefit Plan which is an Employee Pension Benefit Plan has been completely or partially terminated or been the subject of a Reportable Event as to which notices would be required to be filed with the PBGC. No proceeding by the PBGC to terminate any such Employee Pension Benefit Plan has been instituted or threatened; and
Notification of Force Majeure Event 11.5.1 The Affected Party shall give notice to the other Party of any event of Force Majeure as soon as reasonably practicable, but not later than seven (7) days after the date on which such Party knew or should reasonably have known of the commencement of the event of Force Majeure. If an event of Force Majeure results in a breakdown of communications rendering it unreasonable to give notice within the applicable time limit specified herein, then the Party claiming Force Majeure shall give such notice as soon as reasonably practicable after reinstatement of communications, but not later than one (1) day after such reinstatement. Provided that such notice shall be a pre-condition to the Affected Party’s entitlement to claim relief under this Agreement. Such notice shall include full particulars of the event of Force Majeure, its effects on the Party claiming relief and the remedial measures proposed. The Affected Party shall give the other Party regular (and not less than monthly) reports on the progress of those remedial measures and such other information as the other Party may reasonably request about the Force Majeure Event.
