Using the Data Extract Service

How do the Stored Procedures work?

The Data Extract Service utilises Stored Procedures to return data from specific datasets. There are key features of the stored procedures which must be understood before the service can be used.


Extract Method

Users of the service extract data by specifying a date range. This can be a maximum of 1 month. When executing the stored procedures it is the responsibility of the user to ensure that there are no gaps between the dates specified from one execution to the next.


Dataset Selection

A stored procedure is provided for each dataset, totalling 18. To ensure that all of the information is retrieved, it is necessary to execute them all. The datasets available are as follows:

Dataset Name Description Reporting Basis Version Availability
Risk Core Risk data processed from Risk and Risk/Premium Bordereaux. Transactional v1.1 onwards
Risk_Coverage Coverage details relating to processed Risks, where captured from a Bordereau. Transactional v2.1 onwards 
Risk_Tax Tax details relating to processed Risks, where captured from a Bordereau. Transactional v2.1 onwards 
Premium Core Premium data processed from Premium and Risk/Premium Bordereaux. Transactional v1.1 onwards 
Premium_Coverage
Coverage details relating to processed Risks, where captured from a Premium Bordereau.
Transactional V3.0 onwards
Premium_Tax Tax details relating to processed Premium entries, where captured from a Bordereau. Transactional v2.1 onwards 
Claim Core Claim data processed from Claims Bordereaux. Transactional v1.1 onwards 
Claim_Expert Expert details relating to processed Claims, where captured from a Bordereau. Transactional v2.1 onwards 
Contract Core Contract data, stored at a Section level, of delegated authority agreements managed by Tide (e.g. Binder, Lineslip e.t.c.). In-Force v1.1 onwards 
Contract_Market
Market participation details associated with Tide Contracts/Sections
In-Force
v2.1 onwards 
Contract_ReportingChannel Reporting Channel details relating to Tide Contracts/Sections. In-Force v2.1 onwards 
Contract_Rule_Breach
Details of breaches on Contracts
In-Force
v2.2 onwards 
Contract_ClaimsAuthority Claims Authority details relating to Tide Contracts/Sections. In-Force v2.1 onwards 
Contract_Version Version history of Tide Contracts. In-Force v2.1 onwards 
Bordereau Core Bordereau data for received, processed and approved Bordereaux. In-Force v1.1 onwards 
Bordereau_Financial Summary financials relating to approved Bordereaux, provided at Section level. In-Force v2.1 onwards 
Risk_Codes Data relating to all risk codes added to a Contract Section.  In-Force
v2.6 onwards
Contract_Section_Location Permissible location data relating to a Contract Section. In-Force
v2.6 onwards
DataExtractSchema Data Extract Schema document. N/A v2.7 onwards

Please contact the Service Desk if you would like to obtain a copy of the data schema for these datasets.


Data Relationships

The data exported will relate to all Divisions associated with your Company in Tide. It is therefore necessary to account for this in downstream reporting to avoid inaccurate figures/values.

Please contact the Service Desk if you would like to obtain a copy of the entity relationship diagram and/or details of the field links for the datasets above. 


Reporting Basis

Data is presented in one of the following methods (based upon the dataset):

  • Transactional
    Each record exported represents the change from the last reported position of the entity. Therefore, all records relating to the same entity can be aggregated to produce the in-force position.

  • In-Force
    Due to the nature of both entities, each record exported represents the state of the entity at the time the record was created. The in-force position is therefore the record with the youngest created date/time.


Contra Entries

The output data may contain Contra entries, which represent a reversal of approved data. It is only the Transactional datasets which include these entries. As of DE v2.2 onwards, bordereau records will include ‘Deleted’ status records if a bordereau is deleted in Tide.


Data Warehouse Timestamp

The [DWH_InsertedDateTime] field has the timestamp for when a record is created in Data Warehouse.

When a market participant (Coverholder, Broker, Insurer or TPA) is added to an existing contract, the [DWH_InsertedDateTime] for any applicable existing Contract, Bordereau, Risk, Premium and Claim records in the Data Warehouse will have the date/time when the Contract was assigned a 'Signed' [Status] with them as a participant. Contract, Bordereau, Risk, Premium and Claim records created after this time will have the usual [DWH_InsertedDateTime] value.

A record is applicable to a market participant based upon the inception/expiry date of the contract, and the effective date of any endorsements. 


Stored Procedure Parameters

The stored procedures require the following parameters in order to execute successfully:

Parameter Description Input/Output SQL Data Type
Data_Creation_Start_DateTime
Start of the output date range. Applies the DWH_InsertedDateTime, UTC. Input datetime2(7)
Data_Creation_End_DateTime
End of the output date range. Applies the DWH_InsertedDateTime, UTC. Input datetime2(7)
ResultId Returns the result of the execution. 1 = Success, 2 = General Error, 9X = Specific Error (See Narrative). Output int
Result_Narrative Narrative associated with the ResultId. Output nvarchar(max)





Was this article helpful?

Can't find what you're looking for?

Contact Support