openIDL - System Requirements Table (DaleH @ Travelers)

Grouping

ID

Date

Requirement

Data and Data Integrity

D.1

5/23/22

Data contained in the carrier data store will conform to OpenIDL data model standards

Data and Data Integrity

D.2

6/1/22

OpenIDL data model standards shall exist for all Property & Casualty lines of business except Workers Compensation (List out lines of business). Domestic business for now. 

Data and Data Integrity

D.3

5/23/22

Minimal data attributes to be available in carrier data store shall consist of the "Day 1" OpenIDL data model fields, other attributes in the OpenIDL data model are populated at the option of the carrier

Data and Data Integrity

D.4

5/23/22

Data shall consist of policy and loss transactions over the course of the policy term and lifetime of any associated claims based on source system activity

Data and Data Integrity

D.5

5/23/22

Data shall be current to the Prior Month + 45 days

Data and Data Integrity

D.6

5/23/22

Companies shall maintain data in the carrier data store for 5 prior years plus current year

Data and Data Integrity

D.7

6/1/22

All data contained in the carrier data store is soley owned and controlled by that carrier 

Data and Data Integrity

D.8

6/1/22

Data shall remain accurate as of a point in time and may be corrected over time if errors in the transmission of data occurs with no obligation to restate prior uses of the data. Once data leaves the carrier node, that data is assumed to be published/accepted.

Data and Data Integrity

D.9

6/1/22

OpenIDL shall maintain (specification and implementation) an edit package to be available and used by carriers to test conformance to data model standards and data point interactions similar to the functioning of the AAIS SDMA portal. Implementation is part of HDS solution. OpenIDL will audit, certify and conformance of edit package implementation.

Data and Data Integrity

D.10

5/23/22

Data must pass through OpenIDL edit package and be within 5% error tolerance per line and state based similarly to acceptance by AAIS through SDMA portal

Data and Data Integrity

D.11

6/1/22

The OpenIDL data model standards will foster effective and efficient data extractions such that queries of data can be satisfied within 24 hours of commitment to participate in an information request  

Data and Data Integrity

D.12

6/1/22

Any changes NAIC required fields to the OpenIDL data model will require a minimum of 18 months notice for carriers to conform 

Information Requests

IR.1

6/1/22

Requests for information shall be specific in detail and communicated through a secured protocol

Information Requests

IR.2

6/1/22

Forum shall be established for carriers and regulators to discuss and agree to intent and interpretation of information request

Information Requests

IR.3

6/1/22

Request for information shall  be for aggregated information only, no individual policy, claim, or personally identified information shall be requested or honored

Information Requests

IR.4

6/1/22

information requests shall identify who has access to the private analytics node

Information Requests

IR.5

5/23/22

Information requests shall define timeframes for data to be included in the aggregation

Information Requests

IR.6

5/23/22

Information requests shall define the attributes to be used in aggregation

Information Requests

IR.7

5/23/22

Information requests shall define the logic for extracting and aggregating data

Information Requests

IR.8

5/23/22

Information requests shall identify and define the calculations to be used in aggregations, analysis, and reporting

Information Requests

IR.9

5/23/22

Information requests shall define the specific use of the information

Information Requests

IR.10

6/1/22

Information requests shall define the permitted accessors to the information and users of data

Information Requests

IR.11

5/23/22

Information requests shall communicate the proportion of individual carrier information to the population of data in the extraction prior to final commitment to participate

Information Requests

IR.12

5/23/22

Information requests shall be for one time use only.  Additional uses for data will require a new request. 

Information Requests

IR.13

6/1/22

Information requests shall identify the path information will flow from its raw form through final reporting  (e.g. carrier data store to private analytics node to Multi-Carrier aggregation mode to Regulator)

Information Requests

IR.14

6/1/22

Information requests shall identify the form information will flow from its raw form through final reportings (raw data; carrier summarized aggregated and anonymized data; reported data)

Information Requests

IR.15

5/23/22

Information requests have an expiration date and time from which consent is needed, if applicable

Information Requests

IR.16

6/1/22

All requests for information, its approval, the disposition of data from its raw form through final reporting shall be tracked, recorded and archived within OpenIDL

Information Requests

IR.17

5/23/22

Carriers who participate in information requests shall receive a copy of the final information presented as well as their individual carrier results

Information Requests

IR.18

6/1/22

Carriers decide in which information requests they will participate

Information Requests

IR.19

6/1/22

Carriers must provide an affirmative response prior to any information being extracted to the private analytics mode

Information Requests

IR.20

5/23/22

Final reports shall be archived by OpenIDL for 3 years

Access and Security

AS.1

5/23/22

Carrier's raw data will be "walled off" from other entities with access only through permissioned protocols

Access and Security

AS.2

6/1/22

Carriers raw data shall not leave its control - a secured limited access "private analytics node" may be established for processing information requests

Access and Security

AS.3

6/1/22

If multiple information requests are being processed at the same time, separate "private analytics nodes" with separate access shall be employed

Access and Security

AS.4

6/1/22

If multiple information requests are being processed at the same time, the data for each request will be segregated

Access and Security

AS.5

6/1/22

Carrier data may be transmitted to a private analytics node only as the result of an approved data request via a permissioned access protocol

Access and Security

AS.6

5/23/22

Carrier data may be transmitted to a private analystics node that has been aggregated and anonymizated through a secured protocol

Access and Security

AS.7

6/1/22

Carrier data in the private analytics node shall only be used for the purposes for which permissioned access has been granted

Access and Security

AS.8

6/1/22

Carrier data in the private analystics node shall be immediately purged upon completion of the processing for which permissioned access was granted

Access and Security

AS.9

5/23/22

No Personally identifiable information (PII) data shall be transmitted 

Access and Security

AS.10

5/23/22

No altering or embellishing data including appending outside data is permitted throughout the processing of the information request unless approved by carrier

Access and Security

AS.11

5/23/22

No changes to request, attributes used, extraction patterns, accessors, users, or specific use of the data is permitted post consent

Access and Security

AS.12

5/23/22

Only authorized approvers may commit carrier to a data request

Access and Security

AS.13

5/23/22

Data request communication shall be through a communications protocol within OpenIDL and archived within OpenIDL

Access and Security

AS.14

5/23/22

Individual carrier contribution to a data request will not exceed 15% of the population of premium, losses, exposures, etc. for a given information request

Access and Security

AS.15

6/1/22

OpenIDL is responsible for fulfilling multi-carrier information requests including extraction patterns, aggregations and formatting of final reports

Communication

C.1

6/1/22

All requests for information via OpenIDL will be through a secured communications portal within OpenIDL

Communication

C.2

6/1/22

All communications will be written (electronic) and be archived by OpenIDL for 10 years

Communication

C.3

6/1/22

A non-response to a request for information will  be considered a decline to participate

Communication

C.4

6/1/22

Requests for information must come from an authorized representative of the requesting body

Communication

C.5

6/1/22

Requests for information must state the regulatory authority for the information being sought

Communication

C.6

6/1/22

Agreement to participate in a request for information is conditioned on OpenIDL providing the carrier the proportion of data that carrier is providing to the population of data

Communication

C.7

6/1/22

Final agreement to participate in a request for information is valid once received by the OpenIDL communications portal

Communication

C.8

6/1/22

Final agreement to participate may be recinded up to an hour after final agreement is received by the communciations portal to affirm participation