CRM for Health Plans: Building a Member Engagement System

A health plan's CRM is organized around the member for as long as they stay with the plan. What the member record should show, which communications run on federal deadlines, when a member message counts as HIPAA marketing, and how Star Ratings and the CMS interoperability rule change what service teams need to see.

In short

  • A CRM for a health plan is a member engagement system: one view of each member across enrollment, onboarding, service, care programs and renewal, fed by the plan's core administration, claims and care management systems.
  • Much of its work runs on federal deadlines, such as the Annual Notice of Change by September 30 and the Evidence of Coverage by October 15 for Medicare Advantage members, and on HIPAA rules that decide which member messages count as marketing.
  • CMS's interoperability and prior authorization rule adds prior authorization decision timeframes from 2026 and new APIs by January 1, 2027, so service teams need prior authorization status and data-sharing choices in the same member view.

A CRM for a health plan should give every person who talks to a member the same complete picture: which plan they are in and since when, their primary care physician, every recent contact with the plan, open service cases, prior authorization requests and their status, care programs they are part of, the documents the plan has sent, and the member's communication choices. It is a member engagement system, and three things set it apart from a sales CRM: the member is the unit, most data comes from systems the CRM does not own, and much of the outreach runs on federal deadlines and HIPAA rules. The rest is ordinary CRM work.

How is a health plan CRM different from an agent CRM?

An agent or broker CRM follows a person from lead to enrollment. Its main records are leads, appointments and applications, and its main rules are Medicare marketing rules on contact and Scope of Appointment, covered in our CRM requirements article. A plan's CRM starts where that one ends, at enrollment, and stays with the member for years.

  • System of record: enrollment, eligibility and claims live in the core administration and claims systems. The CRM reads them and should not become a second copy that drifts.
  • Users: member services, care managers, outreach teams, sometimes provider relations, and sales.
  • Channels: phone, portal, app, mail, email and text, all in one timeline.
  • Scale: every member, every year, instead of only the people in a sales pipeline.

What should the member record show?

  • Plan, product line, effective date and the enrollment period used, read from the enrollment system.
  • Primary care physician and care team, if the plan assigns one.
  • A timeline of every contact: calls with their reason codes, portal messages, mailed and emailed documents, outreach attempts and their results.
  • Open cases, such as grievances, billing questions or provider searches, with owners and due dates.
  • Prior authorization requests with their status and decision dates.
  • Care management or wellness programs the member is enrolled in, and the care manager assigned.
  • Communication preferences and opt-outs per channel, and the member's choices on data sharing.

Role-based views matter more here than in a sales CRM. A member services agent needs plan and case detail. A care manager needs clinical program data. An outreach team running a campaign may need only contact details and eligibility. Limit each role to what it needs, under the HIPAA minimum necessary standard, and show health detail only where the job requires it.

Which communications run on a federal deadline?

For Medicare Advantage, 42 CFR 422.2267 sets required materials and when members must get them:

  • Annual Notice of Change: sent for current enrollees to receive by September 30 each year, with a shorter window for members whose coverage starts October 1, November 1 or December 1.
  • Evidence of Coverage: current enrollees receive it by October 15 of the year before the coverage year. New enrollees get it within 10 calendar days of CMS confirming their enrollment, or by the last day of the month before coverage starts, whichever is later.
  • Summary of Benefits: provided with an enrollment form, available before an online enrollment is submitted, and pointed to during phone enrollment.
  • Star Ratings document: provided with the enrollment form, and updated ratings may be used only after CMS releases them on Medicare Plan Finder.

42 CFR 422.2264 adds that plans must tell every beneficiary they contact, at least once a year and in writing, that they can opt out of future calls about plan business. The CRM should treat each of these as a tracked obligation per member: what was due, when it was sent, by which channel, and whether it came back undelivered. A missed document then shows up as a list of members before an audit finds it.

When does a member message count as marketing?

