Reporting a Reportable Event Sample Clauses

Reporting a Reportable Event. All Reportable Events must be reported to the EOHHS System and Support Desk immediately upon discovery. You can contact the EOHHS System and Support Desk at (000) 000-0000 or at the email addresses available at xxxx://xxxxx- xxx.xxx.xxxx.xxxxx.xx.xx/XX/xxxxxx-xxxxx-xxxxxxxxx.xxx. As time is of the essence during most Security Incidents, managers or Agencies shall not implement administrative processes that delay reporting of a Reportable Event and which may serve to exacerbate a Reportable Event. Examples of such administrative processes are internal programmatic, department and/or Agency reporting requirements and escalation prior to reporting the Reportable Event to the EOHHS System and Support Desk. In some situations, a Reportable Event may constitute a Privacy Incident which is reportable to Agency legal counsel, privacy official or other designated contact under an Agency’s privacy or security policy. In this case, you should report the Reportable Event to both the EOHHS System and Support Desk under this Section XI, Incident Response and Security Incident Response Team and to Agency legal counsel, privacy office or other appropriate official, who will cooperate with the SIRT in their response. In some situations, a Reportable Event may also require contacting emergency services due to an immediate danger (e.g.: dialing 911 for police or fire). In the event a call to emergency services is necessary, notwithstanding the prior statement to call the EOHHS System and Support Desk first, the reporter shall first call emergency services and when the reporter is out of danger, call the EOHHS System and Support Desk. The EOHHS System and Support Desk will then open a “Security Incident” ticket and assign it to the ENT.SEC.CSO queue.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to Reporting a Reportable Event

  • 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

  • Reporting of Reportable Events If Xxxxx determines (after a reasonable opportunity to conduct an appropriate review or investigation of the allegations) through any means that there is a Reportable Event, Xxxxx shall notify OIG, in writing, within 30 days after making the determination that the Reportable Event exists.

  • Definition of Reportable Event For purposes of this CIA, a “Reportable Event” means anything that involves:

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

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Reportable Events under Section III J.1.c. For Reportable Events under Section III.J.1.c, the report to OIG shall include:

  • CERTIFICATION REGARDING DEBARMENT, SUSPENSION, INELIGIBILITY AND VOLUNTARY EXCLUSION This provision is applicable to all Federal-aid construction contracts, design-build contracts, subcontracts, lower-tier subcontracts, purchase orders, lease agreements, consultant contracts or any other covered transaction requiring FHWA approval or that is estimated to cost $25,000 or more – as defined in 2 CFR Parts 180 and 1200.

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

  • Data Reporting 1. Maintain and adhere to data system software and encrypted portable computer device updates, and interface capability requirements for each computer located within the facility, and as specified in the Contract and required by County.

  • CERTIFICATION REGARDING DEBARMENT, SUSPENSION INELIGIBILITY AND VOLUNTARY EXCLUSION This provision is applicable to all Federal-aid construction contracts, design-build contracts, subcontracts, lower-tier subcontracts, purchase orders, lease agreements, consultant contracts or any other covered transaction requiring FHWA approval or that is estimated to cost $25,000 or more - as defined in 2 CFR Parts 180 and 1200. 2 CFR 180.220 and 1200.220.

Time is Money Join Law Insider Premium to draft better contracts faster.