In short
- Store each policy as its own record, so a person can have a primary and a secondary policy.
- Show only the insurance company and member ID on the saved policy card. Keep the rest in its own section.
- Run verification from a button, and record the outcome as approved, not approved or pending.
- Send the policy fields to the EMR on admit, and keep plan and clinical details out of marketing systems.
Why a custom insurance widget in Salesforce
Insurance fields on a lead page turn into a long, messy section. A second policy has nowhere to go. The verification result lives in an email. The EMR gets a policy number with a typo.
A Lightning Web Component built for insurance puts policies on cards, runs the verification from the record and keeps the outcome where the next rep will see it.
Several insurance policies per person
- A custom insurance object, related to the lead and the opportunity.
- One record per policy, marked primary or secondary.
- Insurance company, member ID, and subscriber name and relationship when the policy holder is someone else.
- The saved policy card shows the insurance company and member ID. Other fields open in their own section.
Fewer fields on the card means reps read it at a glance. Everything else is one click away.
Run insurance verification from Salesforce
Start from the record
A button on the widget sends the policy to your verification platform, such as VerifyTX, or opens it with single sign-on.
Record the outcome
The result comes back to a verification section on the record: approved, not approved or pending.
Tell the team
An email or notification goes to the right people when a verification comes back.
Show clear errors
If the verification platform returns an error, the widget shows it in a toast that closes on its own.
Talk through your project
A free call about your integration, your CRM or whatever you are stuck on. Honest advice, even if you never hire us. No obligation.
Send insurance details to the EMR
When a lead admits, the EMR needs the same policy. Map the insurance company, member ID, policy number and subscriber fields to the EMR, so admissions staff do not type them twice.
- Test each field with a real record before go-live. A missing insurance ID mapping is easy to miss.
- Map the payment method for the primary subscriber, so self-pay and insured records go through the right way.
- Log sync errors on the record, so a failed push gets fixed.
Keep insurance data where it belongs
- Insurance details are protected health information. Limit field access to the roles that need it.
- Ad platforms get an outcome only, such as "insured lead", sent back as a conversion. No plan, diagnosis or treatment details.
- Put a BAA in place with every vendor that touches the data. We sign BAAs for healthcare work.
Where to start
List the insurance fields your reps fill in today and the ones the EMR needs. That list is the widget. Book a free call and we will design it with you.
Want help with this?
Book a free call about your CRM, integrations or reporting, or map your systems first with our free tech stack diagram builder.