Reimbursement System Changes Sample Clauses

Reimbursement System Changes. In the event of a proposed rule change to the TDAPA or the ESRD PPS Bundled Payment System, the Coordination Committee will [**] revisions to this Agreement, if any, in response to such proposed rule change. Following such [**] by the Coordination Committee, the Parties may [**] for the purpose of entering into a written amendment to this Agreement or such other changes to this Agreement as the Parties may agree. If such proposed rule change is not [**] to the TDAPA or the ESRD PPS Bundled Payment System and the Parties fail to enter into such a written amendment within [**] of issuance of the proposed rule change (unless the Parties agree in writing that no amendment is necessary), (a) if the License is not then in effect, then the License will not go into effect under Section 3.2.1 (Effectiveness) (and the Effective Date will not occur) until the Parties enter into such an amendment, or (b) if the License is then in effect, then Akebia may elect to suspend the License and commence a Suspension Period under Section 3.2.2 (Suspension), which Suspension Period will continue until the Parties enter into such an amendment.
Sample 1
AutoNDA by SimpleDocs

Related to Reimbursement System Changes

  • Program Changes Contractor agrees to inform the County of any alteration in program or service delivery at least thirty (30) days prior to the implementation of the change, or as soon as reasonably feasible.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Residence Life or the Director’s designee.

  • Contractor Changes The Contractor shall notify DAS in writing no later than ten (10) Days from the effective date of any change in: a. its certificate of incorporation or other organizational document; b. more than a controlling interest in the ownership of the Contractor; or c. the individual(s) in charge of the Performance. This change shall not relieve the Contractor of any responsibility for the accuracy and completeness of the Performance. DAS, after receiving written notice by the Contractor of any such change, may require such agreements, releases and other instruments evidencing, to DAS’s satisfaction, that any individuals retiring or otherwise separating from the Contractor have been compensated in full or that provision has been made for compensation in full, for all work performed under terms of the Contract. The Contractor shall deliver such documents to DAS in accordance with the terms of DAS’s written request. DAS may also require, and the Contractor shall deliver, a financial statement showing that solvency of the Contractor is maintained. The death of any Contractor Party, as applicable, shall not release the Contractor from the obligation to Perform under the Contract; the surviving Contractor Parties, as appropriate, must continue to Perform under the Contract until Performance is fully completed.

  • Product Changes Vocera shall have the right, in its absolute discretion, without liability to End User, to update to provide new functionality or otherwise change the design of any Product or to discontinue the manufacture or sale of any Product. Vocera shall notify End User at least 90 days prior to the delivery of any Product which incorporates a change that adversely affects form, fit or function (“Material Change”). Vocera shall also notify End User at least 90 days prior to the discontinuance of manufacture of any Product. Notification will be made as soon as reasonably practical for changes associated with regulatory or health and safety issues.

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification. 2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length. 2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A. 2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties. 2.5.5 Rates for ULM are as set forth in Exhibit A. 2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered. 2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned. 2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition. 2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Maintenance Program LESSEE's Maintenance Program

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

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