Managed care organizations (MCOs) must maintain a network of service providers that is adequate to meet members’ needs. Adequacy in some cases means that members have access to a particular type of service provider within a specified number of miles, or within a drive of a specified number of minutes. In other cases, in order to ensure adequacy and choice, an MCO is required to contract with every willing provider of a certain type.
Contents – To access the full text, please click each sub-topic.
Overall Network Adequacy
- MCO must have contracts with at least two HCBS providers per country: Florida
- MCO must have contracts with at least two facility-based service providers per county, with at least one licensed bed for each enrollee in applicable enrollment maximum: Florida
- MCO must demonstrate adequacy given consumer needs and enrollment: Wisconsin
- MCO network must be diverse and flexible: Arizona
- Network must be sufficient to assure that care is at least as good as community norms: Arizona
- MCO must ensure covered services are provided promptly and are reasonably accessible in terms of location and hours of operation: Arizona
- MCO must ensure timely and adequate coverage of medically necessary services required under contract through an out-of-network provider when necessary: Arizona
- Services must be as accessible to plan consumers in terms of timeliness, amount, duration and scope as are services provided to non-plan persons within same service area: Arizona
- MCO must offer appropriate range of services and accessible services to meet needs of maximum enrollment level, and maintain sufficient number, mix and geographic distribution of providers, including providers who are accepting new Medicaid patients: Florida
- MCO must establish mechanisms to ensure network providers comply with timely access requirements, monitor regularly to determine compliance, and take corrective action if there is failure to comply: Florida
- MCO must ensure network capacity to serve expected enrollment in service area: Hawaii
- Network adequacy is addressed through array of performance indicators that focus on time measures and provider number, mix and geographic distribution: Kansas
- Consumers must be divided proportionately between plans: Florida
Adequate Network of HCBS Providers
- HCBS are available 7 days a week and for extended hours, as dictated by consumer needs: Florida , Arizona
- MCO must contract with sufficient number of long-term care providers to provide all covered services and ensure that each covered service is provided promptly and is reasonably accessible: Florida
- LTSS subcontracts must not be constructed so as to limit network of providers: Wisconsin
- For residential care facilities, evidence of adequate capacity includes identification of availability of facilities offering private rooms, and process for moving consumer to private room, if desired, when one becomes available: Wisconsin
- Consumers must have access to at least two HCBS service providers: Massachusetts , Tennessee
Adequate Network of Nursing Facilities
- Consumer must have access to at least two nursing facilities: Massachusetts
- MCO must contract with all current nursing facilities that meet CMS certification requirements, for a minimum of 3 years; after that, MCO must contract with a sufficient number of nursing facilities to have adequate capacity: Tennessee
- MCO may not include facility-based service providers from outside region as network providers unless it obtains agency waiver: Florida
Readiness Reviews
- State conducts readiness review to assess MCO’s ability to provide services, including review of MCO’s policies and procedures and corresponding documents, provider network and corresponding provider contracts and subcontracts, walk-through of operations, system demonstrations, and interviews with MCO staff: Florida
- If MCO does not meet readiness review deadlines, MCO will lose initial enrollment of eligible consumers. If problems remain unfixed, contract will be terminated: Florida
- MCO must submit organizational report 60 days before operational start date: Texas
Changes in Network
- Material changes in provider network must be approved by state: Arizona
- MCO must notify state within 7 days of any significant changes to regional network: Florida
- Material change to network is one which affects MCO’s ability to meet performance and network standards in contract, or cause more than 5% of consumers to change where services are received: Arizona , Florida
- MCO requests for approval of network changes must include description of any short-term gaps identified as result of change: Arizona
- Material change in provider network requires 30 days advance written notice to affected consumers: Arizona
- MCO must notify state within one business day of any unexpected changes that would impair provider network: Arizona
- MCO must document compliance with access requirements after any significant change in operations: Florida
- MCO must have procedures to address network changes that negatively affect ability of consumers to access services, including access to culturally diverse provider network: Florida
- MCO must notify consumer if provider is unavailable to continue to provide services within 10 calendar days from date MCO becomes aware of such unavailability: Florida
- If MCO excludes provider, it must provide written notice to affected consumers 30 days before effective date: Florida
Requirement to Contract
- For LTSS benefits involving intimate personal care or regular home visits, MCO must purchase services from consumer’s choice of any qualified provider who will accept and meet subcontractor provisions: Wisconsin
- MCO must contract with community-based residential facility, residential care apartment complex, community rehabilitation program, home health agency, day service provider, personal care provider, or nursing facility to serve as contracted provider if provider agrees to be reimbursed at MCO’s contract rate and meets all guidelines established by MCO: Wisconsin
- MCO must contract with providers of personal assistance services, and day activity and health services: Texas
- If MCO declines to include provider in network, MCO must give affected provider timely written notice of reason: Arizona
Time and Travel Standards
- MCO required to show how many people are within certain distances of providers: Texas
- Transport distance to licensed adult day care must not exceed 20 miles in urban areas, 30 miles in suburban areas, or 60 miles in rural areas: Kansas , Tennessee
- For community-based residential alternatives, MCO must demonstrate good faith efforts to have a travel distance of no more than 60 miles between consumer’s community-based residential alternative placement and his or her residence: Tennessee
- Therapy, facility-based hospice, and adult day health care locations must be within average of 30 minutes from consumer’s residence unless waiver granted; in rural areas, standard increased to 60 minutes for therapy services and adult day health care: Florida
Non-Compete Agreements
- MCO must not prohibit provider from signing with another MCO: Arizona , Texas
- Personal care workers must be free to work for any consumer, or work for any agency: Minnesota
Other
- For certain inappropriate behavior, MCO can place consumer on “Administrative Lock-In” and be limited to one hospital, one pharmacy, and/or one service provider: Kansas
- Pursuant to federal regulation, MCO on request must provide information about any physician incentive plan that may affect referrals: Minnesota
- Fla. Contract, Atch. II, Exh. 7, p. 56. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 59. (back)
- Wis. Contract, pp. 113-15. (back)
- Ariz. Contract, pp. 59-60. (back)
- Ariz. Contract, p. 60. (back)
- Ariz. Contract, p. 60. (back)
- Ariz. Contract, p. 60. (back)
- Ariz. Contract, p. 60. (back)
- Fla. Contract, Atch. II, p. 68. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 60. (back)
- Haw. RFP, p. 76. (back)
- Kan. RFP, p. 44. (back)
- Fla. Contract, Atch. I, pp. 2-3. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 57. (back)
- Ariz. Contract, p. 60. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 55. (back)
- Wis. Contract, p. 101. (back)
- Wis. Contract, p. 114. (back)
- Mass. Contract, p. 41. (back)
- Tenn. Contract, p. 207. (back)
- Mass. Contract, p. 41. (back)
- Tenn. Contract, p. 213. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 60. (back)
- Fla. Contract, Atch. II, p. 41. (back)
- Fla. Contract, Atch. II, p. 41. (back)
- Tex. Contract, p. 7-4. (back)
- Ariz. Contract, p. 66. (back)
- Fla. Contract, Atch. II, p. 71. (back)
- Ariz. Contract, p. 66. (back)
- Fla. Contract, Atch. II, pp. 71-72. (back)
- Ariz. Contract, p. 66. (back)
- Ariz. Contract, p. 66. (back)
- Ariz. Contract, p. 66. (back)
- Fla. Contract, Atch. II, p. 71. (back)
- Fla. Contract, Atch. II, p. 71. (back)
- Fla. Contract, Atch. II, p. 72. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 57. (back)
- Wis. Contract, p. 101. (back)
- Wis. Contract, p. 110. (back)
- Tex. Contract, p. 8-125. (back)
- Ariz. Contract, pp. 61-62. (back)
- Tex. Contract, pp. 4-47 through 4-50. (back)
- Kan. RFP, p. 58. (back)
- Tenn. Contract, p. 469. (back)
- Tenn. Contrct, p. 213. (back)
- Fla. Contract, Atch. II, Exh. 7, p. 59. (back)
- Ariz. Contract, p. 68. (back)
- Tex. Contract, p. 8-28. (back)
- Minn. Contract, p. 138. (back)
- Kan. RFP, p. 80. (back)
- Minn. Contract, p. 225. (back)