Today when a claim is submitted but does not meet some criteria it is rejected, therefore there is some check in the front end that prevent submitting a claim that don’t meet those criteria

This is seen as bad in term of user experience because the user have no clue why the claim don’t meet the criteria, worst, a single claim can hide the submit button for when a list of claim is selected

In this ticket we will disable the FE check but we will need to make sure it won’t reject the claim not eligible therefore I want to discuss here ideas to distinguish claim submit failure and rejection

the problem is that there is mandatory validation (coverage: policy that have the claimed product) and optional validation. adding a new validation can be done via rules/signal but removing a validation might be trickier (eg: 0 value claims)

possible approach:

• 1 list for submission failure that can contains mandatory validation (may be kept in rejection check as it will never reach that point) and optional validation

• 1 list for optional rejection validation

Saurav Bhattarai Daniella Majakari Dragos Dobre any thoughts ?