Carrier connectivity is provided through the Trimble Marketplace.

To learn about pricing and how to get started, go to the Trimble Marketplace website and complete the online form: https://marketplace.trimble.com/integrations/viewpoint-vista/benefit-enrollment.

If you are an existing Trimble Marketplace customer and want to learn more about carrier connectivity, please contact your customer support representative or enter a support ticket at: https://info.trimble.com/en/knowledge/kb-tickets/new.

The Trimble Marketplace integration supports the benefits carriers listed below. New carriers are added to the Trimble Marketplace on an ongoing basis. If you do not see your carrier listed here, please contact Trimble Marketplace to determine if your carrier is supported.

98point6

Aetna

Alerus

BlueCross BlueShield (BC/BS)

Cigna

Delta Dental

Diversified

Empower

EyeMed

Fidelity Investments

Guardian

HealthPartners

iSolved

Kaiser Permanente

MetLife

Optum

Peak One Administration

Pension Consultants Inc.

Primera Blue Cross

Principal

Prudential Life

Regence

Securian Financial

UMR

United Healthcare

United Heritage

VOYA Financial

VSP Vision

WEX

WPS

EDI stands for Electronic Data Interchange.

EDI is an electronic communication method that provides standards for exchanging data via any electronic means. Some insurance carriers accept EDI files and some carriers have APIs. Where a carrier has an API, the integration will build to that API. Where a carrier has an EDI file, the integration will create the file and submit it. EDI file creation and acceptance by the carrier is a longer process than building to an API.

The integration can accommodate delivery requirements for any of your benefits carriers.

The frequency at which EDI files are received is entirely dependent on each carrier.

No. You will receive an email to let you know that the file was submitted, but this email does not include any data sent to carriers as that data contains personally identifiable information (PII).

In certain circumstances, such as when attempting to troubleshoot an issue, you can request the file and the integration will send it via a secure method.

File automation can take two to four months per carrier.

The integration is capable of preparing multiple files for any given carrier. For example, if your implementation calls for five files, you can expect it to take about six months for all files to become operational. As such, we recommend launching this service outside of open enrollment and starting your implementation process approximately nine to twelve months prior to your next open enrollment period.

Yes. We highly recommend that you launch carrier automation outside of open enrollment.

You should also plan to start your implementation process approximately nine to twelve months prior to your next open enrollment period to ensure that data is flowing as expected before open enrollment begins.