PROVIDER PANEL REQUIREMENTS Sample Clauses

PROVIDER PANEL REQUIREMENTS. The provider network criteria that must be met by each MCP are as follows:
AutoNDA by SimpleDocs
PROVIDER PANEL REQUIREMENTS. Failure to contract with, and properly report to the provider network management (PNM) system, all MCOP contracted providers will result in sanctions as outlined in Appendix N. ODM will grant an ‘exception to the issuance of sanction’ only when an action taken by ODM has adversely impacted a plan’s ability to meet the provider panel network or when a provider is not available in the required zip code, county, and/or region.
PROVIDER PANEL REQUIREMENTS. The provider network criteria that must be met by each MCP are as follows: a. Primary Care Providers (PCPs) 1. Acceptable specialty types for PCPs include family/general practice, internal medicine, pediatrics, and obstetrics/gynecology (OB/GYN). Acceptable PCCs include FQHCs, RHCs and the acceptable group practices/clinics specified by ODJFS. As part of their subcontract with an MCP, PCPs must stipulate the total Medicaid member capacity that they can ensure for that individual MCP. Each PCP must have the capacity and agree to serve at least 50 Medicaid members at each practice site in order to be approved by ODJFS as a PCP. The Appendix H Aged, Blind or Disabled (ABD) population Page 3 capacity-by-site requirement must be met for all ODJFS-approved PCPs. ODJFS reviews the capacity totals for each PCP to determine if they appear excessive. ODJFS reserves the right to request clarification from an MCP for any PCP whose total stated capacity for all MCP networks added together exceeds 2000 Medicaid members (i.e., 1 FTE). ODJFS may allow up to an additional 750 member capacity for each nurse practitioner or physician’s assistant that is used to provide clinical support for a PCP. For PCPs contracting with more than one MCP, the MCP must ensure that the capacity figure stated by the PCP in their subcontract reflects only the capacity the PCP intends to provide for that one MCP. ODJFS utilizes each approved PCP’s capacity figure to determine if an MCP meets the provider panel requirements and this stated capacity figure does not prohibit a PCP from actually having a caseload that exceeds the capacity figure indicated in their subcontract. ODJFS expects that MCPs will need to utilize specialty physicians to serve as PCPs for some special needs members. In these situations it will not be necessary for the MCP to submit these specialists to the PVS database, or other system, as PCPs, however, they must be submitted to PVS, or other system, as the appropriate required provider type. Also, in some situations (e.g., continuity of care) a PCP may only want to serve a very small number of members for an MCP. In these situations it will not be necessary for the MCP to submit these PCPs to ODJFS for prior approval. These PCPs will not be included in the ODJFS PVS database, or other system and therefore may not appear as PCPs in the MCP’s provider directory. These PCPs will, however, need to execute a subcontract with the MCP which includes the appropriate Model Medicaid...
PROVIDER PANEL REQUIREMENTS. The provider network criteria that must be met by each MCP are as follows: a. Primary Care Physicians (PCPs)
PROVIDER PANEL REQUIREMENTS. Failure to contract with, and properly report to the MCPN, the minimum necessary panel will result in sanctions as outlined in Appendix N. ODM will grant an ‘exception to the issuance of sanction’ only when an action taken by ODM has adversely impacted a plan’s ability to meet the provider panel network or when a provider is not available in the required zip code, county, and/or region. a. All MCOPs must provide all medically-necessary Medicaid-covered services to their members. MCOPs must ensure that all network providers follow community standards in the scheduling of routine appointments (i.e., the amount of time members must wait from the time of their request to the first available time when the visit can occur). b. The MCOP must comply with all provider network requirements set forth in the Three-Way and the provider network requirements included as part of this appendix except as explicitly noted herein. i. Certified Nurse Midwives (CNMs) and Certified Nurse Practitioners (CNPs). The MCOP must ensure access to CNM and CNP services in the region if such provider types are present within the region. The MCOP may contract directly with the CNM or CNP providers, or with a physician or other provider entity which is able to obligate the participation of a CNM or CNP. If an MCOP does not contract for CNM or CNP services and such providers are present within the region, the MCOP will be required to allow members to receive CNM or CNP services outside of the MCOP’s provider network. ii. Vision Care Providers. MCOPs must contract with at least the minimum number of ophthalmologists and optometrists for each specified county and region, all of whom must maintain a full-time practice at a site(s) located in the specified county and region to count toward minimum panel requirements. All ODM-approved vision providers must regularly perform routine eye exams. MCOPs will be expected to contract with an adequate number of ophthalmologists as part of its overall provider panel, but only ophthalmologists who regularly perform routine eye exams can be used to meet the vision care provider panel requirement. If optical dispensing is not sufficiently available in a region through the MCOP’s contracting ophthalmologists/optometrists, the MCOP must separately contract with an adequate number of optical dispensers located in the region. iii. Dental Care Providers. MCOPs must contract with at least the minimum number of dentists. iv. Waiver Providers. The MCOP shall ensure ...
PROVIDER PANEL REQUIREMENTS. The provider network criteria that shall be met by the MCP is as follows: a. Primary Care Providers (PCPs). PCP means an individual physician (M.D. or D.O.), certain physician group practice/clinic (Primary Care Clinics [PCCs]), physician assistants, or an advanced practice registered nurse (APRN) as defined in ORC section 4723.43 or advanced practice nurse group practice within an acceptable specialty, contracting with the MCP to provide services as specified in OAC rule 5160-26-03. 1. Acceptable specialty types for PCPs include family/general practice, internal medicine, and pediatrics. Acceptable PCCs include FQHCs, RHCs, and the acceptable group practices/clinics specified by ODM. In order for the PCP to count toward minimum provider panel requirement, as part of the MCP’s subcontract with a PCP, the MCP shall ensure the total Medicaid member capacity is not greater than 2,000 for that individual PCP. The PCP capacity for a county is the total amount of members that all of the PCPs in the MCP agree to serve in that county. ODM will determine the PCP capacity based on information submitted by the MCP through the MCPN. The PCP capacity shall exceed by at least 5% the total number of members enrolled in the MCP during the preceding month in the same county. ODM will determine the MCP’s compliance with the PCP capacity requirement each quarter using the ODM enrollment report for the previous month. For example, in April, ODM will review the MCP’s countable PCP capacity using one of the April MCPN reports. The countable capacity will be compared to the finalized enrollment report for March. ODM recognizes that some members needing specialized care will use specialty providers as PCPs. In these cases, the MCP will submit the specialist to the MCPN database as a PCP. However, the specialist serving as a PCP will not count toward minimum provider panel PCP requirements, even though they are coded as a PCP. Also, in some situations (e.g., continuity of care) a PCP may only want to serve a very small number of members for the MCP. These PCPs will, however, need to execute a subcontract with the MCP which includes the appropriate Model Medicaid Addendum. In addition to the PCP capacity requirement, the MCP shall also contract with the specified number of pediatric PCPs for each region. These pediatric PCPs will have their stated capacity counted toward the PCP capacity requirement. A pediatric PCP shall maintain a general pediatric practice (e.g., a pediatric neu...
PROVIDER PANEL REQUIREMENTS a) PROVIDER shall specify a capacity of members he/she is willing to accept under this Agreement; the maximum capacity is two thousand five hundred (2,500) for each full-time physician in the PROVIDER group; for each full-time physician assistant or advanced registered nurse practitioner in the PROVIDER group, the maximum is one thousand two hundred fifty (1,250); for each medical resident in the PROVIDER group, enrollment shall not exceed eight hundred seventy-five (875) members. If PROVIDER has both Choice and IO panels, PROVIDER shall not exceed these capacities for both panels combined. b) OHCA does not guarantee PROVIDER an enrollment level nor will OHCA pay for members who are not eligible or excluded from enrollment. c) PROVIDER may request a change in his/her capacity by submitting a written request signed by authorized representative of PROVIDER group. This request is subject to review according to program standards. In the event PROVIDER requests a lower capacity, OHCA may lower the capacity by dis-enrolling members to achieve that number or allowing the capacity to adjust as members change their PCP/CM or lose eligibility; d) Unless approved by OHCA, PROVIDER must accept members in the order in which they apply without restriction up to the capacity established by this Agreement. PROVIDER may not refuse an assignment or will not discriminate against members on the basis of health status or need for health care services. PROVIDER will not use any policy or practice that has the effect of discriminating on the basis of race, color, or national origin, unless superseded by another Federal statute. e) PROVIDER shall provide medically necessary health care for any member who has selected or been assigned to PROVIDER’s panel until OHCA officially reassigns the member. PROVIDER shall not notify the member of a change of PCP/CM until PROVIDER has received notification from OHCA; f) PROVIDER may request that OHCA disenroll a member for cause. OHCA will give written notice of the disenrollment request to the member. If OHCA approves a disenrollment request for a Choice member, OHCA will enroll the member in SoonerCare Traditional for a period not to exceed six months. During this period, PROVIDER must continue to provide services to the member as necessary for continuity of care.
AutoNDA by SimpleDocs

