Creation of Deidentified Data Sample Clauses

Creation of Deidentified Data. As a service to Practice, SiteRx shall use Practice Data to create deidentified data, in accordance with, and as defined by, 45 C.F.R. § 164.514 (the “Deidentified Data”). For avoidance of doubt, the forgoing right only includes data, information or records in SiteRx’s possession via Practice’s use of the Platform, and does not permit SiteRx to modify or delete Practice’s data, information or records on Practice’s systems.
AutoNDA by SimpleDocs

Related to Creation of Deidentified 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.

  • Service Information Pages Verizon shall include all CBB NXX codes associated with the geographic areas to which each directory pertains, to the extent it does so for Verizon’s own NXX codes, in any lists of such codes that are contained in the general reference portion of each directory. CBB’s NXX codes shall appear in such lists in the same manner as Verizon’s NXX information. In addition, when CBB is authorized to, and is offering, local service to Customers located within the geographic area covered by a specific directory, at CBB’s request, Verizon shall include, at no charge, in the “Customer Guide” or comparable section of the applicable alphabetical directories, CBB’s critical contact information for CBB’s installation, repair and Customer service, as provided by CBB. Such critical contact information shall appear alphabetically by local exchange carrier and in accordance with Verizon’s generally applicable policies. CBB shall be responsible for providing the necessary information to Verizon by the applicable close date for each affected directory.

  • USE OF REFERRAL INFORMATION Recipient Broker/Agent shall use Referral information provided by XXXX.xxx for the sole purpose of providing real estate services. Recipient Broker/Agent agrees that any Referral e-mail and/or other contact information will not be added to any telemarketing or email distribution lists or provided to a third party without the written consent of the Referred Client.

  • Your Information You must provide updated information to any person to whom you claimed to be an exempt payee if you are no longer an exempt payee and anticipate receiving reportable payments in the future from this person. For example, you may need to provide updated information if you are a C corporation that elects to be an S corporation, or if you no longer are tax exempt. In addition, you must furnish a new Form W-9 if the name or TIN changes for the account; for example, if the grantor of a grantor trust dies.

  • Your Data Subject to the limited rights granted by You hereunder, We acquire no right, title or interest from You or Your licensors under this Agreement in or to Your Data, including any intellectual property rights therein.

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

  • Use of websites (a) The Guarantor may satisfy its obligation to deliver any public information to the Lenders by posting this information onto an electronic website designated by the Guarantor and the Administrative Agent (the “Designated Website”) by notifying the Administrative Agent (i) of the address of the website together with any relevant password specifications and (ii) that such information has been posted on the website; provided, that in any event the Guarantor shall supply the Administrative Agent with one copy in paper form of any information which is posted onto the website. (b) The Administrative Agent shall supply each Lender with the address of and any relevant password specifications for the Designated Website following designation of that website by the Guarantor and the Administrative Agent. (c) The Guarantor shall promptly upon becoming aware of its occurrence notify the Administrative Agent if: (i) the Designated Website cannot be accessed due to technical failure; (ii) the password specifications for the Designated Website change; (iii) any new information which is required to be provided under this Guaranty is posted onto the Designated Website; (iv) any existing information which has been provided under this Guaranty and posted onto the Designated Website is amended; or (v) the Guarantor becomes aware that the Designated Website or any information posted onto the Designated Website is or has been infected by any electronic virus or similar software. If the Guarantor notifies the Administrative Agent under Section 8.3(c)(i) or Section 8.3(c)(v) above, all information to be provided by the Guarantor under this Guaranty after the date of that notice shall be supplied in paper form unless and until the Administrative Agent is satisfied that the circumstances giving rise to the notification are no longer continuing.

  • 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.

  • Company Creation and Use of Confidential Information The Executive understands and acknowledges that the Company has invested, and continues to invest, substantial time, money and specialized knowledge into developing its resources, creating a customer base, generating customer and potential customer lists, training its employees, and improving its product offerings in the field of financial services. The Executive understands and acknowledges that as a result of these efforts, the Company has created, and continues to use and create Confidential Information. This Confidential Information provides the Company with a competitive advantage over others in the marketplace.

  • 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.

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