Personal data
Information allowing individual to be identified, either on its own or in combination with other info
Sensitive personal data
Info which disclosure to others without consent can cause high level of distress/damage
Circumstances under which sensitive personal data can be processed
Explicit consent given
Required by law for employment purposes
Protect vital interests of individual/individual/another person
Needed for administration of justice/legal proceedings
Characteristics of big data
Big data consideration
Data governance
Overall management of availability, usability, integrity and security of data employed in organisation
Data governance risks
Data risks
Reasons why data may not reflect future
Algorithmic decision making
Automated trading involving buying/selling of financial securities electronically to capitalize on price discrepancies for same stock/assets in different markets
Data requirements
Must be controlled through single, integrated system
Advantages of keeping data in a single system
Sources of data
Public data
- Publsihed accounts
- Overseas data
- National statistics
- Industry data
Internal data
Reinsurer
Industry-wide collection schemesReasons why data from industry collection schemes may not be comparable
Other problems with data from industry wide collection schemes
Checks on data
• Past data can help verify current data
• Accounting data is useful to help verify income and outgo + value of assets
• Data on individual assets could be checked and verify:
- Existence of assets
- Allowed to be held for valuation purposes
- If valuation is restricted by legislation/regulation
Assertions to check quality of data
Lack of ideal data
Sources of poor quality data
* Poor data system design
Mechanisms that can be used to ensure good quality data
Proposal form
Must be designed to:
Collect data at appropriate level, incl data not currently used but may be needed in future
Clear and unambiguous to give correct information
Have inputs be as quantitative as possible
Claim form
Must be clear and unambiguous and must link to proposal form so cross-checking can be done
Input of data onto system
Inputs must be in same order as in proposal form so person inputting info doesn’t need to interpret info
Staff inputting info must be well trained
Financial incentives for accuracy
System must have validation checks, e.g. checks on
- blank entry fields
- sensible entry values e.g. sensible bounds on ages and sum assureds
Insurer may send policyholder key info for verification
Other features of good data system
System must be capable of storing info, so that historical data can be used for future pricing exercises
System must be robust and flexibles
Secure- many can view but not many can amend
At regular intervals, checks of movement analyses must be carried out and checks of changes in policy details, e.g. how sum assured is changing from year to year