MCO Operations Transition Sample Clauses

MCO Operations Transition. MCO transition is defined as the activities that the MCO is required to perform upon termination or expiration of the Contract in situations where the MCO will transition data and documentation to BMS or a subsequent contractor. For purposes of this provision, "documentation" means all operational, technical, and user manuals used in conjunction with the software, services, and deliverables, in whole or in part, that BMS determines are necessary to view and extract application data in a proper format. The MCO must provide the documentation in the formats in which the documentation exists at the expiration or termination of the Contract. The data, documentation, information, and services provided as detailed in this section must be provided at no additional cost to BMS or a subsequent contractor. BMS or subsequent contractor must receive and verify all relevant data, documentation, and information. If BMS determines that the data, documentation, or information is not accurate, complete, or HIPAA-compliant, BMS reserves the right to hire an independent contractor to assist BMS in obtaining and transferring all the required data and information, and to ensure that all of the data is HIPAA-compliant. The MCO is responsible for the reasonable cost of providing these services. The MCO must maintain a Transition Plan covering the turnover of the program records and information maintained to either BMS or a subsequent contractor. The Transition Plan must be a comprehensive document detailing the proposed schedule, activities, information, and resource requirements associated with the turnover tasks. BMS reserves the right to review the MCO Transition Plan and any significant modifications to the previously approved Transition Plans. BMS reserves the right to provide CMS with Transition Plan documentation upon request. The MCO must transfer to BMS or a subsequent contractor all data and information necessary to transition operations, including: data and reference tables; data entry software; third-party software and modifications; documentation relating to software and interfaces; functional business process flows; and operational information, including correspondence, documentation of ongoing or outstanding issues, operations support documentation, and operational information regarding Subcontractors. In addition, the MCO must provide the following to BMS or a subsequent contractor:  The MCO must provide data, information, and services necessary and sufficient to...
Sample 1Sample 2Sample 3See All (19)
AutoNDA by SimpleDocs
MCO Operations Transition. 41 6.16 Cooperation with Other Contractors and Prospective Contractors 43
Sample 1

Related to MCO Operations Transition

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • Transition Seller will not take any action that is designed or intended to have the effect of discouraging any lessor, licensor, customer, supplier, or other business associate of the Company from maintaining the same business relationships with the Company after the Closing as it maintained with the Company prior to the Closing. The Seller will refer all customer inquiries relating to the business of the Company to the Purchaser from and after the Closing.

  • Indiana Veteran’s Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran’s Business Enterprise (“IVBE”) participation plan. The following IVBE subcontractors will be participating in this Contract: VBE PHONE COMPANY NAME SCOPE OF PRODUCTS and/or SERVICES UTILIZATION DATE PERCENT _____________________________________________________________________________________ _____________________________________________________________________________________ A copy of each subcontractor agreement shall be submitted to IDOA within thirty (30) days of the request. Failure to provide any subcontractor agreement may also be considered a material breach of this Contract. The Contractor must obtain approval from IDOA before changing the IVBE participation plan submitted in connection with this Contract. The Contractor shall report payments made to IVBE subcontractors under this Contract on a monthly basis. Monthly reports shall be made using the online audit tool, commonly referred to as “Pay Audit.” IVBE subcontractor payments shall also be reported to IDOA as reasonably requested and in a format to be determined by IDOA.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • MASTER CONTRACT TRANSITION Contractor represents and warrants that, in the event this Master Contract or a similar contract, is transitioned to another contractor (e.g., Master Contract expiration or termination), Contractor shall use commercially reasonable efforts to assist Enterprise Services for a period of sixty (60) days to effectuate a smooth transition to another contractor to minimize disruption of service and/or costs to the State of Washington.

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

  • Transition Plan In the event of termination by the LHIN pursuant to this section, the LHIN and the HSP will develop a Transition Plan. The HSP agrees that it will take all actions, and provide all information, required by the LHIN to facilitate the transition of the HSP’s clients.

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Max-Tel access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Max-Tel to obtain the technical capability to access and utilize BellSouth’s OSS interfaces. Specifications for Max-Tel ’s access and use of BellSouth’s electronic Version R4Q01: 12/01/01 interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • Community Engagement Integration Activities The SP will support the HSP to engage the community of diverse persons and entities in the area where it provides health services when setting priorities for the delivery of health services and when developing plans for submission to the LHIN including but not limited to CAPS and integration proposals.

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