In short
- A health insurance CRM has to hold three kinds of data: the sales record from lead to enrolled member, the compliance evidence Medicare marketing rules require, and the health and plan details that make the record protected health information.
- For Medicare Advantage, the compliance evidence includes contact consent and opt-outs, a Scope of Appointment agreed before each personal marketing appointment, agent licensing and annual training results, and, for third-party marketing organizations, sales call recordings kept for at least six years.
- Write these requirements down as fields, statuses and reports before you choose a product, because each one either fits a CRM's data model or becomes custom work.
A health insurance CRM must hold three things. First, the sales record: every lead, opportunity and enrolled member, with their history. Second, the compliance evidence that Medicare marketing rules require, such as contact consent, Scope of Appointment records, agent licensing and training, and, for third-party marketing organizations, recorded sales calls. Third, the health and plan details agents work with, which make the record protected health information (PHI) under HIPAA. A generic sales CRM covers the first well. The second and third are where the requirements list grows, so write them down as fields, statuses and reports before you compare products.
The rules cited below are the federal Medicare Advantage marketing rules in 42 CFR Part 422, Subpart V, and the HIPAA Security and Privacy Rules. State insurance rules and your contracts with carriers add more. If you sell only commercial or ACA plans, some Medicare items will not apply, but the structure of the list holds.
What does the sales record need?
Start with the stages. One common model moves a person from Lead to Opportunity to Contact, a customer who bought a health plan. We built a custom CRM for a California health insurer on exactly that model, with statuses for contacted, converted and lost, and an account status bar that shows where each account stands. Whatever the stage names, each record needs:
- Source: web form, agent entry, referral, event or purchased list, since the rules on contacting a person depend on how you got their details.
- Assigned agent and manager, with the date of each reassignment.
- A timeline of every interaction: calls, emails, appointments, documents sent and received, and status changes.
- Tasks with due dates and results, so a manager can see overdue follow-ups.
- Documents shared with the person, kept with the account.
- Search and filters by date, status, assignee and source.
The insurance-specific fields come next. In the California CRM, agents enter the Medicare Beneficiary Identifier, healthcare proxy, health plan, primary care physician and pharmacy. Add current coverage, plan effective date, enrollment period used, and the plan's contract and plan IDs if you work with several carriers.
What contact permissions must the CRM track?
42 CFR 422.2264 limits unsolicited contact with Medicare beneficiaries. Plans may contact people by mail and print, and by email if every email has an opt-out. Unsolicited door-to-door visits, approaches in common areas such as parking lots, social media direct messages, and cold calls, robocalls, texts and voicemails are prohibited. Calls are not unsolicited if the beneficiary gave consent or initiated contact.
- Store, per person and per channel, whether consent was given, when, how, and the exact wording they agreed to.
- Record who initiated each contact. A call back to someone who called you is different from a first call.
- Track opt-outs per channel and apply them at once to every dialer, email tool and agent list.
- Flag event attendees separately. The rule treats calls to sales event attendees as unsolicited unless the person gave express permission to be contacted.
- Block lead generation through other lines of business. The rule says plans may not make unsolicited calls about other lines of business as a way to generate Medicare leads.
The same section requires plans to tell everyone they contact, at least once a year and in writing, that they can opt out of future calls about plan business. Record when and how each person got that notice.
What does a Scope of Appointment record need?
Before a personal marketing appointment, the plan or agent must agree on and record the Scope of Appointment with the beneficiary, and in person it must be in writing. The agent may not market health care products beyond the agreed scope, and the documented scope is valid for 12 months from the beneficiary's signature date. Marketing an additional health-related line needs a separate Scope of Appointment. Non-health products such as annuities may not be marketed at all during the appointment.
- The products in scope, the beneficiary's signature date and method, and the computed expiry date 12 months later.
- A link to each appointment it covers, with a check that the appointment date falls before expiry.
- A warning when an agent opens a quote or application for a product outside the recorded scope.
- A report for managers. 42 CFR 422.2274 requires plans to maintain a system to confirm agents complete Scope of Appointment records for all personal marketing appointments.
What must the CRM hold about agents?
42 CFR 422.2274 sets requirements for the agents and brokers who sell plans. They must be licensed and appointed under state law where required, trained and tested every year on Medicare rules and the plan's products, and score 85 percent or higher on all forms of testing. Plans must report terminations to the state where state law requires it, and report to CMS all enrollments made by unlicensed agents and all for-cause terminations.
- Agent profile: license number, states, expiry, carrier appointments and their dates.
- Training and testing records per plan year, with scores.
- A rule that blocks assignment of leads or applications to an agent whose license, appointment or training is missing or expired.
- Termination records with reason and reporting dates.
The same section limits compensation for independent agents. Compensation may be paid only for months the member is enrolled, and plans recover it when a member disenrolls within the first three months. If the CRM feeds commission reports, it needs the member's enrollment and disenrollment dates per plan as well as the closed deal.
What about call recordings and required documents?
If your organization is a third-party marketing organization (TPMO), 42 CFR 422.2274(g) requires marketing and sales calls, including the audio of web-based calls, to be recorded and kept in full for at least six years. The first three years must be audio. Years four to six may be audio or a complete and accurate transcript. TPMOs that generate leads must tell the person their information will go to a licensed agent, and since October 1, 2024, beneficiary data may be shared with another TPMO only with the person's prior express written consent.
- Link each recording to the account, agent and date, and store the retention end date.
- Store which TPMO disclaimer version was read or shown. 42 CFR 422.2267(e)(41) has two versions, depending on whether the TPMO represents every plan in the area.
- Record that the Summary of Benefits was provided with the enrollment form, as 422.2267 requires, and the Star Ratings document with it.
- Record data-sharing consent before any lead goes to another TPMO.
Timing matters too. Under 42 CFR 422.2263, plans may start marketing the next plan year on October 1. Materials that discuss both years must say clearly which year they mean, so tag templates and sent documents with their plan year.
What makes the CRM a PHI system?
Once the CRM holds a member's plan, doctors, pharmacy or health needs, the HIPAA Security Rule applies to it. Its technical safeguards in 45 CFR 164.312 include unique user identification, an emergency access procedure, automatic logoff, encryption, mechanisms to record and examine activity, integrity protection, person authentication and transmission security. The minimum necessary standard in 164.514(d) asks you to identify which roles need which categories of PHI and limit access to that.
The California CRM applied the principle of least privilege to users, rotated passwords and logged users out after 15 idle minutes, and it runs on the company's private server. Our article on HIPAA-compliant insurance CRMs goes deeper into PHI handling, BAAs and vendor coverage.
Which reports should managers get?
- Pipeline: monthly lead and opportunity counts, lead-to-closed and opportunity-to-closed ratios, and AEP and OEP results, as in the California CRM's reports.
- Compliance: appointments without a valid Scope of Appointment, contacts without recorded consent, agents with expiring licenses or missing training.
- Retention: members who disenrolled within three months, by agent and source.
- Recordings: calls missing a recording or past their retention date.
How do you turn this into a product decision?
Put every item above in a spreadsheet with three columns: does the product hold it as standard, can it be configured, or does it need custom work? Then add the cost of each custom item to the license price. The California insurer chose a custom build: a team of 5 specialists delivered it in 6 months, from January to June 2023, and instead of monthly fees for a third-party CRM, the company made a one-time payment and pays only for hosting and maintenance. Our TCO comparison of custom, Salesforce and HubSpot covers the cost side.
Writing your CRM requirements?
Talk to an engineer at Onix Health. Onix Systems has built software since 2000 and has 370+ engineers. We sign a BAA before anyone on our team sees PHI, and our free five-day technical audit ends with a written report that checks your current CRM against this list.
Sources
- 42 CFR 422.2264: beneficiary contact (Cornell LII)
- 42 CFR 422.2274: agent, broker and other third-party requirements (Cornell LII)
- 42 CFR 422.2267: required materials and content (Cornell LII)
- 42 CFR 422.2263: general requirements for marketing (Cornell LII)
- 45 CFR 164.312: HIPAA technical safeguards (Cornell LII)
- 45 CFR 164.514: minimum necessary requirements in (d) (Cornell LII)