How much telematics information do insurers need for claim classification?

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-8.xsd">
<mods version="3.8">
<titleInfo>
<title>How much telematics information do insurers need for claim classification?</title>
</titleInfo>
<name type="personal" usage="primary" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20230005262">
<namePart>Duval, Francis</namePart>
<nameIdentifier>MAPA20230005262</nameIdentifier>
</name>
<name type="personal" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080297572">
<namePart>Boucher, Jean-Philippe</namePart>
<nameIdentifier>MAPA20080297572</nameIdentifier>
</name>
<name type="personal" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20130016573">
<namePart>Pigeon, Mathieu</namePart>
<nameIdentifier>MAPA20130016573</nameIdentifier>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">usa</placeTerm>
</place>
<dateIssued encoding="marc">2022</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
</physicalDescription>
<abstract displayLabel="Summary">It has been shown several times in the literature that telematics data collected in motor insurance help to better understand an insured's driving risk. Insurers who use these data reap several benefits, such as a better estimate of the pure premium, more segmented pricing, and less adverse selection. The flip side of the coin is that collected telematics information is often sensitive and can therefore compromise policyholders' privacy. Moreover, due to their large volume, this type of data is costly to store and hard to manipulate. These factors, combined with the fact that insurance regulators tend to issue more and more recommendations regarding the collection and use of telematics data, make it important for an insurer to determine the right amount of telematics information to collect. In addition to traditional contract information such as the age and gender of the insured, we have access to a telematics dataset where information is summarized by trip</abstract>
<note type="statement of responsibility">Francis Duval, Jean-Philippe Boucher & Mathieu Pigeon</note>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080579258">
<topic>Cálculo actuarial</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080603779">
<topic>Seguro de automóviles</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080578848">
<topic>Análisis de datos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080591182">
<topic>Gerencia de riesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080592875">
<topic>Protección de datos</topic>
</subject>
<classification authority="">6</classification>
<location>
<url displayLabel="MÁS INFORMACIÓN" usage="primary display">
mailto:centrodocumentacion@fundacionmapfre.org?subject=Consulta%20de%20una%20publicaci%C3%B3n%20&body=Necesito%20m%C3%A1s%20informaci%C3%B3n%20sobre%20este%20documento%3A%20%0A%0A%5Banote%20aqu%C3%AD%20el%20titulo%20completo%20del%20documento%20del%20que%20desea%20informaci%C3%B3n%20y%20nos%20pondremos%20en%20contacto%20con%20usted%5D%20%0A%0AGracias%20%0A
</url>
</location>
<relatedItem type="host">
<titleInfo>
<title>North American actuarial journal</title>
</titleInfo>
<originInfo>
<publisher>Schaumburg : Society of Actuaries, 1997-</publisher>
</originInfo>
<identifier type="issn">1092-0277</identifier>
<identifier type="local">MAP20077000239</identifier>
<part>
<text>05/12/2022 Tomo 26 Número 4 - 2022 , p. 570-590</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">230613</recordCreationDate>
<recordChangeDate encoding="iso8601">20231214134312.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20230012499</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>