Ideas, suggestions and thoughts on the best way to actually store claim data, and how to access it and find it quickly and easily.

Storing Claims

What fields/data should be stored?

Claim Data 

1. Policyholder details
2. Details of the claim - what happened?
3. The referring client
4.  
5.  

Documents

1. Photos
2. Word and Excel
3. PDF
4. Video?
5. Audio?

Notes 

1. Currently all notes can be edited. Enhance this to allow editing up to x minutes/hours after creation. I.e After x minutes/hours the note becomes locked.

Accessing and Finding Claims

How to get to a particular claim, or a group of claims. 

1. Have the ability to open multiple claims at a time, rather than having to close each claim before opening the next. (thanks to Tom Zawistowski)

Processing Claims and Operational Features 

Some ideas about the actual process of claim management. How the workflow will look and operational features that will help with processing. I.e validation, alerts, notifications etc.

• Validation of a policy that is in force 
• Validation to check whether the property damaged is covered or not 
• Validation to check whether the cause of damage is covered or not. There could be multiple ways of checking this. 
• Check whether the claim amount will exceed any deductible - it should not rejec the claims but should provide a comparison between the estimate and the deductible.
• Once an FNOL is registered, the system should send out an SMS and / or an email to acknowledge intimation of the claim and that it has been recorded. 
• In the background, the claims should tringger a process to intiate a reserve made agains the claims especially if the claim is being intimated during the financial year or fiscal year ending.