Related to PROVIDER PANEL REQUIREMENTS

  • Personnel Requirements a. The CONTRACTOR shall secure, at the CONTRACTOR'S own expense, all personnel required to perform this Contract. b. The CONTRACTOR shall ensure that the CONTRACTOR'S employees or agents are experienced and fully qualified to engage in the activities and perform the services required under this Contract, and that all applicable licensing and operating requirements imposed or required under federal, state, or county law, and all applicable accreditation and other standards of quality generally accepted in the field of the activities of such employees and agents are complied with and satisfied.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.

  • Contractor Requirements The Firm shall be construed, during the entire term of this contract, to be an independent contractor. Nothing in this contract is intended to nor shall be construed to create an employer- employee relationship, or a joint venture relationship. The Firm represents that it is qualified to perform the duties to be performed under this contract and that it has, or will secure, if needed, at its own expense, applicable personnel who are qualified to perform the duties required under this contract. Such personnel shall not be deemed in any way, directly or indirectly, expressly or by implication, to be employees of the District. Any person assigned by the firm to perform the services hereunder shall be the employee or a subcontractor of the Firm, who shall have the sole right to hire and discharge its employee or subcontractors. The Firm or its subcontractors shall pay, when due, all salaries and wages of their employees and accepts exclusive responsibility for the payment of federal income tax, social security, unemployment compensation and any other withholdings that may be required. Neither the Firm, its subcontractors nor their employees are entitled to state retirement or leave benefits. It is further understood that the consideration expressed herein constitutes full and complete compensation for all services and performance hereunder, and that any sum due and payable to the Firm shall be paid as a gross sum with no withholdings or deductions being made by the District for any purpose from said contract sum, except as permitted in paragraphs 16, 17 and 18.

  • Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.

  • Subcontractor Requirements The Supplier must ensure that any subcontract entered into for the purpose of this Agreement contains an equivalent clause granting the rights specified in this clause.

  • Minimum Vendor Legal Requirements Vendor shall remain aware of and comply with this Agreement and all local, state, and federal laws governing the sale of products/services offered by Vendor under this contract. Such applicable laws, ordinances, and policies must be complied with even if not specified herein.

  • Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.

  • Credentialing Requirements Registry Operator, through the facilitation of the CZDA Provider, will request each user to provide it with information sufficient to correctly identify and locate the user. Such user information will include, without limitation, company name, contact name, address, telephone number, facsimile number, email address and IP address.

  • Federal Requirements In the event this Contract is paid in whole or in part from any federal government agency or source, the specific terms, regulations and requirements governing the disbursement of these funds shall be specified herein and become a part of this clause.

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