We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Critical Incident Reports Sample Clauses

Critical Incident Reports. The CONTRACTOR shall: (a) comply with all state regulations and direction for reporting critical incidents; (b) conduct training and oversight of all applicable providers and subcontractors to ensure compliance with critical incident requirements to the extent that providers/subcontractors have been required to provide copies of incident reports to the CONTRACTOR; (c) develop and implement policies and procedures for Critical Incident Reporting; (d) track, analyze, and report to HSD as required, the reporting definitions, procedures and format identified by HSD in Letter of Direction #2 (December 29, 2008) and Letter of Direction #13 (July 10, 2009), specific to physical health and/or behavioral health visits handled by the PCPs that shall enable HSD to determine potential problem areas, including but not limited to, quality of care, access to care, provider payment timeliness or service delivery issues; (e) utilize the report formats provided by HSD and provide monthly analysis report findings no later than thirty (30) business days after reporting month end; (f) utilize critical indicator monitoring for early identification and interventions of quality of care and/or health and safety issues; (g) analyze the data, including the identification of any significant trends; (h) address any negative trends in the analysis and develop appropriate CQI initiatives. Examples of negative trends may include: increases in grievances related to a specific issue; increases in hospital or nursing facility readmission rates; decreases in health screens or other indicators of performance issues that would benefit from targeted CQI initiatives; (i) follow all due dates and reporting format requirements set forth in the Appendices, unless specifically provided for herein; and (j) conduct annual provider reviews of all Network Providers on data collected by the Network Provider on medication management to identify harmful practices.
Sample 1Sample 2
Critical Incident Reports. Grantee shall write up and submit all critical incidents using the City-provided form within the required timeframe. Critical incidents include, but are not limited to, anytime emergency response are called to the site, a guest or staff person is seriously injured on or near the site, a guest is transported to the hospital, any incident that results in the immediate exit of a guest from the program, overdose/use of Narcan, and damage to the site that results in one or more guests having to be relocated.
Sample 1
Critical Incident Reports. Report the number and percentage of Critical Incident reports received requiring LME intervention, categorized by reason. (Section 1915(c) waiver s only)
Sample 1
Critical Incident Reports. The CONTRACTOR shall report to the County’s Contract Administrator within twenty-four (24) hours any incident where physical injury occurs to any program participant. An initial verbal report will be accepted. The CONTRACTOR shall submit a written report within 24 hours following the verbal report, which outlines the specifics of the incident. The Collection Site CONTRACTOR shall verbally notify the below COUNTY contact person as soon as possible and send the written report by US Mail to Placer County Adult System of Care Attn: Xxx Xxxxx 000 Xxxxx Xxxxx Xx. Xxxxxxxxx, XX 00000 Phone: 000.000.0000 Fax: 000.000.0000
Sample 1
Critical Incident Reports. Grantee shall report critical incidents, as defined in the Critical Incident Policy, to HSH within 72 hours of the incident according to Department policy. Critical incidents shall be reported using the online Critical Incident Report (CIR) form. In addition, critical incidents that involve life endangerment events or major service disruptions should be reported immediately to the HSH program manager. Please refer to the CIR Policy and procedures on the HSH Providers Connect website.
Sample 1
Critical Incident Reports. The CONTRACTOR shall: (a) develop and implement policies and procedures for Critical Incident Reporting; (b) track, analyze, and report to the State as required, those reporting indicators identified by the State, specific to physical health and/or behavioral health visits handled by the PCPs that shall enable the State to determine potential problem areas, including but not limited to, quality of care, access to care, provider payment timeliness or service delivery issues; (c) utilize the report formats provided by the State and provide monthly analysis report findings no later than fifteen (15) business days after reporting month ends; (d) utilize critical indicator monitoring for early identification and interventions of quality of care and/or health and safety issues;. (e) analyze the data, including the identification of any significant trends; (f) address negative trend in the analysis and develop appropriate CQI initiatives. Examples of negative trends may include increases in grievances related to a specific issue; increases in hospital or nursing facility readmission rates; decrease in health screens or other indicators of performance issues that would benefit from targeted CQI initiatives; (g) follow all due dates and reporting format requirements set forth in the Appendices, unless specifically provided for herein; and (h) conduct annual provider reviews of all Network Providers on data collected by the Network Provider on medication management to identify harmful practices.
Sample 1
Critical Incident Reports. Report the number and percentage of Critical Incident reports received requiring MCO intervention, categorized by reason. (Section 1915(c) waiver s only)
Sample 1

Related to Critical Incident Reports

  • 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.

  • Incident Reports Any serious occurrence involving a beneficiary, outside the normal routine of the OTP (see TRICARE Operations Manual (XXX), Chapter 7, Section 4), shall be reported to the referring military providers and/or Military Treatment Facility (MTF)/Enhanced Multi-Service Market (eMSM) referral management office (on behalf of the military provider), and DHA, and/or a designee, as follows: (a) An incident of a life-threatening accident, patient death, patient disappearance, suicide attempt, incident of cruel or abusive treatment, or any equally dangerous situation involving a beneficiary, shall be reported by telephone on the next business day with a full written report within seven days. (b) The incident and the following report shall be documented in the patient’s clinical record. (c) Notification shall be provided, if appropriate, to the parents, legal guardian, or legal authorities.

  • Accident Reports If any of the Equipment is damaged, lost stolen, or destroyed, or if any person is injured or dies, or if any property is damaged as a result of its use, maintenance, or possession, You will promptly notify Us of the occurrence, and will file all necessary accident reports, including those required by law and those required applicable insurers. You, Your employees, and agents will cooperate fully with Us and all insurers providing insurance under this Agreement in the investigation and defense of any claims. You will promptly deliver to Us any documents served or delivered to You, Your employees, or Your agents in connection with any claim or proceeding at law or in equity begun or threatened against You, Us, or both You and Us.

  • 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.

  • 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.

  • 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 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.

  • Accident Reporting 25.1 If You or an Authorised Driver has an Accident or if the Vehicle is stolen You must report the Accident or theft to Us within 24 hours of it occurring and fully complete an Accident/Theft report form. 25.2 If the Vehicle is stolen or if You or an Authorised Driver of the Vehicle has an Accident where: (a) any person is injured; (b) the other party has failed to stop or leaves the scene of the Accident without exchanging names and addresses; or (c) the other party appears to be under the influence of drugs or alcohol, You or the Authorised Driver must also report the theft or Accident to the Police. 25.3 If You or an Authorised Driver has an Accident You and the Authorised Driver must: (a) exchange names and addresses and telephone numbers with the other driver and drivers licence details; (b) take the registration numbers of all vehicles involved; (c) take as many photos as is reasonable showing: (i) the position of the Vehicles before they are moved for towing or salvage; (ii) the Damage to the Vehicle; (iii) the damage to any third party vehicle or property; and (iv) the general area where the Accident occurred, including any road or traffic signs; (d) obtain the names, addresses and phone numbers of all witnesses; (e) not make any admission of fault or promise to pay the other party's claim or release the other party from any liability; (f) forward all third party correspondence or court documents to Us within 7 days of receipt together with a fully completed Accident Report Form (if not already submitted); and (g) co-operate with Us in the prosecution of any legal proceedings that We may institute or defence of any legal proceedings which may be instituted against You or Us as a result of an Accident, including: (i) attending Our lawyer's office; and (ii) any Court hearing.

  • 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.

  • Development Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

Most Referenced Clauses

Most Referenced Definitions