Requirements for Network Adequacy Sample Clauses

Requirements for Network Adequacy. State Medicaid standards shall be utilized for LTSS, behavioral health services where Medicare is not primary, and prescription drugs that Medicaid covers and are excluded from Medicare Part D, and Medicare standards shall be utilized for Medicare prescription drugs and for other services for which Medicare is primary. Home health and durable medical equipment requirements, as well as any other services for which Medicaid and Medicare may overlap, shall be subject to State Medicaid standards, so long as the State can show that such standards are at least as stringent and beneficiary friendly as Medicare standards.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Requirements for Network Adequacy. State Medicaid standards shall be utilized for LTSS, as described below, or for other services for which Medicaid is exclusive, and Medicare standards shall be utilized for Medicare prescription drugs and for other services for which Medicare is primary, unless applicable Medicaid standards for such services are more stringent. Home health and durable medical equipment requirements, as well as any other services for which Medicaid and Medicare may overlap, shall be subject to State Medicaid standards, so long as the State can show that such standards are at least as stringent and Enrollee friendly as Medicare standards. MMIPs must pay Enrollees’ current service providers for at least the first 90 days of enrollment, as described in Section V.F below. MMIP must provide and arrange for timely access to all medically-necessary services covered by Medicaid, including those under the HCBS waiver. Both the State and the CMS will monitor access to services through survey, utilization, and complaints data to assess needs to MMIPs network corrective actions. In addition to these protections, minimum LTSS standards for MMIPs are stated below. CMS and the State will also monitor access to care and the prevalence of needs indicated through Enrollee assessments, and based on those findings, may require that the MMIPs initiate further network expansion over the course of the Demonstration
Sample 1

Related to Requirements for Network Adequacy

  • Standards for Network Elements 1.8.1 BellSouth shall comply with the requirements set forth in the technical references, as well as any performance or other requirements identified in this Agreement, to the extent that they are consistent with the greater of BellSouth’s actual performance or applicable industry standards.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

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

  • Cost Responsibility for Network Upgrades 9 5.1 Applicability 9 5.2 Network Upgrades 9

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Changes to the Department's Requirements 5.1 The Department shall notify the Contractor of any material change to the Department's requirement under this Contract.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Customer Requirements ▪ Seller shall comply with the applicable terms and conditions of any agreements between Buyer and Xxxxx’s Customer (the “Customer Purchase Orders”) pursuant to which Buyer agreed to sell to Buyer’s Customer products or assemblies which incorporate the goods provided by Seller hereunder. This provision specifically includes costs and obligations imposed by warranty programs instituted by the original equipment manufacturer that ultimately purchases Buyer’s products that incorporate the goods sold by Seller if applicable to Buyer under the terms of the Customer Purchase Order. ▪ If Buyer is not acting as a Tier One supplier, the defined term “Customer Purchase Order” shall also include the terms and conditions of the original equipment manufacturer that ultimately purchases Buyer’s product that incorporates the goods or services sold by Seller. ▪ Seller will be responsible to ascertain how the disclosed terms affect Seller’s performance under the Purchase Order. ▪ By written notice to Seller, Buyer may elect to disclose and have the provisions of the Customer’s Purchase Orders prevail over any term of the Purchase Order at any time.

  • Maintenance Standards Unless otherwise authorized by the CRC Board, the General Manager shall prepare and submit to the CRC Board proposals (including the Program Maintenance plan submitted pursuant to Section 5(b)) for the performance of such Routine Maintenance and Program Maintenance as is reasonably necessary to keep and maintain the Shared Assets substantially in their condition as of the date of this Agreement. If the CRC Board fails either to approve or disapprove by majority vote any such proposal within 45 days after it was submitted to the CRC Board, the disagreement over the propriety or need for any of the Routine Maintenance or Program Maintenance included in such proposal may be submitted by either Operator for resolution by binding arbitration pursuant to Section 13.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

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