OhioRISE service removals Sample Clauses

OhioRISE service removals. Following the incorporation of the SFY 2021 Experience Adjustment, we modeled the impact of removing expenditures attributable to MMC program services that are anticipated to be covered under the OhioRISE program. This consisted of simulating a methodology for identifying the members and services anticipated to enroll during the first twelve months (July 1, 2022 through June 30, 2023) of the upcoming rating period. The OhioRISE program will include MAGI, ABD, Expansion, and AFK beneficiaries who meet the following criteria. • Enrolled in Ohio Medicaid under either managed care or fee for service; • Under the age of 215; • Not enrolled in the MyCare Ohio program; and, • Meet a functional needs threshold for behavioral health care, as identified by the Child and Adolescent Needs and Strengths (CANS) assessment. For the purpose of the OhioRISE removals, we utilized a proxy population of Medicaid beneficiaries under 21, identified in SFY 2021 via the following process. This methodology was developed based on the provisions in the Ohio Administrative Code (OAC) rules and subsequent conversations with ODM.
Sample 1
AutoNDA by SimpleDocs

Related to OhioRISE service removals

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • SPECIALIZED SERVICE REQUIREMENTS In the event that the Participating Entity requires service or specialized performance requirements not addressed in this Contract (such as e- commerce specifications, specialized delivery requirements, or other specifications and requirements), the Participating Entity and the Supplier may enter into a separate, standalone agreement, apart from this Contract. Sourcewell, including its agents and employees, will not be made a party to a claim for breach of such agreement.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing iNetworks traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices 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 iNetworks, the subtending arrangements between iNetworks Tandems and iNetworks End Offices shall be the same as the Tandem/End Office subtending arrangements that iNetworks maintains for the routing of its own or other carriers’ traffic.

  • Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.

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

  • Maintenance of Services 5.1 Services resold pursuant to this Attachment and BellSouth’s General Subscriber Service Tariff and Private Line Service Tariff and facilities and equipment provided by BellSouth shall be maintained by BellSouth.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Loop Testing/Trouble Reporting 2.1.6.1 TeleConex will be responsible for testing and isolating troubles on the Loops. TeleConex must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, TeleConex will be required to provide the results of the TeleConex test which indicate a problem on the BellSouth provided Loop.

  • SUSPENSION OF SUPPLIER'S APPOINTMENT 27.1 Without prejudice to the Authority's rights to terminate this Framework Agreement as set out in Clause 26 (Termination), or if the Authority reasonably believes that a Consistent Failure has occurred, the Authority may suspend the Supplier's appointment to provide Services to Contracting Bodies under this Framework Agreement by giving notice in writing to the Supplier which notice shall take immediate effect from the date specified in such notice and the Supplier agrees that it shall not be entitled to enter into any new Order during such suspension period.

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