Claims Database Clause Samples

The Claims Database clause establishes the requirement for maintaining a centralized record of all claims made under the agreement. This database typically includes details such as the nature of each claim, relevant dates, parties involved, and the status or resolution of each claim. By mandating a structured and accessible repository of claims information, the clause ensures transparency, facilitates efficient claims management, and helps prevent disputes by providing a clear historical record.
Claims Database. The Claims Administrator will maintain a joint database of all cases filed in any court and all unfiled claims identified pursuant to the Case Census Orders and in connection with enrollments of Claims in the Program, which database shall be made available to the MDL Court, the Illinois Coordinating Court, and the California Coordinating Court, Takeda and the PSRC. The database may include for every registered ACTOS-related claim, inter alia, the current venue, case number, alleged injury, date of alleged injury, alleged duration of ACTOS Products use, the identity of the Primary Counsel responsible for the Claim, state where alleged injury occurred, and filing jurisdiction, as well as other claim specific information. Nothing herein prevents either Takeda or the PSRC from maintaining their own separate database of all registered plaintiffs and unfiled Claims. The Claims Administrator may consult with Takeda and the PSRC regarding the accuracy of the information in the Case Census.
Claims Database. As soon as reasonably possible, the Settlement Administrator will provide Class Counsel and Defendants’ Counsel the total number of DSL Claimants and the total number of ARL Claimants. The Settlement Administrator will maintain a secured database of Claims, which will include all relevant information captured from claimants’ claim forms.
Claims Database. The Claims Administrator will maintain a joint database of all cases filed in any court and all unfiled Claims identified pursuant to the Case Census Orders and in connection with enrollments of Claims in the Program, which database shall be made available to the MDL Court and the New Jersey Coordinating Court, Daiichi Sankyo, Forest and the PNC. The database may include for every registered Olmesartan Products-related claim, inter alia, the current venue, case number, alleged injury, date of alleged injury, alleged dates of Olmesartan Products use, the identity of the Primary Counsel responsible for the Claim, state where alleged injury occurred, and filing jurisdiction, as well as other claim specific information. A list of the data to be compiled in the database is set forth in the spreadsheet that is referred to in Appendix A, available through the Claims Administrator’s website. Nothing herein prevents either Daiichi Sankyo, Forest or the PNC from maintaining their own separate database of all registered plaintiffs with filed cases and claimants with unfiled Claims. The Claims Administrator may consult with Daiichi Sankyo, Forest and the PNC regarding the accuracy of the information in the Case Census.
Claims Database. Contractor will use best efforts to ensure that adequate information is captured during the claim payment process to allow HHS to evaluate individual and overall high risk pool program health care utilization. Contractor shall provide HHS reports upon request concerning utilization that are in a mutually agreeable electronic format, to include the ability to routinely update claims files as necessary, report individual claims histories as well as claims experience by category of condition or treatment, and fully document the claims adjudication process. The Claims database shall contain for each claimant an identification number, claim number, date(s) of service, treatment by descriptor and treatment code, provider name and provider number, date and type of service, amount billed, amount allowed, and amount paid, enrollee responsibility. In all respects, claims and utilization data shall be maintained, and available for reporting to and analysis by HHS or any designee, in a manner consistent with industry standards for comparable commercial health insurance carriers, or health plan administrators.
Claims Database. The Claims Administrator will maintain a joint database of all cases filed in any court and all unfiled claims identified pursuant to the Case Census CMOs and in connection with enrollments of Claims in the Program, which database shall be made available only to the MDL Court, the State Coordinated Courts, BHCP and the NPC. The database may include for every registered DCOC ATE Injury claim, inter alia, the venue, case number, alleged injury, date of initial alleged injury, DCOC(s) used, the identity of the Primary Counsel responsible for the Claim, and state of Claimant's residence. Counsel representing the same Claimant shall confer and designate one counsel to serve as Primary Counsel for purposes of the Program to minimize the instances of multiple submissions of the same Claimant. Nothing herein prevents either BHCP or the NPC from maintaining their own separate database of all registered plaintiffs and unfiled Claims. The Claims Administrator will consult with BHCP and the NPC regarding the accuracy of the information in the Case Census. Within five (5) days after the Execution Date, BHCP and the NPC will provide the Claims Administrator with lists of all known filed and unfiled DCOC ATE Injury claims.
Claims Database. Except as set forth on Section 2.7 of the Disclosure Schedules, to the Knowledge of Seller, since May 16, 2016, all Claims with respect to Asbestos-Related Liabilities and Products Liabilities that have been received by Seller or its Subsidiaries (including the Company and its Subsidiaries) through due service of process on Seller or its Subsidiaries (including the Company and its Subsidiaries) are provided to the Claims Database for inclusion therein.

Related to Claims Database

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Database File The Servicer will provide the Successor Servicer with a data file (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Cutoff Date, (ii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Servicing Transfer, and (iii) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Servicing Transfer.

  • Data shared with Subcontractors If DSHS Data provided under this Contract is to be shared with a subcontractor, the Contract with the subcontractor must include all of the data security provisions within this Contract and within any amendments, attachments, or exhibits within this Contract. If the Contractor cannot protect the Data as articulated within this Contract, then the contract with the sub- Contractor must be submitted to the DSHS Contact specified for this contract for review and approval.

  • Class Data Not later than 15 days after the Court grants Preliminary Approval of the Settlement, Defendant will simultaneously deliver the Class Data to the Administrator, in the form of a Microsoft Excel spreadsheet. To protect Class Members’ privacy rights, the Administrator must maintain the Class Data in confidence, use the Class Data only for purposes of this Settlement and for no other purpose, and restrict access to the Class Data to Administrator employees who need access to the Class Data to effect and perform under this Agreement. Defendant has a continuing duty to immediately notify Class Counsel if it discovers that the Class Data omitted class member identifying information and to provide corrected or updated Class Data as soon as reasonably feasible. Without any extension of the deadline by which Defendant must send the Class Data to the Administrator, the Parties and their counsel will expeditiously use best efforts, in good faith, to reconstruct or otherwise resolve any issues related to missing or omitted Class Data.

  • Third Party Data Any statistical, industry-related and market-related data, which are included in the Disclosure Package and the Prospectus, is based on or derived from sources that the Company reasonably and in good faith believes to be reliable and accurate, and such data agrees with the sources from which it is derived, and the Company has obtained the written consent for the use of such data from such sources to the extent required.