Obligations of Provider 3.1 Provider shall submit information to InterWest, upon request, as may be required to support InterWest’s provider credentialing process. Provider warrants and represents that all such information is true, accurate, and complete and shall notify InterWest promptly of any changes.
Obligations of the data exporter The data exporter agrees and warrants:
Obligations of the University (a) organizes the doctoral studies;
OBLIGATIONS OF THE CONTRACTOR AND SURETY The Contractor and the Surety, in consideration of the award of this Contract to the Contractor, jointly and severally for themselves, their heirs, executors, administrators, and successors or assigns, hereby guarantee, covenant and agree to and with the Owner that:
Obligations of Parties Nothing herein shall relieve a Party of its obligations under the Federal Rules, the Bankruptcy Rules, the Federal Rules of Evidence, and the Local Rules, or under any future stipulations and orders, regarding the production of documents or the making of timely responses to Discovery Requests in connection with the Cases.
OBLIGATIONS OF THE DEVELOPER In addition to and not in derogation or substitution of any of its other obligations under this Agreement, the Developer shall have the following obligations:
File Management and Record Retention relating to CRF Eligible Persons or Households Grantee must maintain a separate file for every applicant, Eligible Person, or Household, regardless of whether the request was approved or denied.
Obligations of Registry Operator to TLD Community Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.
Obligations of the Consultant A. CONSULTANT shall perform as required by this AGREEMENT. CONSULTANT also warrants on behalf of itself and all subcontractors engaged for the performance of this AGREEMENT.
Obligations of the Department a. The Department shall notify Business Associate of a) any limitation in any applicable Notice of Privacy Practices that would affect the use or disclosure of PHI by the Business Associate and b) any changes, revocations, restrictions or permissions by an individual to the use and disclosure of his/her PHI to which the Department has agreed, to the extent such restrictions or limitations may affect the performance of Business Associate’s services on behalf of the Department.