Configuring Cloud API behavior with workers' comp claims

Enabling the main injury incident

By default, workers' comp claims must be submitted within the context of a composite request. Also, there must be a "main" injury incident. This is an injury incident whose mainWorkersCompIncident property is set to true.

This behavior is enforced by the EnableWorkersCompMainInjuryIncidentInCloudAPI application configuration parameter, which is introduced in the 2024.07.0 (Kufri) release.

• For insurers who enter production with the 2024.07.0 (Kufri) release or a later release, this parameter is set to true by default.
• For insurers who entered production with a release earlier than the 2024.07.0 (Kufri) release, during the update process, this parameter is set to false by default to maintain the behavior of previous releases.

When the parameter is set this parameter to false:

• Workers' comp claims can be submitted outside of a composite request.

• The "main" injury incident is not returned by the /injury-incidents endpoint
  • However, if a caller is able to ascertain the main injury incident's ID, then it can be accessed directly through the /claim/injury-incident/{incidentId} endpoint
• The InjuryIncident schema's mainWorkersCompIncident property cannot be updated through Cloud API

Exposing additional fields

As of this release, the base configuration of Cloud API exposes many of the fields used by ClaimCenter to process workers' comp claims. But it does not expose all of them.

If there are fields that you need for Cloud API to support workers' comp claims, you can configure Cloud API to expose them. This applies to both base configuration fields and extension fields.