Non-Formulary Approval Process Sample Clauses

Non-Formulary Approval Process a. The Provider shall create a written process for the approval of nonformulary medication requests. In creating this process, the Provider shall take into account feedback from the medical and behavioral health vendor and shall submit the finalized process to the DDOC for review and approval before the process is put into effect.
AutoNDA by SimpleDocs

Related to Non-Formulary Approval Process

  • Regulatory Approval 25.1 The Parties understand and agree that this Agreement and any amendment or modification hereto will be filed with the Commission for approval in accordance with Section 252 of the Act and may thereafter be filed with the FCC. The Parties believe in good faith and agree that the services to be provided under this Agreement are in the public interest. Each Party covenants and agrees to fully support approval of this Agreement by the Commission or the FCC under Section 252 of the Act without modification.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Annual Production Program document describing the forecasts for Production and handling of Oil, Gas, water, special fluids, and waste arising from the Production process of each Development Area or Field.

  • Motion for Preliminary Approval The Parties agree to jointly prepare and file a motion for preliminary approval (“Motion for Preliminary Approval”) that complies with the Court’s current checklist for Preliminary Approvals.

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • School Improvement Plans The School shall develop and implement a School Improvement Plan as required by section 1002.33(9)(n), Florida Statutes and applicable State Board of Education Rules or applicable federal law.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

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