Claim Incident Configuration table

  • Release version: Xanadu
  • Updated October 10, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Claim Incident Configuration table

    The Claim Incident Configuration table [sninsclaimincidentconfig] within the Insurance claims application allows you to define the claim incidents that can be created in the workflow. This table associates service definitions with incidents and generates corresponding adjuster tasks automatically, reducing the need for manual notifications to adjusters.

    Show full answer Show less

    Key Features

    • Name: Defines the name of the claim incident configuration entry.
    • Active: Indicates whether the incident is active, affecting its visibility in the first notice of loss playbook.
    • Adjuster task service definition: Links to the service definition that triggers the creation of an adjuster task.
    • Create adjuster task: Options to generate tasks per incident or per incident type.
    • Incident table name: Identifies where incidents are stored.
    • Incident type icon: Displays an icon in the playbook for the claim incident.
    • Itemized loss available: Indicates support for itemizing losses, useful for claims like baggage.
    • Order: Determines how the service definition appears in the playbook.
    • Service definition: Links to the case service definition (e.g., Report travel claim).
    • Short description: Provides a brief description of the claim incident visible in the playbook.

    Key Outcomes

    Using the Claim Incident Configuration table enhances the efficiency of managing insurance claims by automating adjuster task creation and providing a structured way to handle various incident types. For example, in a travel insurance scenario, this configuration streamlines the reporting process and allows for itemized loss tracking when applicable, improving the clarity and management of claims.

    Associate the service definition of a case with the incident and adjuster task service definitions by using the Claim Incident Configuration [sn_ins_claim_incident_config] table in the Insurance claims application.

    Claim Incident Configuration table overview

    You can define the claim incidents that can be created in the Insurance claims workflow by making an entry in the Claim Incident Configuration [sn_ins_claim_incident_config] table. This incident type also creates an adjuster task in the system for the corresponding case so that you don't have to notify the adjuster about the case.

    To access the Claim Incident Configuration [sn_ins_claim_incident_config] table, set the application scope of your instance to Insurance claims, and then navigate to All > Insurance claims > Administration > Claim incident configurations.

    The following example shows the table fields of the Claim Incident Configuration (sn_ins_claim_incident_config) table. For more information, see the next section.Claim Incident Configuration table in Insurance claims.

    Claim Incident Configuration Table fields

    The following table shows the fields in the Claim Incident Configuration [sn_ins_claim_incident_config] table.
    Table 1. Claim Incident Configuration table fields
    Field Description
    Name Name of the claim incident configuration entry.
    Active Status of whether this incident is active or inactive and whether the incident displays in the first notice of loss playbook.
    Adjuster task service definition Adjuster task service definition (that is, a service definition that creates an adjuster task in a claim). For more information, see Create a service definition for Insurance claims.
    Create adjuster task How an adjuster task is generated:
    • Per incident: Creates an adjuster task for each incident.
    • Per incident type: Creates an adjuster task for each incident type (for example, one task for all trip incidents and another task for all baggage incidents).
    Incident table name Table in which the incidents are stored. For more information, see Claim incidents.
    Incident type icon Icon that displays in the playbook for the claim incident.
    Itemized loss available Whether the claim incident supports itemizing each loss (for example, to itemize each item in a baggage claim).
    Order Order in which the service definition appears in the playbook.
    Service definition Service definition for the case (for example, Report travel claim). For more information, see Creating a service definition for Insurance claims.
    Short description Brief description of the claim incident, which is also displayed in the playbook.

    Travel insurance example of the Claim Incident Configuration table

    In the following travel insurance line of business (LOB) example, the claim incident configuration is reflected in the workflow when reporting a travel claim. The Incident details activity in the first notice of loss playbook shows the entries in the table and information about each entry.

    Entries in the Claim Incident Configuration table that can be seen in the Incident details activity.

    If the claim incident supports an itemized loss as defined in the table, the Itemized Loss/Expenses tab is also displayed when the incident is saved as shown in the following example.

    Itemized Loss/Expenses tab is displayed for an incident when the Itemized loss available is true.