Other incidents Sample Clauses
Other incidents. Vendor will notify NTT promptly if Vendor becomes aware of:
(a) a complaint or a request concerning the exercise of a data subject’s rights under any applicable Data Protection Laws about Personal Data Vendor processes on behalf of NTT and its data subjects; or
(b) an investigation into or seizure of the Personal Data of NTT by government officials, or a specific indication that such an investigation or seizure is imminent; or
(c) where, in the opinion of Vendor, implementing an instruction received from NTT about the processing of Personal Data would violate applicable laws to which NTT or Vendor are subject.
Other incidents. NTT will notify Client promptly if NTT becomes aware of:
(a) complaint or a request with respect to the exercise of a data subject’s rights under any applicable Data Protection Laws in relation to personal data NTT processes on behalf of Client and its data subjects; or
(b) an investigation into or seizure of the personal data by government officials, or a specific indication that such an investigation or seizure is imminent; or
(c) where, in the opinion of NTT, implementing an instruction received from Client in relation to the processing of personal data would violate applicable laws to which Client or NTT are subject.
Other incidents. The following matters or events are classified as Other Incidents:
(a) a serious accident/injury resulting in hospitalisation of a Transferee;
(b) an acute psychiatric hospital admission of a Transferee;
(c) an occurrence of self harm resulting in injury to a Transferee;
(d) an occurrence of attempted self harm by any Transferee;
(e) the voluntary starvation (over 48 hours) of a Transferee;
(f) the end of Voluntary Starvation (three subsequent meals consumed) of a Transferee;
(g) any possible public health risk (including suspected outbreak of an infectious or communicable disease at a Facility), or the identification of a Transferee with an infectious or communicable disease;
(h) an admission to or treatment of a Transferee at a hospital (Note: in addition to the reporting obligations described in clause 9 of Schedule 2 (Statement of Work), for hospital admissions of less than one week duration, daily written reports of the person's condition and other relevant details must be provided to the Department. For hospital admissions exceeding one week duration, weekly written reports must be provided to the Department, unless a significant change is observed in the person, in which case a further written report must be provided to the Department outlining the change in the person's condition, within twenty four (24) hours of the change occurring);
(i) a discharge of a Transferee from hospital;
(j) an identified or suspected torture and trauma sufferer;
(k) the theft or loss of medication or other medical supplies or equipment at a Facility;
(l) the refusal of a Transferee to consent to a Health Induction Assessment, Health Discharge Assessment, or any clinically recommended Health Care, treatment or procedure (other than any refusal required to be reported under clause 2(e) of this Annexure A to Schedule 2 (Statement of Work));
(m) all complaints received from Transferee, and any complaints referred (whether by the Health Services Manager or a Person in Detention) for external investigation; and
(n) any Occupational Health and Safety incidents (as described in the Occupational Health and Safety and Environment Policy and Planning) that occurs at an onsite medical clinic; and
(o) any other event, circumstance, matter or thing that the Health Services Manager reasonably considers should be reported to the Department as an "other incident" under clause 8 of Schedule 2 (Statement of Work). BETWEEN AND [THE MAJOR SUBCONTRACTOR] [INSERT FULL NAME AND ADDRESS] (the 8...
Other incidents. Security Incidents do not include any incident that results in no unauthorized access to Customer Data (as defined in the MSA) or to Khoros’s Applications, websites, or cloud servers involving pings and other broadcast attacks on firewalls or edge servers, phishing (even if successful), port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access beyond headers), or similar incidents not caused by any fault of Khoros. These incidents shall not be considered a breach of this DPA, the MSA, or SLA. Nonetheless, to the extent that a successful phishing attack leads to the compromise of Personal Data, Khoros will work with Customer to fulfil any ADPL reporting requirements.
Other incidents. Security Incidents do not include any incident that results in no unauthorized access, destruction, loss, or alteration to Customer Data or to Khoros’s Services, websites, or cloud servers involving pings and other broadcast attacks on firewalls or edge servers, phishing (even if successful), port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access beyond headers), or similar incidents not caused by any fault of Khoros. These incidents shall not be considered a breach of this DPA, the MSA, or SLA. Nonetheless, to the extent that a successful phishing attack leads to the compromise of Personal Data, Xxxxxx will work with Customer to fulfil any ADPL reporting requirements.
Other incidents. Lost or stolen patient-identifiable information (records, prescriptions). It’s not just accidents and hazards that should be reported. Errors or oversights in practice should also be reported to provide a clear record of what has occurred and how it can be prevented in the future. The incident reporting form should be completed as soon as possible after the event. An incident report should be an objective account of what happened. Ideally the person directly involved in the incident should complete the form, but any pharmacy staff member can do it. A Care Trust incident report form must be completed in addition to any internal reporting procedures within the pharmacy/company. Incident reporting and monitoring should be a supportive process and is not about “blame”.
Other incidents. Maintenance (Scheduled and Urgent) The standard time for scheduled operations (maintenance) is from 21.00 to 06.00 hours on Saturday and Sunday and from 00.00 to 06.00 from Monday to Friday in Estonian time. Table 1. Agreed interruptions and notifications № Position Indicators Notification of the Customer Additional terms 1 Scheduled operations performance The total duration of breaks is not more than 6 hours per year. The intervals between the breaks - not less than 90 calendar days At least 48 hours before the break Time of operations is agreed with the Customer 2 Urgent operations performance The break time is equal to the actual time of work At least 12 hours before the break The estimated duration of operations is reported to the Customer The CONTRACTOR shall inform the CUSTOMER about all the interruptions in the services provision with indication of the time when the service provision will be interrupted, as well as the time of service restoration:
Other incidents. Verizon or Customer can create Other Incident tickets for service related incidents on the Serviced Devices that are not related to an Availability or Health incident. They can be logged on a 24x7 basis.