HIPAA-Compliant Insurance CRM: How to Handle PHI in a Sales and Service System

An insurance CRM becomes a HIPAA system the moment it holds a member's plan, doctors or medications. From there, your role as covered entity or business associate decides who signs which BAA, the Security Rule sets the safeguards, and Salesforce and HubSpot each limit where PHI can go.

In short

  • Health plans, including Medicare Advantage organizations, are HIPAA covered entities, and the agencies, vendors and subcontractors that handle their PHI are business associates, so an insurance CRM holding member data falls under the Security Rule.
  • A HIPAA-ready CRM starts with a risk analysis, then applies the technical safeguards in 45 CFR 164.312, such as unique user IDs, automatic logoff, encryption and activity review, and limits each role to the minimum PHI it needs.
  • Off-the-shelf CRMs can hold PHI only within the products and features their BAA covers, such as the HIPAA Covered Services Salesforce lists or HubSpot's Enterprise-only Sensitive Data setting, so map every feature your design uses against that list.

An insurance CRM is HIPAA-compliant when the organization running it has done a risk analysis, applied the Security Rule's safeguards to the CRM and everything connected to it, limited each user to the protected health information (PHI) their job needs, and has a business associate agreement (BAA) with every vendor that stores or processes that PHI. No product is compliant on its own. A CRM can only support compliance, and off-the-shelf CRMs do that only inside the products and features their BAA covers.

Does HIPAA apply to an insurance CRM?

Usually, yes. Under 45 CFR 160.103, a health plan is a covered entity, and the definition of health plan lists health insurance issuers, issuers of Medicare supplemental policies and the Medicare Advantage program under Part C. A business associate is a person or company that handles PHI on behalf of a covered entity, for functions that include claims processing, data analysis, utilization review, billing and benefit management. A subcontractor that creates, receives, maintains or transmits PHI for a business associate is a business associate too.

So a plan's own member CRM is a covered entity system. An agency or marketing organization that handles member data for a plan may be a business associate. The CRM vendor and its hosting provider, in turn, are subcontractors. Which role your organization holds depends on your contracts, so settle that with counsel before design starts, because it decides who signs which BAA.

What makes the data PHI is the health context. A name and phone number from a marketing list become health information about an identifiable person once they sit next to a Medicare Beneficiary Identifier, a health plan, a primary care physician and a pharmacy, the fields agents fill in on the custom CRM we built for a California health insurer.

What must the BAA cover?

45 CFR 164.504(e) sets what a business associate contract must contain. The business associate must agree to:

  • Use and disclose PHI only as the contract permits or the law requires.
  • Use appropriate safeguards, including the Security Rule's for electronic PHI.
  • Report any use or disclosure not provided for by the contract, including breaches of unsecured PHI.
  • Make sure subcontractors that handle the PHI agree to the same restrictions.
  • Support the individual's rights of access and amendment, and supply what is needed for an accounting of disclosures.
  • Make its practices, books and records available to the Secretary of HHS.
  • At termination, return or destroy all PHI if feasible, or extend the protections to anything that cannot be destroyed.

For a CRM, the last item deserves a test before you sign: can the vendor export every record, attachment, recording and note, and then prove deletion? We sign a BAA before anyone on our team sees PHI.

Where does a HIPAA-ready CRM start?

With a risk analysis. 45 CFR 164.308 requires an accurate and thorough assessment of the potential risks and vulnerabilities to electronic PHI, then security measures that reduce them to a reasonable and appropriate level. For a CRM, the analysis should list every place PHI goes: the database, file storage, the email tool, the dialer and its recordings, the e-signature service, analytics exports, backups and support tickets. Each of those is either inside a BAA or should not see PHI.

The same section requires procedures to regularly review records of system activity, policies that give each workforce member appropriate access, procedures for ending access when someone leaves, and security awareness training for the whole workforce, including management. If your sales team grows for the enrollment season, removing access at the end of each contract has to be fast and routine.

Which technical safeguards apply to a CRM?

