Specified Data Sample Clauses

Specified Data. Includes, but is not limited to, Client, patient and transactional information required for home delivery orders on behalf of Customer; pet medical records; pet vaccination history; and Pharmacy, Client and Patient Data.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Specified Data. The Specified Data relating to the Business that was supplied by or on behalf of the Ceding Company or any of its Affiliates to the Reinsurer or any of its Affiliates in connection with this Agreement and the transactions contemplated hereby as of the date supplied (or if later corrected or supplemented prior to the date hereof, as of the date corrected or supplemented), (a) was derived from the Books and Records, (b) was generated from the same underlying sources and systems that were utilized to prepare the Financial Statements, (c) to the extent applicable to the Specified Data, was compiled in accordance with generally accepted actuarial principles and practices consistently applied given the intended purpose at the time compiled, (d) was accurate in all material respects as of the date prepared, and did not omit any such factual information or data directly relevant to the calculations to be performed in and under or scope of the particular, applicable data file component of the Specified Data as such calculations and scope were defined or reasonably described, as applicable, therein, in each case as of the date so provided, and (e) to the extent applicable, was based upon a complete inventory of Reinsured Contracts available as of the date delivered. The Ceding Company is not aware to its Knowledge of any omissions, errors or discrepancies that would materially affect such data since the respective dates on which such documents were prepared.
Sample 1Sample 2
Specified Data. Generation of specialized data-based reports which would require additional programming, the purchase of additional data, costs for county staff research, or similar matters not necessary to carry out services outlined in Section 2.0.
Sample 1Sample 2
Specified Data. Generation of specialized data-based reports or the development of special geo-based designations from CITY maps or geographic areas which would require additional programming, the purchase of additional data, costs for county staff research, additional historical parcel tracking by CONTRACTOR or similar matters not necessary to carry out services outlined in Section 2.0.
Sample 1
Specified Data. All Specified Data concerning Seller, Sponsor and the Purchased Assets that has been delivered by or on behalf of Seller to the Buyer Agent under or in connection with the Agreement or by or on behalf of Sponsor to the Buyer Agent under or in connection with the Guaranty is true, complete and correct in all material respects as of the date of delivery (or if stated to have been prepared as of an earlier date, as of such earlier date).
Sample 1
Specified Data. Company will provide Insurance Provider access to a secure API that allows Insurance Provider to request claim-related information and receive a structured and normalized representation of the invoice that the Client previously submitted. If desired, Insurance Provider will also be able to request via this API additional medical information which will return a text-based version of the Patient’s medical history, such as SOAP notes, unstructured notes, prescription history, and vitals history, recorded in Customer’s PIMS, recorded in Customer’s PIMS in proximity before and after the date of the service associated with the request.
Sample 1
Specified Data. All Specified Data concerning Seller and the Purchased Assets that has been delivered by or on behalf of Seller to Buyers under or in connection with this Agreement, is complete and correct in all material respects as of the date of delivery (or if stated to have been prepared as of an earlier date, as of such earlier date).
Sample 1
AutoNDA by SimpleDocs
Specified Data. The following data will be provided to <Data User> for the business purposes detailed in Section 7. Use Cases: Use Cases Project <CC> Agreement between <Data Owner> and <Data User> Approved by <Data Owner> Agreed by <Data User> Director/Delegate Effective date As above Review Date As above <Batched reports containing aggregated> <System A> data will be created in <System B> and transferred through to <Project CC>.
Sample 1

Related to Specified Data

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by XXX to return or destroy Student Data. Except for Subprocessors, Xxxxxxxx agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.

  • Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.

  • Aggregated Data Anonymous, aggregate information, comprising financial account balances, other financial account data, or other available data that is collected through your use of the Services, may be used by us and our service providers to conduct certain analytical research, performance tracking and benchmarking. Our service providers may publish summary or aggregate results relating to metrics comprised of research data, from time to time, and distribute or license such anonymous, aggregated research data for any purpose, including but not limited to, helping to improve products and services and assisting in troubleshooting and technical support. Your personally identifiable information will not be shared with or sold to third parties.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Statistical, Demographic or Market-Related Data All statistical, demographic or market-related data included in the Registration Statement, the Disclosure Package or the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate and all such data included in the Registration Statement, the Disclosure Package or the Prospectus accurately reflects the materials upon which it is based or from which it was derived.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").

  • Categories of Data Subject 2.1. When using this Service, the groups of individual’s data by category • Your end users using the service that you deliver • The personal data about your employees and contractors that bookinglab collects as a Customer of ours to complete account administration and set up

  • Statistical or Market-Related Data Any statistical, industry-related and market-related data included or incorporated by reference in the Time of Sale Disclosure Package, are based on or derived from sources that the Company reasonably and in good faith believes to be reliable and accurate, and such data agree with the sources from which they are derived.

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!