Network Disruption Sample Clauses

Network Disruption. (i) Contractor shall implement policies and practices designed (i) to reduce the potential for disruptions in Contractor’s provider networks, and (ii) to minimize the amount of uncertainty, disruption, and inconvenience of Enrollees in the execution of the transition of care as required under State laws, rules and regulations in connection with any such disruption. Contractor agrees to maintain adequate records, reasonably satisfactory to the Exchange, documenting its policies and its compliance with these requirements by Contractor and Participating Providers. (ii) If Contractor experiences provider network disruptions that require a block transfer of Enrollees from a terminated Participating Physician or Participating Hospital to a new Participating Physician or Participating Hospital, Contractor shall provide the Exchange with copies of the written notices the Contractor proposes to send to affected Enrollees, as required under Health and Safety Code 1373.65 prior to mailing to Enrollees. (iii) If Contractor experiences provider network disruptions or other similar circumstances that make it necessary for Enrollees to change QHPs or Participating Providers, Contractor agrees to provide prior notice to the Exchange and Health Insurance Regulator, in accordance with advance notice, meeting, and other requirements set forth in applicable laws, rules and regulations, including, Insurance Code 10199.1 and Health and Safety Code 1367.23 and 1366.1. (iv) In the event of a change in Participating Providers or QHPs under paragraphs (ii) or (iii) above, Contractor shall, and shall require Participating Providers to, cooperate with the Exchange in planning for the orderly transfer of Enrollees as necessary and as required under applicable laws, rules, and regulations including, those relating to continuation of care, including, those set forth at Health and Safety Code Section 1373.95 and Insurance Code 10133.55.
AutoNDA by SimpleDocs
Network Disruption. (i) Contractor shall implement reasonable policies and practices designed (i) to reduce the potential for disruptions in Contractor’s provider networks, and (ii) to minimize the amount of uncertainty, disruption, and inconvenience of Enrollees in the execution of the transition of care as required under State laws, rules and regulations in connection with any such disruption. Contractor agrees to maintain adequate records, reasonably satisfactory to the Exchange, documenting its policies and its compliance with these requirements by Contractor and Participating Providers.
Network Disruption. If the interconnection of Landlord or Resident equipment results in any observable service disruption (including, without limitation, a measurable reduction of service levels, equipment or network malfunctions or failures, or excessive event alarms) and the disruption is caused by or arises from the Landlord or Resident equipment or acts or omissions of the Landlord, then the following apply: (a) If the disruption is not a Service Threatening Disruption, then UC2B will notify Landlord promptly of such disruption and Landlord will have seventy-two (72) hours (or such longer period as may be mutually agreed to by UC2B and Landlord) to eliminate the source of the disruption. If Landlord is unable to eliminate the source of disruption within the required time period, then UC2B may apply any operating procedures then in effect by UC2B to eliminate disruptions of similar nature and Landlord and Resident will (a) cooperate with such efforts, and be responsible for all reasonable out-of-pocket expenses as communicated to Landlord in a timely manner by UC2B, caused by Landlord’s or Resident’s negligence or willful misconduct and actually incurred by UC2B in eliminating the disruption. (b) If the disruption is a Service Threatening Disruption, then UC2B may at any time, without prior notice to Landlord or Resident, take immediate action to eliminate such Service Threatening Disruption. UC2B shall notify Landlord immediately after action is taken and, upon notice, UC2B is entitled to immediate access to the Landlord’s Premises and each Residential Unit. Landlord will provide any assistance reasonably requested by UC2B. In taking such action, UC2B will use its reasonable best efforts to minimize any disruption to Landlord’s operations and will use its reasonable best efforts to restore service to Landlord promptly. Landlord will be responsible for all reasonable out-of-pocket expenses actually incurred by UC2B to resolve any Service Threatening Disruption.
Network Disruption. You are expressly prohibited from any use of the Service or any other action that causes a disruption in the network integrity of SunRocket or its vendors, whether directly or indirectly. SunRocket, in its sole discretion, may terminate your Service without advance notice if it determines you are responsible for such disruptions.
Network Disruption. (i) Contractor shall implement reasonable policies and practices designed (i) to reduce the potential for disruptions in Contractor’s provider networks, and (ii) to minimize the amount of uncertainty, disruption, and inconvenience of Enrollees in the execution of the transition of care as required under State laws, rules and regulations in connection with any such disruption. Contractor agrees to maintain adequate records, reasonably satisfactory to the Exchange, Covered California – Final HealthFinal SADP Plan Contract – May 6August 190, 2013 9 documenting its policies and its compliance with these requirements by Contractor and Participating Providers.

Related to Network Disruption

  • Downtime Each of Zero Hash and ZHLS uses commercially reasonable efforts to provide the Services in a reliable and secure manner. From time to time, interruptions, errors, delays, or other deficiencies in providing the Services may occur due to a variety of factors, some of which are outside of Zero Hash’s and/or ZHLS’ control, and some which may require or result in scheduled maintenance or unscheduled downtime of the Services (collectively, “Downtime”). You understand and acknowledge that part or all of the Services may be unavailable during any such period of Downtime, and you acknowledge that Zero Hash and ZHLS are not liable or responsible to you for any inconvenience or losses to you as a result of Downtime. Following Downtime, you further understand and acknowledge that the prevailing market prices of cryptocurrency may differ significantly from the prices prior to such Downtime.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

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