5.3.1. New

The operation new in case of a claim is used to initiate the claim process with a first notification of loss. The insurance provider creates a claim file and assesses the claim. In the following steps the claim can be rejected, or claim handling will commence. These subsequent steps make use of the change operation.

A notification of loss relates to a single policy, even if that policy is part of a package policy. A notification of loss does not relate to the package policy itself, only to one of its underlying policies. If more policies are involved in a loss or an event, for each policy a separate notification of loss should be made.

How to use variants

If you need to add a new claim, choose the operation new. If a particular handling variant is requested, use a variant. If not, select the default variant. The variant determines which attributes are mandatory. It is possible to add documents that provide additional information.

A positive response to the operation new contains the AFD structure of the request as reference, with the result of the transaction (process.statusType).The requested information that was collected during the transaction and a reference Id/number of the carrier for further communications (claimNumberCarrier), is also added to the output.

Different scenarios are possible, for example:

• If there is no immediate result available (because of manual processing), then the status is in process (in behandeling).
• If the claim is denied, then the status is rejected (afgewezen).
• If the claim is accepted, then a complete return message (input message completed with result data) is returned.
  

If a negative response is generated, that means the request is technically incorrect, it follows the general rules as described in the Error section of the HTTP status codes and error handling chapter.

Variants

The variant enables a differentiation in requirements to suit the specific situations (listed below), and for each variant, to which AFD structure it applies.

<default> – First notification of loss (FNOL)

The default variant is the initial creation of the claim file, the first notification of loss (FNOL). The claimStructure is used to add a new claim. The mandatory attributes (in a generic way) are listed in the table Mandatory input and/or output (I/O) attributes.

Endpoint definition

Method	Endpoint	Request	Query parameter(s)	Response	Remarks
POST	{ uri }/claims/new	claimStructure	N/A	claimStructure

Mandatory input and/or output (I/O) attributes

Entity	Attribute	I/O	Remarks
commonFunctional	dataCatalogVersion	I/O	Version of the data catalog on which the message is based.
commonFunctional	functionVariant	I/O	The function variant is used to determine the additional set of required and optional input and output data.
commonFunctional	businessLine	I/O	Classification of the type of contract. E.g. to be used for addressing within a company.
commonFunctional	porCompany	I/O	The identification of the insurer is necessary to find the correct product and rate combination.
commonFunctional	afdDefinitionName	I/O	Name of the AFD-definition.
commonFunctional	afdDefinitionVersion	I/O	Version of the AFD-definition.
process	statusType	O	The status of the process (codelist ADNSTS) within the entityType transaction.
claim	claimNumberCarrier	O	The identifying number of the claim at the company / underwriting agent. This number is linked to the claim file and (usually) does not change.
claim	lossNotificationDate	I/O	Date on which the claim was notified.
claim	dateOfLoss	I/O	Date when the accident/damage occurred.
policy	contractNumber	I/O	The identifying characteristic assigned by a company or underwriting agent.
incident	causeOfLoss	I/O	Description of the cause of damage/loss.
incident	incidentType	I/O	Code indicating the type of incident.

Note: since the attribute “entityType” is mandatory for all used structures, it is not mentioned in this table for clarity reasons.

registration – Registration of a new claim with an automatic underwriting

The variant registration makes it possible to register a new claim that already had an intake. Registration is needed for further claim handling. The claimStructure is used to add/register a new claim. The mandatory attributes (in a generic way) are listed in the table Mandatory input and/or output (I/O) attributes.

Endpoint definition

Method	Endpoint	Request	Query parameter(s)	Response	Remarks
POST	{ uri }/claims/registration	claimStructure	N/A	claimStructure

Mandatory input and/or output (I/O) attributes

Entity	Attribute	I/O	Remarks
commonFunctional	dataCatalogVersion	I/O	Version of the data catalog on which the message is based.
commonFunctional	functionVariant	I/O	The function variant is used to determine the additional set of required and optional input and output data.
commonFunctional	businessLine	I/O	Classification of the type of contract. E.g. to be used for addressing within a company.
commonFunctional	porCompany	I/O	The identification of the insurer is necessary to find the correct product and rate combination.
commonFunctional	afdDefinitionName	I/O	Name of the AFD-definition.
commonFunctional	afdDefinitionVersion	I/O	Version of the AFD-definition.
process	statusType	O	The status of the process (codelist ADNSTS) within the entityType transaction.
claim	claimNumberCarrier	O	The identifying number of the claim at the company / underwriting agent. This number is linked to the claim file and (usually) does not change.
claim	lossNotificationDate	I/O	Date on which the claim was notified.
claim	dateOfLoss	I/O	Date when the accident/damage occurred.
policy	contractNumber	I/O	The identifying characteristic assigned by a company or underwriting agent.
incident	causeOfLoss	I/O	Description of the cause of damage/loss.
incident	incidentType	I/O	Code indicating the type of incident.

Note: since the attribute “entityType” is mandatory for all used structures, it is not mentioned in this table for clarity reasons.