Common use of Out-of-State Functions Clause in Contracts

Out-of-State Functions. For functions (e.g., claims processing and service authorizations) that the MCO is not required to have in the state of Ohio, the MCO must maintain a list of the functions and their location. The MCO must notify and obtain ODM’s approval prior to moving functions, whether they are performed inside or outside of the state. The MCO’s notification must occur prior to implementation and include a transition and implementation plan. MCO must bear any additional costs borne by ODM associated with ODM conducted on-site audits or other oversight activities for out-of-state MCO functions.

Out-of-State Functions. 1. For functions (e.g., claims processing and service authorizations) that the MCO is not required to have in the state of Ohio, the MCO must maintain a list of the functions and their location. The MCO must notify and obtain ODM’s 's approval prior to moving functions, whether they are performed inside or outside of the state. The MCO’s 's notification must occur prior to implementation and include a transition and implementation plan. MCO must bear any additional costs borne by ODM associated with ODM conducted on-site audits or other oversight activities for out-of-state MCO functions.