...
- Much of content wrt OLGA that has been shown to date was prototyped and set up as a front-end website. This week the team has worked on the services layer- connecting database to front end
- No webpage updates today - more coming next week
- Focus of today: data elements and data extraction information with CAT reporting they are looking into
- Jeff - talked through various elements - data element definitions for NE CAT PoC that will be used for report
- Line of insurance - homeowners in this case
- Transaction date - date when the transaction was booked - fixed format codes (mm yy) - they talked about the poss. of making this an actual date if this fixed format makes it more difficult to use
- State code - reference codes for this are documented in separate tables.
- County Code - per state - ties in later with the zip code element, used for isolating claims pertaining to areas afflicted by catastrophe, and used to weed out unaffected areas.
- Transaction Code - includes paid loss + outstanding loss; 6-7 digit codes for new members that haven't used this format; mapping from their systems to these codes needs to be set up
- Loss Amount - table for this that is in this document as well
- Cause of Loss
- Accident date - actual date in which the loss occurred.
- Zip Code
- Claim number - says all of these claims in the event record are part of the same claim # (each claim has a unique identifier)
- Claim identifier - the identifier for each particular claim event
- Catastrophe indicator - identifies catastrophe, but for the purposes of the PoC, limited to this particular catastrophe - we determine from whatever data is extracted a binary indicator - was this part of the catastrophe or not?
- Accounting Date - it was recommended that this actually be a date. Suggestion: perhaps a placeholder for the date, and then it would default to the 15th if said date is unavailable). - Agreement with this change, no objection.
- Peter discussed calculation of the various amounts for the reporting side of things (pulled up excel sheet to illustrate). Looking by zip code; reviewing by county as well
- Looking at Number of Claims Recorded
- From our table - want to count the amount of records and alias to the claim count - where accident is greater than start date and less than end date
- Causes of loss - in a, b, & c - which are yet to be determined.
- Group by claim identifier to avoid double-counting records
- If multiple transactions in same accounting period and same claim: if they have the same claim identifier, they will be grouped together into one record - so can only count as one in this case.
- Claim count will indeed be a unique count rather than per transaction (not a record count but a claim count based on the claim # and id)
- Peter pulled up an example - made sure that the given record had a transaction code '2' which means it has a payment associated with it. (It was noted that he should further filter by location). For number of claims closed with payment, trans. code 2 needed, but to assume it's closed, they need to make sure it also has a transaction code '3' with a loss of 0 - to have an outstanding of zero. It's an open claim if it has an oustanding reserve.
- Looked at number of claims closed without payment (first) before coming back to one above it.
- Peter said 'I want to find all the ones that have 0 outstanding.'
- Of these, he said 'I also want to get rid of all the ones that have a level 2 transaction code associated with them.'
- Table A - outstanding with loss amt. 0 - without pay; table B - records that have a trans. code 2- there was a payment. Give me all the claim identifiers not in table B
- All of the amounts from these transactions will be summed up (but have not been accrued yet) - loss amounts. Peter will add this.
- We're aggregating based on these criteria that we have.
- Need to find the most recent outstanding.
- Also looking at number of claims with payment
- Number of claims closed without payment
- Paid loss
- Case of incurred loss
...
{"serverDuration": 94, "requestCorrelationId": "b0f272fbcac4e6af"}