Incident Reporting Overview Sample Clauses

Incident Reporting Overview. ‌ The e-RB must report security and service incidents as described throughout this document. The e-RB may continue to use their Criminal Justice Secure eMail (CJSM) email account for the sending / receiving of information up to and including “restricted” once they have gone live on the e-Bulk interface. The e-RB will report any compromise or potential compromise to the e-Bulk service as soon as it is identified. In the first instance this should be done by telephone. E-RBs are not permitted to document sensitive information including personal data via non secure e-mail or facsimile. Incidents which occur without warning should be communicated to the first line support helpdesk via telephone. If the e-RB is aware of an incident in advance this must be brought to the attention of the first line support team immediately in writing via email. The e-RB should report the nature of the incident, when it was first discovered, how it happened and how many applications could be potentially impacted including details of the unique reference number(s) and any other details of the application(s). The CRB first line support team will work with the e-RB to resolve the issue. The e-RB should make every effort to provide adequate resource to assist in resolving the issue. Failure to do so may result in the e-RB being disabled from using the e-Bulk service. Please refer to section 2.7. The CRB will report incidents and communicate planned changes to e-RBs either directly to the e-RB via telephone or email where appropriate or as an e-bulletin published on the e-Services section of the CRB website. Incidents will be assessed and where possible a period of notice will be given prior to changes being implemented. Where necessary the CRB reserves the right to revert to the fallback procedure as defined above in section 7.4. It is the responsibility of the e-RB to check the e-Services section of the CRB website regularly for bulletins and updates.
Sample 1
AutoNDA by SimpleDocs

Related to Incident Reporting Overview

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

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

  • Incident Reporting and Client Risk Prevention An incident report shall be created and maintained at the AGENCY for the following: in the event the AGENCY’S staff or subcontractor becomes aware of an occurrence of any incident of injury to a client receiving program services through the COUNTY, requiring medical treatment by a licensed physician; any lawsuit entered into or against the AGENCY, all allegations of any kind of abuse, neglect, or exploitation of the AGENCY’S clients with the exception of those AGENCIES whose primary function is working with those that have been abused, neglected or exploited unless the allegation is against an AGENCY staff member; media coverage relating to the media expressing an interest in a case or issue concerning a client of the AGENCY or an employee on the AGENCY premises, a fire, hostage situation, bomb threat, epidemic or any circumstance which may impact the service provision. All occurrences shall be verbally communicated directly to COUNTY staff no later than 10:00 a.m. the following business day via telephone to the COUNTY. All incident reports shall be made available to the COUNTY upon request and maintained at the AGENCY. These reporting requirements shall in no way supersede the requirements for notification of allegations of abuse/neglect/exploitations to the State of Florida Abuse Hotline, as mandated in Chapter(s) 39 and 415, Florida Statutes.

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

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

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

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.

  • Project Reporting During the course of Implementation Services, the NAVITAIRE Hosted Revenue Accounting Services Project Manager will coordinate status reporting with the NAVITAIRE Hosted Reservation Services Project Manager. Following completion of installation of the Hosted Reservation Services, the NAVITAIRE Hosted Revenue Accounting Services Project Manager will provide Customer with status on the remaining Implementation Services for Hosted Revenue Accounting Services as follows; (a) Weekly Project Plan Update and Status Report; (b) Weekly Updated Issues/Resolution List; and (c) Executive Summary.

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

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