Skip to main content

ISO ClaimSearch

  • Updated

Overview

BriteCore integrates with ISO ClaimSearch (a Verisk product) to help carriers identify potentially related prior claims and support fraud detection and claim investigation workflows. Clients can use this integration to improve claim insight, reduce manual research, and make more informed claim decisions by submitting claim data to ISO and receiving match and claim history results back in BriteCore.

More information:

  • ISO ClaimSearch overview: https://www.verisk.com/insurance/products/iso-claimsearch/
  • Verisk insurance solutions: https://www.verisk.com/insurance/

Within BriteCore, ISO ClaimSearch is used for two main purposes:

  1. Submit claim data to ISO ClaimSearch so the carrier contributes claim information to ISO.
  2. Receiving and reviewing ISO results directly within the claim, including match details, alerts, notifications, risk indicators, and response history.

The integration supports:

  • Initial claim search requests
  • Replacement requests when claim data changes
  • Scheduled research requests based on configuration
  • Webhook-based responses from ISO back into BriteCore
  • Retries for failed webhook processing events

Adoption considerations

Clients should evaluate the following before enabling the integration:

  • Configuration dependency: ISO mapping values (such as line of business, coverage, and loss cause mappings) must be configured correctly for accurate submissions and results. See Section 3 for details. 

Implementing the Integration 

Before implementation begins, the client should have:

  1. An active relationship/account with Verisk ISO ClaimSearch.
  2. Internal agreement on claim workflows for initial searches, updates, and periodic re-searches.
  3. Staff identified for:
    • BriteCore configuration ownership
    • Claims operations/testing ownership
    • Vendor coordination

1. Install the ISO ClaimSearch Integration

Installation Steps

  1. Go to Settings > Vendor Integration > Production.
  2. Search for Claim Search.
  3. Install the integration.
  4. Once installed, open the integration configuration screen.

2. Configure Integration Settings

After installation, configure the integration settings.

Authentication Details

The integration requires client-specific ISO ClaimSearch credentials, including:

  • Username
  • Password
  • Agency ID

Note: The Agency ID is tied to the carrier/client, not to individual agents. 

Example: ABC Carrier would have its own Agency ID.

Failed Webhook Retry Count

A webhook is an automated message sent from one system to another when an event occurs. Instead of BriteCore constantly checking ISO ClaimSearch for updates, ISO automatically sends information to BriteCore via a webhook whenever search results, alerts, or claim updates are available.

In the ISO ClaimSearch workflow, webhooks are used to return claim search responses from ISO back into BriteCore. This is how BriteCore receives:

  • Match results
  • Risk indicators
  • Alerts
  • Notifications
  • Research request responses
  • Replacement request responses

Without webhooks, users would need to manually check ISO for updates. The webhook allows claim search activity and results to flow back into the claim automatically.

This setting controls how many times BriteCore retries failed webhook events.

Use this when ISO sends data back to BriteCore, but BriteCore is temporarily unable to process the webhook. For example, if the BriteCore site is unavailable, the webhook can be retried.

Important behavior:

  • Retries occur once per day.
  • If the retry count is set to 5, BriteCore retries the event for up to 5 days.
  • The maximum retry period is 30 days.
  • This setting applies to webhook processing failures, not to claim search requests rejected by ISO.

Automatic Re-search Request Interval

The Scheduled Re-Search Interval Days (0 = disabled) setting controls how often BriteCore automatically performs a new ISO research request after a successful claim search.

Behavior:

  • The interval is measured in days.
  • The countdown starts from the last successful search for the claim
    • This includes manual and automated searches.
  • A value of 0 disables scheduled automatic research requests.

Example: If the setting is 30, BriteCore will automatically send another research request 30 days after the last successful search.

3. Configure System Tags

System tags are used to map BriteCore policy, coverage, and claim information to ISO ClaimSearch codes. For more details on how to add or edit system tags, read this article. 

Required System Tag Categories

BriteCore has two system tag categories:

  1. Line of Business Code
  2. Coverage Code

Line of Business Code

The line of business code maps a BriteCore policy type to the ISO line of business value. This can apply to multiple policy programs, including state-specific programs.

Example: PPHO = Homeowners

Coverage Code

Coverage codes map BriteCore line items or coverages to ISO coverage values.

These codes come from ISO documentation and should be configured based on the carrier’s lines and coverages.

Where to Obtain Codes

Codes are provided by ISO ClaimSearch documentation. Please see your ISO representative to obtain a copy. 