45 CFR 164.312 lists the Security Rule's technical safeguards. Here is how each one lands in a CRM:

  • Unique user identification (required): every agent and manager has their own login. No shared team accounts, including on the dialer.
  • Emergency access procedure (required): a documented way to reach member data if the normal path fails.
  • Automatic logoff (addressable): end idle sessions after a set time. The California insurer's CRM logs users out after 15 idle minutes.
  • Encryption and decryption (addressable): encrypt PHI at rest and in transit, including recordings and attachments.
  • Audit controls: mechanisms that record and examine activity in systems holding PHI, such as who opened, changed or exported a member record.
  • Integrity: protect PHI from improper change or destruction, and be able to show a record was not altered.
  • Person or entity authentication: verify users are who they claim to be. For a CRM used from home and on the road, that usually means multi-factor sign-in.
  • Transmission security: protect PHI sent over networks, including email and integrations with carriers.

Addressable does not mean optional. It means you assess whether the specification is reasonable for your setting and document what you do instead if it is not.

How should access be divided by role?

The minimum necessary standard in 45 CFR 164.514(d) requires covered entities to identify which people or classes of workforce need PHI, which categories they need, and under what conditions, and then limit access to match. Routine disclosures also need standard protocols that limit PHI to what is reasonably necessary.

  • Agents see the accounts assigned to them, not the whole book.
  • Managers see their team's accounts and reports.
  • Marketing sees counts and segments, not health fields.
  • Support and engineering staff work on de-identified or test data unless a specific issue needs real records.
  • Exports of health fields need a named approver and a reason.

The California insurer's CRM applies the principle of least privilege to system users and rotates passwords. Build roles in the data model from day one. Adding them later means auditing every screen and report.

Can the CRM use PHI for marketing?

Only under strict conditions. Under 45 CFR 164.508(a)(3), a covered entity must get the individual's authorization to use or disclose PHI for marketing, except for face-to-face communications and promotional gifts of nominal value. If a third party pays for the marketing, the authorization must say so. Selling PHI also needs an authorization that discloses the payment.

In CRM terms, keep a flag that separates people who have shared health details from prospects who have not, and do not feed health fields into campaign segments without a review of whether the communication is marketing and whether an authorization is on file. Medicare marketing rules add their own consent requirements for calls and texts, covered in our CRM requirements article.

Can you hold PHI in Salesforce or HubSpot?

Both offer a BAA, with limits that shape the design.

Salesforce's BAA restrictions page lists its HIPAA Covered Services, including Health Cloud, Sales Cloud, Service Cloud, Experience Cloud, Marketing Cloud Services and Service Cloud Voice, and requires the service to be included in a signed BAA. The customer must encrypt PHI it transmits, and PHI stored in the services within its control, and must make sure third-party telephony, e-signature services, LLM providers and external data sources it connects meet HIPAA requirements. Some features are excluded, and some services carry extra rules: for example, PHI may not appear in Einstein Bots utterance records, and on Slack, PHI may not appear in profiles, custom statuses, workspace names or user group names.

HubSpot can store PHI only with its Sensitive Data feature, available on Enterprise tiers of its hubs and Smart CRM. A Super Admin turns it on, confirms the account is a HIPAA covered entity or business associate, and accepts the Business Associate Agreement. Each property that holds PHI is marked as containing PHI, and that setting cannot be changed after creation. Sensitive properties are unavailable in personalization tokens, sandboxes, chatbots and playbooks, and calculation, rollup and property sync fields cannot store sensitive data.

With either product, list every feature and connected app in your design and check it against the vendor's page. A single unlisted integration can move PHI outside the BAA.

What about a custom CRM?

A custom build puts every safeguard in your hands, which is both the benefit and the work. The California insurer's CRM runs on the company's private server, records each web lead's consent to process their contact details, and was built by a team of 5 specialists in 6 months. With a custom build you still need a BAA with the hosting provider and any service that touches PHI, a risk analysis, and a maintenance plan for security updates.

Whichever route you take, test it the way an attacker would. We run a penetration test before launch.

Checking PHI handling in your CRM?

Talk to an engineer at Onix Health. Onix Systems has built software since 2000 and has 370+ engineers. Our free five-day technical audit ends with a written report that maps where PHI goes in your CRM and which of those places a BAA covers.