Glossary

Managed Care Organization (MCO)

Definition

A managed care organization (MCO) is a health plan that manages the cost, use and quality of care for its members through a contracted provider network, utilization rules and negotiated payments. Common types include HMOs, PPOs and EPOs, and most states contract with Medicaid MCOs to cover many of their Medicaid enrollees.

An MCO builds a network of providers who agree to serve its members at negotiated rates, and manages how care is used through rules such as referrals and prior authorization.

What types of managed care organizations exist?

  • Health maintenance organizations (HMOs): members use network providers and usually need referrals for specialists
  • Preferred provider organizations (PPOs): more choice of providers, at higher cost
  • Exclusive provider organizations (EPOs): coverage only for network providers, without referral rules
  • Medicaid MCOs: private plans that states pay to manage care for Medicaid members

How do MCOs affect healthcare?

MCOs aim to control costs while keeping care quality up. They do this through negotiated rates, care management, prevention programs and rules on which services need approval. Critics point out that the same rules can delay care and add work for providers.

How do MCOs affect healthcare costs?

By negotiating rates, steering members to network providers and managing the use of expensive services, MCOs try to keep spending predictable. Many also pay providers through value-based contracts that share savings when care costs less.

How do Health IT teams work with MCOs?

MCOs buy care management, utilization management, prior authorization, claims, risk adjustment and member engagement tools. Decision makers include the CMO, the VP of care management, the CIO and network leaders. Because states pay Medicaid MCOs, state contracts and requirements shape what those plans need.

MCO

See where MCO shows up on the accounts you sell to

Search 7.4M+ HCPs and 11M+ executives at 997K+ sites of care, each placed under its health system and IDN.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)