Authority and Purpose Pursuant to 18 V.S.A. § 9410, the GMCB maintains certain health care claims and eligibility data within VHCURES to enable it to carry out its statutory duties, including A. determining the capacity and distribution of existing resources; identifying health care needs and informing health care policy; B. evaluating the effectiveness of intervention programs on improving patient outcomes; C. comparing costs between various treatment settings and approaches; D. providing information to consumers and purchasers of health care; and E. improving the quality and affordability of patient health care and health care coverage. To the extent allowed by HIPAA, the GMCB seeks to make some of this data available as a resource for individuals and entities to continuously review health care utilization, expenditures, and performance in Vermont. The purpose of this Agreement is to specify the conditions under which the GMCB will release VHCURES data, and to ensure that the data is accessed, maintained, used, and disclosed in compliance with all applicable statutory, regulatory, and contractual requirements.
AUTHORITY AND PARTIES In accordance with the National Aeronautics and Space Act (51 U.S.C. § 20113), this Agreement is entered into by the National Aeronautics and Space Administration, located at 000 X Xxxxxx XX, Xxxxxxxxxx, XX 00000 (hereinafter referred to as "NASA") and Xxxxxx Space Systems, Inc., located at 0000 Xxxxxxxx Xx., Xxxxxx, XX 00000 (hereinafter referred to as "Partner" or "Xxxxxx"). NASA and Partner may be individually referred to as a "Party" and collectively referred to as the "Parties."
Description of Vendor Entity and Vendor's Goods & Services If awarded, this description of Vendor and Vendor's goods and services will appear on the TIPS website for customer/public viewing. Technology solutions value-added reseller and installer of all things technology. Please identify the individual who will be primarily responsible for all TIPS matters and inquiries for the duration of the contract. Xxxx Xxxxxxx Primary Contact Title VP of Sales Please enter a valid email address that will definitely reach the Primary Contact. xxxx@xxxxxxxxxx.xxx Numbers only, no symbols or spaces (Ex. 8668398477). The system will auto-populate your entry with commas once submitted which is appropriate and expected (Ex. 8,668,398,477). Please provide the accurate and current phone number where the individual who will be primarily responsible for all TIPS matters and inquiries for the duration of the contract can be reached directly. 0000000000 Numbers only, no symbols or spaces (Ex. 8668398477). The system will auto-populate your entry with commas once submitted which is appropriate and expected (Ex. 8,668,398,477). 0000000000 Numbers only, no symbols or spaces (Ex. 8668398477). The system will auto-populate your entry with commas once submitted which is appropriate and expected (Ex. 8,668,398,477). 0000000000
Consideration of Criminal History in Hiring and Employment Decisions 10.14.1 Contractor agrees to comply fully with and be bound by all of the provisions of Chapter 12T, “City Contractor/Subcontractor Consideration of Criminal History in Hiring and Employment Decisions,” of the San Francisco Administrative Code (“Chapter 12T”), including the remedies provided, and implementing regulations, as may be amended from time to time. The provisions of Chapter 12T are incorporated by reference and made a part of this Agreement as though fully set forth herein. The text of the Chapter 12T is available on the web at xxxx://xxxxx.xxx/olse/fco. Contractor is required to comply with all of the applicable provisions of 12T, irrespective of the listing of obligations in this Section. Capitalized terms used in this Section and not defined in this Agreement shall have the meanings assigned to such terms in Chapter 12T. 10.14.2 The requirements of Chapter 12T shall only apply to a Contractor’s or Subcontractor’s operations to the extent those operations are in furtherance of the performance of this Agreement, shall apply only to applicants and employees who would be or are performing work in furtherance of this Agreement, and shall apply when the physical location of the employment or prospective employment of an individual is wholly or substantially within the City of San Francisco. Chapter 12T shall not apply when the application in a particular context would conflict with federal or state law or with a requirement of a government agency implementing federal or state law.
Governing Law, Regulatory Authority, and Rules The validity, interpretation and enforcement of this Agreement and each of its provisions shall be governed by the laws of the state of New York, without regard to its conflicts of law principles. This Agreement is subject to all Applicable Laws and Regulations. Each Party expressly reserves the right to seek changes in, appeal, or otherwise contest any laws, orders, or regulations of a Governmental Authority.
Limitation on Out-of-State Litigation - Texas Business and Commerce Code § 272 This is a requirement of the TIPS Contract and is non-negotiable. Texas Business and Commerce Code § 272 prohibits a construction contract, or an agreement collateral to or affecting the construction contract, from containing a provision making the contract or agreement, or any conflict arising under the contract or agreement, subject to another state’s law, litigation in the courts of another state, or arbitration in another state. If included in Texas construction contracts, such provisions are voidable by a party obligated by the contract or agreement to perform the work. By submission of this proposal, Vendor acknowledges this law and if Vendor enters into a construction contract with a Texas TIPS Member under this procurement, Vendor certifies compliance.
Authority and Binding Agreement As of the Effective Date, (i) it has the corporate power and authority and the legal right to enter into this Agreement and perform its obligations hereunder; (ii) it has taken all necessary corporate action on its part required to authorize the execution and delivery of the Agreement and the performance of its obligations hereunder; and (iii) the Agreement has been duly executed and delivered on behalf of such Party, and constitutes a legal, valid, and binding obligation of such Party that is enforceable against it in accordance with its terms.
State of California Public Liability and Workers’ Compensation Program A. The Judicial Council has elected to be self-insured for its motor vehicle, aircraft liability and general liability exposures. B. The Judicial Council administers workers’ compensation benefits for its employees through a Third Party agreement.
Formation and Purpose Promptly following the Effective Date, the Parties shall confer and then create the JSC and the IPC, and, optionally, create one or more of the other Committees listed in the chart below. Each Committee shall have the purpose indicated in the chart. To the extent that after conferring both Parties agree to not create a Committee (other than the JSC and the IPC), the creation of such Committee shall be deferred until one Party informs the other Party of its then desire to create the so-deferred Committee, at which point the Parties will thereafter promptly create the so-deferred Committee. Joint Steering Committee (“JSC”) Establish projects for the Bacteriophage Program and establish the priorities, as well as approve budgets for such projects. Approve all subcommittee projects and plans (except for decisions of the IPC). The JSC shall establish budgets not less than on a quarterly basis. Chemistry, Manufacturing and Controls Committee (“CMCC”) Establish project plans and review and approve activities and budgets for chemistry, manufacturing, and controls under the Bacteriophage Program. Regulatory Committee (“RC”) Review and approve all research and development plans and projects, including clinical projects, associated with any necessary regulatory approvals, all associated publications, and all regulatory filings and correspondence relating to gaining regulatory approval for new Ampliphi Products under the Bacteriophage Program; and review and approve itemized budgets with respect to the foregoing. Commercialization Committee (“CC”) Establish project plans and review and approve activities and budgets for Commercialization activities under the Bacteriophage Program. Portions herein identified by [*****] have been omitted pursuant to a request for confidential treatment under Rule 24b-2 of the Securities Exchange Act of 1934, as amended. A complete copy of this document has been filed separately with the Securities and Exchange Commission. Intellectual Property Committee (“IPC”) Evaluate all intellectual property issues in connection with the Bacteriophage Program; review and approve itemized budgets with respect to the foregoing.
File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.
