CRITICAL INCIDENT REPORTING PROVISION Sample Clauses

CRITICAL INCIDENT REPORTING PROVISION. A. The CONTRACTOR shall report and document all major and/or sensitive incidents (“critical incidents”) to the COUNTY pursuant to the procedures and timing outlined below. The COUNTY, in its sole discretion, may require the CONTRACTOR to conduct all necessary follow-up after reporting critical incidents. If there is any doubt about whether an incident should be reported, the default shall be for the CONTRACTOR to report the incident to the COUNTY. Nothing in the section shall be interpreted to compel CONTRACTOR to disclose client information in violation of CONTRACTOR's professional duties to maintain confidentiality as required by federal or state law, grant requirements, or canons governing the practice of law, including under the California Model Rules of Professional Conduct, Business and Professions Code Sections 6068 and 6453, 42 U.S.C.1320d-6 (HIPAA), or the Older Americans Act and California Department on Aging guidelines. B. A “critical incident” generally refers to an unanticipated and unusual event or occurrence which (1) impacts or poses a risk to the health or safety of the participants, if any, and/or CONTRACTOR’s staff; or (2) represents a significant deviation from the standard of care for the participants, if any, served by the CONTRACTOR. Critical incidents include, but are not limited to, the following allegations and/or events: 1. Boundary violation (e.g., inappropriate contact/communication/or other interaction between a service provider and participants, if any, served by the CONTRACTOR). 2. Sexual assault or misconduct. 3. Physical, psychological, or emotional abuse or neglect. 4. Attempted suicide.
AutoNDA by SimpleDocs
CRITICAL INCIDENT REPORTING PROVISION. A. The CONTRACTOR shall report and document all major and/or sensitive incidents (“critical incidents”) to the County pursuant to the procedures and timing outlined below. The County, in its sole discretion, may require the CONTRACTOR to conduct all necessary follow-up after reporting critical incidents. If there is any doubt about whether an incident should be reported, the default shall be for the CONTRACTOR to report the incident to the County. B. A “critical incident” generally refers to an unanticipated and unusual event or occurrence which (1) impacts or poses a risk to the health or safety of the participants, if any, and/or CONTRACTOR’s staff; or (2) represents a significant deviation from the standard of care for the participants, if any, served by the CONTRACTOR. Critical incidents may include, but are not limited to the following allegations and/or events: 1. Boundary violation (e.g., inappropriate contact/communication/or other interaction between a service provider and participants, if any, served by the CONTRACTOR). 2. Sexual assault or misconduct. 3. Physical, psychological, or emotional abuse or neglect. 4. Attempted suicide.

Related to CRITICAL INCIDENT REPORTING PROVISION

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Reporting Provision Within 30 days of signing this Agreement, the District will submit for OCR’s review and approval its chosen accessibility standard.

  • 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 Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Duty to report Force Majeure Event 21.5.1 Upon occurrence of a Force Majeure Event, the Affected Party shall by notice report such occurrence to the other Party forthwith. Any notice pursuant hereto shall include full particulars of: (a) the nature and extent of each Force Majeure Event which is the subject of any claim for relief under this Article 21 with evidence in support thereof; (b) the estimated duration and the effect or probable effect which such Force Majeure Event is having or will have on the Affected Party’s performance of its obligations under this Agreement; (c) the measures which the Affected Party is taking or proposes to take for alleviating the impact of such Force Majeure Event; and (d) any other information relevant to the Affected Party’s claim. 21.5.2 The Affected Party shall not be entitled to any relief for or in respect of a Force Majeure Event unless it shall have notified the other Party of the occurrence of the Force Majeure Event as soon as reasonably practicable, and in any event no later than 10 (ten) days after the Affected Party knew, or ought reasonably to have known, of its occurrence, and shall have given particulars of the probable material effect that the Force Majeure Event is likely to have on the performance of its obligations under this Agreement. 21.5.3 For so long as the Affected Party continues to claim to be materially affected by such Force Majeure Event, it shall provide the other Party with regular (and not less than weekly) reports containing information as required by Clause 21.5.1, and such other information as the other Party may reasonably request the Affected Party to provide.

  • Incident Reporting Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

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