HIPAA defines marketing in 45 CFR 164.501 as a communication about a product or service that encourages the recipient to buy or use it. Under 164.508(a)(3), using or disclosing PHI for marketing needs the individual's authorization, apart from face-to-face communications and promotional gifts of nominal value. Several kinds of plan communication fall outside the definition, as long as the plan is not paid by a third party to send them:

  • Communications about health-related products or services the plan provides or includes in its plan of benefits, including the plan's network, replacements of or enhancements to a health plan, and add-on benefits available only to enrollees.
  • Communications for treatment, including case management or care coordination, or recommending alternative treatments, providers or settings.
  • Case management and care coordination contacts, and contacts about treatment alternatives.
  • Refill reminders about a drug the member is currently prescribed, if any payment the plan receives is reasonably related to the cost of sending them.

For the CRM, give every campaign a HIPAA category before it can run: plan benefit communication, care coordination, refill reminder, or marketing. Store who chose the category and why. Block campaigns tagged as marketing from using health fields in their audience unless an authorization is on file for each member, and flag any campaign paid for by a third party for review.

How do Star Ratings affect member engagement?

Medicare uses ratings from 1 to 5 stars to help people compare plans on quality and performance, according to the Medicare & You 2027 handbook. The handbook also describes a 5-star Special Enrollment Period: from December 8 to November 30 of the following year, a person can use it once to switch to a Medicare Advantage Plan, drug plan or cost plan with a 5-star rating in their area.

That has two consequences for the CRM. A 5-star plan can receive enrollments almost all year, so onboarding workflows cannot be built only for January. A plan with a lower rating can lose members to a 5-star plan outside the usual enrollment windows, so disenrollment reasons and early warning signs, such as repeated complaints or unresolved cases, belong on the member view and in retention reports. Keep the rating itself as data by plan and year, and update the Star Ratings document only after CMS publishes new ratings on Plan Finder.

What does the CMS interoperability rule add?

CMS's Interoperability and Prior Authorization final rule, CMS-0057-F, applies to impacted payers: Medicare Advantage organizations, Medicaid and CHIP programs and managed care entities, and qualified health plan issuers on the Federally Facilitated Exchanges. According to CMS's fact sheet:

  • Prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard requests, for impacted payers other than QHP issuers on the Exchanges. Operational provisions generally begin January 1, 2026.
  • Prior authorization metrics posted publicly on the payer's website each year, with the first set due by March 31, 2026.
  • Prior authorization information, excluding drugs, added to the Patient Access API by January 1, 2027, and annual Patient Access API usage metrics reported to CMS from 2026.
  • A Provider Access API for in-network providers with a treatment relationship, and a Payer-to-Payer API with an opt-in process for patients, both by January 1, 2027.

These APIs live outside the CRM, but members call the plan about the same data. If a member can see a prior authorization decision in an app, the service agent on the phone needs the same status and dates. Show prior authorization requests with their decision deadline on the member view, store each member's Payer-to-Payer opt-in choice where agents can see and change it, and read all of it from the same source the APIs use, so the two never disagree.

Should a health plan build, buy or extend its CRM?

The choice turns on three questions. How many people will use it? If member services, care management and outreach all need access, a per-seat price multiplies fast. How far are your workflows from the product's defaults? Deadlines, HIPAA categories and prior authorization views may each need custom work. And where should member data live? If the answer is your own infrastructure, a packaged SaaS CRM may not fit.

Whichever way you go, design the integration with the core administration and claims systems first, because the member view depends on their data. If you buy, check that every feature and connector you plan to use is covered by the vendor's BAA. If you build, budget for maintenance every year. One reference point: the custom CRM we built for a California health insurer was delivered by a team of 5 specialists in 6 months, and instead of monthly fees for a third-party CRM, the company made a one-time payment and pays only for hosting and maintenance.

We sign a BAA before anyone on our team sees PHI, and we run a penetration test before launch. If you add an AI assistant for service agents, the AI assistants we build cite their sources, and run on Claude via AWS Bedrock or Anthropic directly.

Planning a member engagement CRM?

Talk to an engineer at Onix Health about your members, your systems of record and your deadlines. Onix Systems has built software since 2000 and has 370+ engineers. Our free five-day technical audit ends with a written report on your current CRM and its integrations.