Creation and Use of De-identified Data Sample Clauses

Creation and Use of De-identified Data. To the extent that Business Associate receives PHI or ePHI and in the event Business Associate wishes to de-identify PHI or ePHI, it must first submit its proposed plan for accomplishing the conversion to Covered Entity for Covered Entity's approval, which shall not be unreasonably withheld provided such conversion meets the requirements of 45 CFR § 164.514. Business Associate may use de-identified PHI or ePHI only as directed or otherwise agreed to by Covered Entity.
AutoNDA by SimpleDocs
Creation and Use of De-identified Data. Business Associate may de-identify any and all PHI, provided that any process or mechanism used to de-identify the data meets the requirements of 45 C.F.R 164.514(a)-(b). Business Associate may use or disclose (and permit others to use or disclose) such de-identified data on a perpetual unrestricted basis, but in no case shall Business Associate attempt to run or develop any keys, codes or algorithms that may be used to re-identify the data.

Related to Creation and Use of De-identified Data

  • Exclusions and Limitations for Third Party Software SUBJECT TO THE EXCLUSION OF DAMAGES STATED IN SECTION 9.2 AND WITH RESPECT TO THIRD PARTY SOFTWARE, UNDER NO CIRCUMSTANCES AND REGARDLESS OF THE NATURE OF ANY CLAIM SHALL SAP OR ITS LICENSORS’ BE LIABLE FOR AN AMOUNT IN EXCESS OF THE PAID LICENSE FEES FOR THE THIRD PARTY SOFTWARE DIRECTLY CAUSING THE DAMAGES.

  • Use of Data by User Registry Operator will permit user to use the zone file for lawful purposes; provided that (a) user takes all reasonable steps to protect against unauthorized access to and use and disclosure of the data and (b) under no circumstances will Registry Operator be required or permitted to allow user to use the data to, (i) allow, enable, or otherwise support the transmission by email, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than user’s own existing customers, or (ii) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator or any ICANN-­‐accredited registrar.

  • Use of Names The Manager and the Fund agree that the Manager has a proprietary interest in the names “DFA” and “Dimensional,” and that the Fund and/or Portfolio may use such names only as permitted by the Manager, and the Fund further agrees to cease use of such names promptly after receipt of a written request to do so from the Manager.

  • Use of Software Any software that is available on the Services ("Software") is the copyrighted work of Red Hat and/or its licensors. Copying or reproducing the Software to any other server or location for further reproduction or redistribution is strictly prohibited, unless such reproduction or redistribution is permitted by a license agreement accompanying such Software. You may not create derivative works of the Software, or attempt to decompile or reverse-engineer the Software unless otherwise permitted by law. Use of the Software is subject to the license terms of any license agreement that may accompany or is provided with the Software. You may not download any Software until you have read and accepted the terms of the accompanying software license. WITHOUT LIMITING THE FOREGOING, THE SOFTWARE IS WARRANTED, IF AT ALL, ONLY ACCORDING TO THE TERMS OF THE SEPARATE LICENSE AGREEMENT ACCOMPANYING THE SOFTWARE. EXCEPT AS WARRANTED IN SUCH LICENSE AGREEMENT, RED HAT, ITS PARENT, SUBSIDIARY, AND AFFILIATE COMPANIES, AND ITS LICENSORS DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THE SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, TO THE MAXIMUM EXTENT PERMITTED BY LAW.

  • Use of De-identified information De-identified information may be used by the Contractor for the purposes of development, research, and improvement of educational sites, services, or applications, as any other member of the public or party would be able to use de-identified data pursuant to 34 CFR 99.31(b). Contractor agrees not to attempt to re-identify de-identified Student Data.

  • Use of Materials There should be no limitations or restrictions by Union upon a Contractor's choice of materials or design, nor, regardless of source or location, upon the full use and utilization, of equipment, machinery, packaging, precast, prefabricated, prefinished, or preassembled materials, tools or other labor saving devices, subject to the application of the California Public Contract and Labor Codes. Generally, the onsite installation or application of such items shall be performed by the craft having jurisdiction over such work.

  • Freedom to Use Ideas Subject to Section 9 and Client’s rights in Client Information and notwithstanding anything to the contrary contained in this Agreement or an Order Form, the ideas, methods, concepts, know-how, structures, techniques, inventions, developments, processes, discoveries, improvements and other information and materials developed in and during the course of any Order Form may be used by Red Hat, without an obligation to account, in any way Red Hat deems appropriate, including by or for itself or its clients or customers.

  • Use of Name (a) The Sub-Adviser hereby consents to the use of its name and the names of its affiliates in the Fund’s disclosure documents, shareholder communications, advertising, sales literature and similar communications. The Sub-Adviser shall not use the name or any tradename, trademark, trade device, service xxxx, symbol or any abbreviation, contraction or simulation thereof of the Adviser, the Trust, the Fund or any of their affiliates in its marketing materials unless it first receives prior written approval of the Trust and the Adviser.

  • COMPLIANCE WITH NEW YORK STATE INFORMATION SECURITY BREACH AND NOTIFICATION ACT Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law Section 899-aa; State Technology Law Section 208).

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

Time is Money Join Law Insider Premium to draft better contracts faster.