4. Configure Perils / Loss Causes

Each peril or loss cause should be configured with its ISO code.

  1. Go to the Claims > Peril.
  2. For each peril, add the corresponding ISO code.
  3. Confirm that claims using ISO ClaimSearch have a loss cause selected.

5. Required Claim Data for ISO ClaimSearch

Before BriteCore can send an automatic initial request to ISO ClaimSearch, the following claim details must exist:

  • Loss date
  • Loss address
  • Parties with addresses
  • Adjuster
  • Exposure (specifically coverages being filed against)
  • At least one Risk record, such as:
    • Vehicle information
    • Property address
    • Injury 

Important Implementation Note

For carriers that do not use Vehicle, Damaged Property, or Injury tabs, BriteCore relies on claim-level information when possible:

  • Loss address
  • Claim description
  • Claim loss cause
  • Party information
  • Exposure/coverage filed against

6. Request Types

ISO ClaimSearch supports multiple request types within BriteCore:

  • Initial 
    • The first request BriteCore sends to ISO ClaimSearch when the required claim data is available.
  • Replacement 
    • Replacement requests are sent automatically when claim data changes after the initial request.

Note: Important behavior:

  • Replacement requests are sent automatically.
  • Requests are delayed by approximately 1 hour.
    • Note: Replacement requests are delayed by 1 hour so BriteCore can combine multiple claim updates into a single request, rather than sending a new ISO ClaimSearch request each time a small change is made to the claim.
  • Changes made during that time are consolidated into a single request.
  • BriteCore extends the delay window if additional changes are made during it, until the changes have settled.
  • Re-search 
    • Re-search requests are follow-up searches sent after the initial search and can be triggered the following ways:
  • Automatically based on the configured re-search interval.
  • Manually in the Claims system under Information > Past Claims.

Using the integration

1. Where to Find ISO ClaimSearch

ISO ClaimSearch is available under Claims > Information > Past Claims.

The ISO ClaimSearch area displays:

  • Request history
  • Notifications
  • Match results
  • Risk update responses
  • Risk indicators
  • Involved parties returned by ISO
  • Alerts

2. Prepare the Claim

Before requesting ISO ClaimSearch, ensure the claim contains the required information:

  • Loss date
  • Loss address
  • Claim description
  • Loss cause/peril
  • Parties with addresses
  • Assigned adjuster
  • Exposure or coverage filed against

Depending on the claim type and carrier workflow, additional information may include:

  • Vehicle details
  • Damaged property details
  • Injury details

3. Request an ISO ClaimSearch

Once the claim has the required information, BriteCore automatically sends the request to ISO ClaimSearch.

If the request is not sent automatically, or if an error occurs, the issue will be displayed in the Past Claims card.: 

  1. Go to Claims > Information > Past Claims.
  2. Review and complete any missing required fields.
  3. Select Request Search.

If the request is accepted, BriteCore sends the claim data to ISO. A message will display when the request is pending. 

ISO responses are not immediate and may take approximately 30 minutes to return.

4. Review Results

When ISO returns a response, BriteCore displays the results in Claims > Information > Past Claims >  ClaimSearch, which include:

  • No Matches: If ISO does not find related claim history, the response will show that no matches were returned.
  • Match Results: If ISO returns matches, BriteCore lists the matches and allows the user to review match details.

Risk Update Response

ISO may return a risk update response with information about the current claim, which may include:

  • Alerts
  • Risk indicators
  • Involved parties
  • Related risks

Alerts

If ISO returns an alert, BriteCore displays a red alert indicator.

  • BriteCore shows a single red alert indicator at the top of the claims search section. BriteCore then shows the alert text in the request history table and in the details pop-up for individual request history entries, explaining what needs attention.

5. Automatic Replacement Requests

After the initial request is sent, BriteCore automatically sends replacement requests when claim data changes.

Changes that may trigger a replacement request include updates to:

  • Parties
  • Claim details
  • Loss information
  • Vehicles
  • Damaged property
  • Injuries
  • Exposures

Replacement requests are delayed by approximately one hour so multiple edits can be consolidated into a single request.

6. Automatic Re-search Requests

If enabled, BriteCore sends automatic re-search requests after the configured number of days. The schedule is based on the last successful search for the claim.

Note: If the automatic research interval is set to 0, scheduled re-search requests are disabled.

Was this article helpful?
0 out of 0 found this helpful
Return to top