Note for accounts using Sales Records: This article includes a Legacy components section with additional information that applies to your account.
PlanCompare by ConnectureDRX is an online platform that allows agents and brokers to shop, quote, and enroll Medicare beneficiaries. It provides drug pricing and personalized plan options across Medicare Advantage, MAPD, PDP, and Medicare Supplement plans. Visit the PlanCompare website for more details.
With this integration, users can securely transfer Individual Records from AMS+ to PlanCompare for quoting and enrollment. Once an enrollment is completed, the Individual, Carrier Product, and Policy data is sent back to AMS+.
PlanCompare also integrates with Rx Collect, allowing prescription and provider information to be included in the data sent back to AMS+. Learn more about Rx Collect.
Note: There are two versions of this integration — for both a broker and call center site. Both are virtually the same except the call center site may include a call script.
Requirements
For AMS+
Activating the integration
- You must be the Account Owner to activate or deactivate this integration.
- You must also be an Administrator to access the integration's settings:
- You must be logged into AMS+ as an Agency User.
- You must be assigned to a Security Group with the Manage Users permission.
- Once the integration is activated, any Administrator can modify its settings.
Starting quotes
- You must be logged into AMS+ as an Agency User or Agent CRM User.
- To start quotes for Individual Records:
- You must be assigned to a Security Group with the Individual Visible permission.
- If you're an Agent CRM User, you need access to Individual Records assigned to your Accessible Agent, and optionally unassigned records.
- You must be assigned to a Security Group with the Individual Visible permission.
For PlanCompare
Credentials
- Admin access in PlanCompare.
- A PlanCompare Username for every user who needs to use this integration, added by an Administrator. Learn more.
- The API keys and SSO URL for your agency's PlanCompare account, obtained by a PlanCompare admin.
In this article
- Data flow
- Limitations
- Activating the integration
- Setting up the integration
- Starting quotes in AMS+
- Technical documentation
- Troubleshooting
- Legacy components
Data flow
Data moves between AMS+ and PlanCompare in two directions, each triggered independently and on demand rather than continuously or on a set schedule.
- AMS+ to PlanCompare: When you select the Send button on an Individual Record and choose a PlanCompare link, the record's data is sent to PlanCompare for quoting. See what data is sent to PlanCompare.
- PlanCompare to AMS+: After an enrollment is completed in PlanCompare, the enrollment's Individual, Carrier Product, and Policy data is sent back to AMS+ according to the integration's sync settings. See what data is sent to AMS+.
See Starting quotes in AMS+ for the full workflow, and Technical documentation for field-level mapping in both directions.
Limitations
- You can only integrate one PlanCompare site per AMS+ account. If your upline or another agency uses PlanCompare, you cannot leverage or share their site.
- This integration does not send attachments or files, such as a PDF copy of a completed enrollment application, to AMS+. You can manually upload the attachment to the Individual or Policy Record.
Activating the integration (Account Owner)
- Go to My Agency Settings > Third Party Integrations and select either PlanCompare (Broker) or PlanCompare (Call Center).
Select the Add to AgencyBloc… button.
- Enter your Partner ID.
Your Partner ID is a unique identifier from PlanCompare that never changes. Contact the PlanCompare Client Services Team for this info.
- Enter your PlanCompare API keys.
Contact the ConnectureDRX Client Services Team for your API keys.
- Enter your PlanCompare SSO URL.
Contact the PlanCompare Client Services Team for this info. If you need to process enrollments from the previous year, you can enter additional SSO URLs.
- Name the Quoting Menu.
Located on the Individual Record > Details tab, you can use this menu to send AMS+ profiles to PlanCompare's broker site or call center site for quoting.
- Select Save.
You're now ready to set up your integration users. AMS+ users that have a PlanCompare Username can send Individual Records to PlanCompare's broker site or call center site for quoting. If you also want to sync PlanCompare enrollments back to AMS+, continue to Enabling enrollment sync below.
Deactivating the integration
Go to My Agency Settings > Third Party Integrations > PlanCompare and select the Deactivate button in the top-right corner.
Setting up the integration (Administrator)
For a smooth and optimal setup:
- You need to have an account with PlanCompare by ConnectureDRX. This is a separate subscription with PlanCompare that may include additional costs and fees outside of AMS+.
- You need your PlanCompare API keys, SSO URL, and Partner ID. This is a unique link to PlanCompare's login site. Contact the PlanCompare Client Services Team for this info. This URL changes every enrollment period.
- Review your Carriers and Plans/Carrier Products in PlanCompare and AMS+. Their names need to match or the integration could create duplicate Carrier Records and Carrier Products in AMS+. We recommend changing the names in AMS+ to match PlanCompare.
- Some PlanCompare data can be stored in Policy Custom Fields. You may want to create Custom Fields for the Enrollment Confirmation Number and Plan ID.
If you want to sync PlanCompare enrollments to AMS+, continue below.
Enabling enrollment sync
Once you've connected to PlanCompare, select the Sync PlanCompare Enrollments checkbox to enable enrollment syncing. You should now see additional sync settings.
In PlanCompare, an enrollment includes a beneficiary and Medicare plan. In AMS+, a beneficiary is the equivalent of an Individual Record and a plan is the same as a Policy.
| PlanCompare | AMS+ |
|---|---|
| Beneficiary | Individual |
| Plan | Policy (and optionally Carrier Product) |
When PlanCompare sends enrollment data to AMS+, we will take steps to put that data in the right places based on your integration settings. See below for more details.
Individual Records
By default, we will try to match PlanCompare beneficiaries to existing Individual Records. We'll first try to match on Individual ID. If there is no Individual ID in the enrollment data, we'll try to match on First Name, Last Name, and Date of Birth. If we can't find a match, we'll create a new Individual.
Then, we can optionally update all of the Individual's fields with the new info or only the address fields depending on your integration settings.
You can choose what happens in your integration settings. What Individual fields are updated?
Policy Records
By default, we will automatically create a new Policy Record in AMS+ for every PlanCompare plan. What Policy fields are populated?
Also, we will try to match the carrier in a PlanCompare enrollment to a Carrier Record by carrier name. If we can't find a match, we will create a new Carrier Record and associate it with the new Policy Record. The new Carrier Record's name will be the same as the PlanCompare carrier name. If we find a match, we'll associate the existing Carrier Record with the new Policy Record.
Carrier Products
If you choose to bring over Carrier Product data, we will try to match PlanCompare plans to existing Carrier Products by Carrier Product Name. If we can't find a match, we can create a new Carrier Product depending on your Carrier Product Sync settings. What Carrier Product fields are updated?
Before setting up integration users, make sure you have the following:
- Every AMS+ user who is going to use this integration should have their own PlanCompare Username. This allows your AMS+ user to send Individual Records to PlanCompare's broker site or call center site for quoting. The PlanCompare Username is also necessary for mapping the servicing agent to incoming Individuals and Policies via the enrollment sync.
- If you want to assign a servicing agent to incoming Individuals and Policies, you must have at least one Agent Record in your AMS+ account.
Adding PlanCompare Usernames
Once your integration settings have been saved, go to the Users tab. You will see a list of all your AMS+ users.
Here, you can give an AMS+ user the ability to start quotes in AMS+ by adding their PlanCompare Username. This is the username that you use to log in to your PlanCompare account.
Notes:
- If you're quoting with multiple PlanCompare SSO URLs, the AMS+ user must be set up with the same PlanCompare Username on both plan year sites.
- It's ok if an AMS+ user and PlanCompare username don't match exactly. Just make sure the PlanCompare Username is valid and that you're adding it to the right AMS+ user.
- If you create a new username in PlanCompare, it may take a day before it will work in AMS+. Learn more.
You can enter the PlanCompare Usernames one at a time for each AMS+ user or en masse via file upload.
You can also set the servicing agent for Individuals and Policies coming from PlanCompare.
Assigning servicing agents
If you're using the enrollment sync, you will have the option to assign a servicing agent to new Individuals and Policies that are created by this integration.
When PlanCompare sends an enrollment to AMS+, we will look for the PlanCompare Username attached to that enrollment. If we successfully match a PlanCompare Username in AMS+, we'll next look at the associated AMS+ Servicing Agent. This field points to an Agent Record in AMS+.
If there is an AMS+ Servicing Agent, we'll assign it to any new Individuals and Policies.
Starting quotes in AMS+ (Agency User or Agent CRM User)
Sending an Individual Record
- Go to the record and select the Send button.
This displays a dropdown menu with links for each menu label created in your PlanCompare integration settings. Select a PlanCompare link to send the Individual Record to PlanCompare for quoting. See what data is sent to PlanCompare.
- Complete quoting and enrollment in PlanCompare.
When finished, the record's profile and enrollment information will be sent back to AMS+. See what data is sent to AMS+.
The first time you send an Individual Record, the integration creates a new Beneficiary profile in PlanCompare with the sent record's data and ID. Make sure this profile is saved in PlanCompare. The next time you send the same record, the integration matches it to that same Beneficiary profile and updates it with any changes made since the last send.
Note: Data does not sync automatically in either direction. To push updated client data from AMS+ to PlanCompare, resend the Individual Record using the Send button. Data is only pushed from PlanCompare to AMS+ when an enrollment is completed in PlanCompare.
Technical documentation
Note: The integration includes Rx Collect prescription and provider data only for AMS+ accounts on the Accelerate or Elevate subscription packages.
Data sent to PlanCompare
When you send an Individual Record to PlanCompare for quoting, here is the data we send over:
| AMS+ Field | PlanCompare Field |
|---|---|
| Zip Code* | Zip Code |
| First Name | First Name |
| Last Name | Last Name |
| DOB | Date of Birth |
| Medicare Beneficiary ID (MBI) | MBI |
| Medicare Effective Date (Part A) | Hospital (Part A) effective date |
| Medicare Effective Date (Part B) | Hospital (Part B) effective date |
| Email Address | |
| Home Phone** | Phone number |
| Address Line 1*** | Address 1 |
| Address Line 2*** | Address 2 |
| City*** | City |
| State*** | State |
| Prescriptions: Pharmacy Name | Pharmacy Name |
| Prescriptions: Pharmacy Address | Pharmacy Address |
| Prescriptions: Medication Name | Drug Name |
| Prescriptions: Dosage Name | Dosage Name |
| Prescriptions: Quantity | Dosage Quantity |
| Prescriptions: Refill Frequency | Dosage Frequency |
| Providers: Provider | Provider Name |
| Providers: Provider Address | Provider Address |
*If the zip code has trailing spaces, sending the Individual will fail. See Troubleshooting for how to fix this.
**If we don't find the home phone, we'll try the cell phone. If we don't find the cell phone, we'll try the business phone.
***If more than one address is found, we'll use the primary address. Address Line 2 is only sent for Individual Records.
Data sent to AMS+
When PlanCompare syncs enrollments to AMS+, here is the data that comes over:
Individual Records
| PlanCompare Field | AMS+ Field |
|---|---|
| Zip Code | Zip Code |
| First Name | First Name |
| Last Name | Last Name |
| Date of Birth | Date of Birth |
| Email Address | Email Address |
| Phone Number | Home Phone* |
| Address Type** | |
| Primary*** | |
| Address 1 | Address Line 1**** |
| Address 2 | Address Line 2 |
| City | City |
| State | State |
| Username | Servicing Agent***** |
| Part A Effective Date | Medicare Effective Date (Part A) |
| Part B Effective Date | Medicare Effective Date (Part B) |
| Medicare Number or Medicare Claim Number | MBI (Medicare Beneficiary ID) |
| Type | |
| Status | |
| Pharmacy Name | Prescriptions: Pharmacy Name |
| Pharmacy Address | Prescriptions: Pharmacy Address |
| Drug Name | Prescriptions: Medication Name |
| Dosage Name | Prescriptions: Dosage Name |
| Dosage Quantity | Prescriptions: Quantity |
| Dosage Frequency | Prescriptions: Refill Frequency |
| Is Generic Ok?****** | |
| Provider Name | Providers: Doctor Name |
| Provider Address | Providers: Doctor Address |
*If we don't find the home phone, we'll try the cell phone. If we don't find the cell phone, we'll try the business phone.
**When creating/updating an Individual, we'll use the Address Type specified in the integration settings.
***If creating a new Individual, the default will be Yes, is Primary. If adding a new address to an existing Individual, the default will be Yes, is Primary.
****If updating an existing Individual, we'll try to match with an existing address. We will match on Zip Code and house number (house number will be defined as the first set of characters before the first space). If the address matches, we will not update anything. If the address does not match, we will add an additional address to the Individual Record. If creating a new Individual, we will add a new address to the Individual Record.
*****For new Individual Records only. See the Assigning servicing agents section for more.
******The synced value in AMS+ defaults to "Yes" for all dosages.
Only address fields:
| PlanCompare Field | AMS+ Field |
|---|---|
| Address Type* | |
| Primary** | |
| Address 1 | Address Line 1*** |
| Address 2 | Address Line 2 |
| City | City |
| State | State |
| Type | |
| Status |
*When creating/updating an Individual, we'll use the Address Type specified in the integration settings.
**If creating a new Individual, the default will be Yes, is Primary. If adding a new address to an existing Individual, the default will be Yes, is Primary.
***If updating an existing Individual, we'll attempt to match with an existing address. We will match on Zip Code and house number (house number will be defined as the first set of characters before the first space). If the address matches, we will not update anything. If the address does not match, we will add an additional address to the Individual Record. If creating a new Individual, we will add a new address to the Individual Record.
Policy Records
| PlanCompare Field | AMS+ Field |
|---|---|
| Carrier Name | Carrier Name* |
| Enrollment Confirmation Number Note: Typically a temporary number for tracking a Policy until its real policy number is issued. |
Policy Custom Field and/or Policy Number** |
| Premium Per Month | Premium |
| Submission Date | App Submit Date |
| Application Effective Date | Effective Date |
| Username | Servicing Agent*** |
| Status | |
| Plan Type | Coverage Type |
| Plan ID | Policy Custom Field**** |
| Carrier Product***** |
*If Carrier Name does not exist in AMS+, we'll create a new Carrier Record where the Carrier Name = PlanCompare Carrier Name.
**This integration setting is optional. Depending on your settings, we'll attempt to populate the PlanCompare Enrollment Confirmation Number in a Policy Custom Field and/or the Policy Number field.
***See the Assigning servicing agents section for more.
****This integration setting is optional. Depending on your settings, we'll attempt to populate the PlanCompare Plan ID in the specified Policy Custom Field. If no Policy Custom Field is selected, we will not populate the PlanCompare Plan ID.
*****This integration setting is optional. Depending on your settings, we'll attempt to match PlanCompare Plans to Carrier Products in AMS+ by Plan Name or Plan Name + Plan ID. If a match is found, we will associate the Carrier Product with the Policy. If a matching Carrier Product is not found, we can create a new Carrier Product and associate it with the Policy depending on your settings.
Carrier Products
| PlanCompare Field | AMS+ Field |
|---|---|
| Plan Type | Coverage Type* |
| Product Name** |
*We'll look up the corresponding Coverage Type that you've mapped the given Plan Type to. If the specified Coverage Type field option has been deleted or inactivated, we will automatically create that field option and/or make it active in your AMS+ account.
**We'll look up the field "Match PlanCompare Plans to Carrier Products by" from the Sync Setup tab of the integration. If you have selected "PlanName + Plan ID" then Product Name = Plan Name + Plan ID. If you have selected "PlanName" then Product Name = Plan Name.
Note: Does not include attachments or files.
Troubleshooting
Sending an Individual to PlanCompare for quoting fails or the page won't finish loading
This is usually caused by an invalid or outdated PlanCompare Username, or an invalid or outdated PlanCompare SSO URL or Partner ID. PlanCompare changes the SSO URL every enrollment period.
Confirm the AMS+ user's PlanCompare Username is valid, and that your PlanCompare SSO URL and Partner ID are current, then try sending the Individual again.
An Individual's profile fails to load in PlanCompare after being sent
The Individual's zip code has trailing spaces.
Remove any trailing spaces from the zip code, then resend the Individual.
A new PlanCompare Username doesn't work when added to an AMS+ user
New PlanCompare usernames can take up to a day to become active in the integration.
Wait a day, then try adding the username to the AMS+ user again.
Legacy components
The following content applies only to accounts still using Sales Records. If you're unsure whether this applies to you, check your subscription package on the Subscription page. Accounts on Enhanced Records will show a package type that includes "+ Enhanced Records" (e.g., Accelerate + Enhanced Records). If your package does not include "+ Enhanced Records," this section applies to you.
Legacy components in this section:
- Matching criteria for syncing enrollments to Individuals — accounts using Sales Records
- Sending a Sales Record — accounts using Sales Records
- Starting quotes from Sales Opportunities — accounts with Sales Opportunities
- Sales Record permissions — accounts using Sales Records
Matching criteria for syncing enrollments to Individuals
By default, AMS+ attempts to match PlanCompare beneficiaries to existing Sales Records first. If a match is found, the Sales Record is converted into an Individual Record. If the matching Sales Record is linked to an existing Individual, it is merged into that Individual.
If no Sales Record is found, AMS+ attempts to match an existing Individual Record by Individual ID. If there is no Individual ID in the enrollment data, it will try to match on First Name, Last Name, and Date of Birth. If no match is found, a new Individual is created.
Sending a Sales Record
Go to the record and select the Send Quotes button to display a dropdown menu. It will include links for each menu label created in your PlanCompare integration settings.
Select a PlanCompare link to send the Sales Record to PlanCompare for quoting. See what data is sent to PlanCompare.
When finished, the record's profile and enrollment information will be sent back to AMS+. See what data is sent to AMS+.
Starting quotes from Sales Opportunities
You can start quotes from the right-hand summary of Sales Opportunities.
Sales Record permissions
To start quotes for Sales Records, your assigned Security Group must also have the Sales Enablement Visible permission. You must also have user account Sales permissions to View and Edit Sales Records.