Oversight Responsibility. The Behavioral Health Administrator or designee, is designated the MCP Responsible Person, listed on Exhibit A of this MOU, is responsible for overseeing MCP’s compliance with this MOU. The MCP Responsible Person must:
i. Meet at least quarterly with DMC-ODS, as required by Section 9 of this MOU;
ii. Report on MCP’s compliance with the MOU to MCP’s compliance officer no less frequently than quarterly. MCP’s compliance officer is responsible for MOU compliance oversight reports as part of MCP’s compliance program and must address any compliance deficiencies in accordance with MCP’s compliance program policies;
iii. Ensure there is sufficient staff at MCP to support compliance with and management of this MOU;
iv. Ensure the appropriate level of MCP leadership (i.e., persons with decision-making authority) are involved in implementation and oversight of the MOU engagements and ensure the appropriate levels of leadership from DMC-ODS are invited to participate in the MOU engagements, as appropriate;
v. Ensure training and education regarding MOU provisions are conducted annually for MCP’s employees responsible for carrying out activities under this MOU, and as applicable for Subcontractors, Downstream Subcontractors, and Network Providers; and
vi. Serve, or may designate a person at MCP to serve, as the MCP- DMC-ODS Liaison, the point of contact and liaison with DMC-ODS. The MCP-DMC- ODS Liaison is listed in Exhibit A of this MOU. MCP must notify DMC-ODS of any changes to the MCP-DMC-ODS Liaison in writing as soon as reasonably practical, but no later than the date of change, and must notify DHCS within five Working Days of the change.
Oversight Responsibility. The designated Agency Responsible Person, listed in Exhibit B of this MOU, is responsible for overseeing Agency’s compliance with this MOU. The Agency Responsible Person serves, or may designate a person to serve, as the designated Agency Liaison, the point of contact and liaison with MCP. The Agency Liaison is listed in Exhibit B of this MOU. Agency must notify MCP of any changes to the Agency Liaison in writing as soon as reasonably practical but no later than the date of change, except when such prior notification is not possible, in which case notice must be provided within five Working Days of the change.
Oversight Responsibility. Producer acknowledges that the Customer shall oversee and monitor Producer’s and all of Producer’s Subcontractors’ providing Services under this Agreement. Accordingly, Customer will regularly review the performance of Producer and, if applicable, Producer’s Subcontractors, as part of its normal operations to confirm ongoing compliance and to ensure any identified corrective actions are undertaken and effective. Producer further acknowledges that the Customer is ultimately responsible to CMS for the performance of such services and that the Customer shall oversee and is accountable to CMS for the functions and responsibilities described in the Medicare Advantage and Medicare Part D regulatory standards and ultimately responsible to CMS for the performance of all services.
Oversight Responsibility. The Behavioral Health Administrator or designee, the designated MCP Responsible Person, listed in Exhibit A, is responsible for overseeing MCP’s compliance with this MOU. The MCP Responsible Person must:
i. Meet at least quarterly with DMC State Plan County, as required by Section 9 of this MOU;
ii. Report on MCP’s compliance with the MOU to MCP’s compliance officer no less frequently than quarterly. MCP’s compliance officer is responsible for MOU compliance oversight reports as part of MCP’s compliance program and must address any compliance deficiencies in accordance with MCP compliance program policies;
iii. Ensure there is sufficient staff at MCP to support compliance with and management of this MOU;
iv. Ensure an appropriate level of MCP leadership (i.e., persons with decision-making authority) are involved in implementation and oversight of the engagements and ensure the appropriate levels of leadership from DMC State Plan County are invited to participate in the MOU engagements, as appropriate;
v. Ensure training and education regarding MOU provisions are conducted annually for MCP’s employees responsible for carrying out activities under this MOU, and as applicable for Subcontractors, Downstream Subcontractors, and Network Providers; and
vi. Serve, or may designate a person at MCP to serve, as the MCP- DMC State Plan County Liaison, the point of contact with DMC State Plan County. The MCP-DMC State Plan County Liaison must be listed in Exhibit A of this MOU. MCP must notify DMC State Plan County of any changes to the MCP-DMC State Plan County Liaison as soon as reasonably practical, but no later than the date of change, and must notify DHCS within five Working Days of the change.
Oversight Responsibility. The CDE will continue to exercise its responsibilities for general supervision including monitoring practices related to transition requirements. This includes the requirement that, if a participating agency other than the LEA fails to provide transition services it agreed to provide in the IEP, the LEA shall reconvene the IEP team to identify alternative strategies to meet the student’s transition service needs. Goal 2, Strategy 4: Develop business partner initiatives. Actions to achieve this strategy include: Phase II Actions
Oversight Responsibility. The Director of Intake and Clinical Services and the Director of Client Services, the designated Regional Center Responsible Person listed in Exhibit B of this MOU, is responsible for overseeing Regional Center’s compliance with this MOU. The Regional Center Responsible Person serves, or may designate a person to serve, as the designated Regional Center Liaison, the point of contact and liaison with MCP. The Regional Center Liaison may also be a Regional Center care coordinator. The Regional Center Liaison is listed in Exhibit B of this MOU. Regional Center must notify MCP of changes to the Regional Center Liaison as soon as reasonably practical but no later than the date of change. • The Regional Center Responsible Person must ensure there is sufficient staff at Regional Center who support compliance with and management of this MOU. • The Regional Center Responsible Person must ensure training and education regarding MOU provisions are conducted annually for Regional Center’s employees. • The Regional Center Liaison must meet MOU compliance requirements, as determined by policies and procedures established by Regional Center, and must report to the Regional Center Responsible Person.
Oversight Responsibility. Representative acknowledges that MCS shall oversee and monitor Representative’s performance of its responsibilities set forth in this Agreement on an ongoing basis and that MCS is ultimately responsible to CMS for the performance of such services. Representative further acknowledges that MCS shall oversee and is accountable to CMS for the functions and responsibilities described in the Medicare Part D regulatory standards and ultimately responsible to CMS for the performance of all services.
Oversight Responsibility. Management, oversight, decision making and responsibility for the school’s business office, business office activities, compliance, reporting and school-level financial activities rests with the Charter Holder. The Charter Holder is responsible for management, decision making and oversight functions, including internal controls, all fiscal activities of the school, and of the business office. These responsibilities include but are not limited to policy, process and procedures development, implementation and ongoing monitoring of fiscal transactions and activities, all financial transactions, payroll transactions, state and federal program compliance, the school’s accounting records and systems, banking accounts, and all documentation related to the foregoing. Charter Holder understands and agrees that it has oversight responsibility and that the Resources and services provided under this Agreement cannot be relied upon to detect accounting errors, detect or prevent fraud, ensure government program compliance, or prevent illegal acts from occurring.
Oversight Responsibility. The [insert title], the designated County Responsible Person, listed in Exhibit B of this MOU, is responsible for overseeing compliance with this MOU. The County Responsible Person serves, or may designate a person to serve, as the designated County Liaison, the point of contact and liaison with MCP. The County Liaison is listed in Exhibit B of this MOU. County may designate one or more liaisons by program or service line. County must notify MCP of changes to the County Liaison as soon as reasonably practical but no later than the date of change. • County must develop and implement MOU compliance policies and procedures, including oversight reports and mechanisms to address barriers to care coordination. • The County Responsible Person must ensure training and education regarding MOU provisions are conducted annually for County’s employees who carry out responsibilities under this MOU, as applicable. • County must ensure Members, and/or their caregivers or legal guardian(s), are provided with information regarding Covered Services, including Medi-Cal for Kids and Teens services, for which they are eligible. County must refer Members to MCP for Medi-Cal for Kids and Teens services and other MCP Covered Services when indicated based on screening findings. If the child or youth indicates a need for mental health or substance use services, Member may be served by MCP and/or County’s MHP in accordance with Section 8(d) of this MOU.]
Oversight Responsibility. The responsibility for overseeing all development on the Xxxxxx Property and ensuring compliance with all applicable development standards shall rest solely with the Developer, whose project engineer shall certify full compliance for installation of all infrastructure constructed in accordance with the Xxxxxx Preliminary Plat Site Construction Plans. The Town agrees that review of any submittals made by Developer will be performed within ninety (90) days and that failure to render a decision within ninety (90) days will constitute an approval of any Developer submission.