Assigning exposures
Every exposure is assigned to a group and a user in that group. The assigned user has the primary responsible for managing the exposure.
Most exposures are assigned to the same user and group that owns the claim. However, exposures occasionally require special expertise that require assignment to a different user and group than that of the claim. For example, suppose there is a personal auto claim that includes three exposures: two exposures for damaged vehicles and one exposure for medical payments related to a fatal injury. The claim and the vehicle exposures are routine and can all be assigned to the same group and user. But the injury exposure is likely to involve a significant payment or litigation. This exposure is assigned to a group and user that specialize in fatalities.
When you create an exposure through the system APIs, ClaimCenter automatically executes the
exposure assignment rules to initially assign the exposure to a group and user. You can use
the POST /claims/{claimId}/exposures/{exposureId}/assign
endpoint to
reassign the exposure as needed.
Assignment options
An exposure can be assigned through the system APIs in the following ways:
- To a specific group and user in that group
- To a specific group only (and then ClaimCenter uses assignment rules to select a user in that group)
- To the claim owner
- By re-running the exposure assignment rules
- This can be appropriate if you have modified the exposure since the last time assignment rules were run and the modification might affect who the exposure would be assigned to.
The root resources for the /exposures/{exposureId}/assign
endpoints is
ExposureAssignee
. This resource specifies assignment criteria. The schema
has the following fields:
Field | Type | Description |
---|---|---|
autoAssign |
Boolean | Whether to assign the exposure using assignment rules |
claimOwner |
Boolean | Whether to assign the exposure to the claim owner |
groupId |
string | The ID of the group to assign the exposure to |
userId |
string | The ID of the user to assign the exposure to |
The ExposureAssignee
resource cannot be empty. It must specify a single
logical assignment option (group and user, group only, claim owner, or automatic
assignment).
For more information on how assignment rules execute assignment, see the Gosu Rules Guide.
Assignment example - Assigning to a specific group (and user)
The following assigns exposure cc:48 (on claim cc:34) to group demo_sample:31 (Auto1 - TeamA) and user demo_sample:2 (Sue Smith).
POST /claim/v1/claims/cc:34/exposures/cc:48/assign
{
"data": {
"attributes" : {
"groupId" : "demo_sample:31",
"userId" : "demo_sample:2"
}
}
}
The following assigns exposure cc:48 (on claim cc:34) to group demo_sample:31 (Auto1 - TeamA). Because no user has been specified, ClaimCenter will execute assignment rules to assign the exposure to a user in group demo-sample:31.
POST /claim/v1/claims/cc:34/exposures/cc:48/assign
{
"data": {
"attributes" : {
"groupId" : "demo_sample:31"
}
}
}
Note that there is currently no endpoint that returns groups or group IDs. To assign exposures to a specific group, the caller application must determine the group ID using some method other than a groups system API.
Assignment example - Assigning to the claim owner
The following assigns exposure cc:48 (from claim cc:34) to the group and user that owns the parent claim.
POST /claim/v1/claims/cc:34/exposures/cc:48/assign
{
"data": {
"attributes" : {
"claimOwner" : true
}
}
}
Assignment example - Using automated assignment
The following assigns exposure cc:48 (from claim cc:34) using automated assignment rules.
POST /claim/v1/claims/cc:34/exposures/cc:48/assign
{
"data": {
"attributes": {
"autoAssign" : true
}
}
}