Collaborative Practice Agreements Sample Clauses

Collaborative Practice Agreements. Collaborative practice agreements shall describe in detail services that a pharmacist may perform for a patient [that provides informed consent], including but not limited to:
AutoNDA by SimpleDocs
Collaborative Practice Agreements. References
Collaborative Practice Agreements. Required Agreement Terms for All Practice Settings; Duties; Biennial Renewal; Termination; Agreement to be Filed in Primary Practice Setting; and Employment Relationships (1) A collaborative practice agreement must be a written and signed agreement between an authorized pharmacist with training and experience relevant to the scope of the collaborative practice and a supervising physician that defines the collaborative practice in which the authorized pharmacist and supervising physician propose to engage. The collaborative practice must be within the scope of the supervising physician’s practice. In the community pharmacy setting, the CDTM agreement shall include: (a) a written referral of a specific patient from the supervising physician to an authorized pharmacist; and (b) the written consent of the patient to the CDTM agreement.
Collaborative Practice Agreements. Collaborative practice agreements delineate a relationship among an NP, a physician (or group of physicians) and an employing organization to describe how team members work together and define the responsibility and accountability of each team member within the context of practice. Collaborative practice agreements are used to guide decisions that enable the health care providers to work together to use their separate and shared knowledge and skills to provide optimal patient-centered care. NPs at St. Michael’s must develop collaborative practice agreements to define their scope of practice within the clinical environment and those agreements must define and describe: • Patients included in the NP’s practice; • Clinical responsibilities and accountabilities of the NP; • Scope of practice including identification of controlled act procedures and authorized activities (laboratory and diagnostic testing) and medical directives (if required); • General indications for NP communication or consultation with physician partner(s). (Consultation is an explicit request by an NP to another health care professional to provide advice and/or participate in the care of a patient and is required when NPs encounter patient care needs beyond the NP legal scope of practice, beyond their individual competencies, or when patient care would benefit CNO, 2011)). • Description of responsibilities within non-clinical domains of practice consistent with the model of practice for NPs at St. Michael’s (Education, Research and Administration). Please see Appendix 3: a template to guide the development of collaborative practice agreements. Further assistance is available from the Professional Practice Leader for Nurse Practitioners. Once developed and agreed-upon by the NP, physician partners, and Program Director, the Collaborative Practice Agreement must be reviewed by the Professional Practice Leaders for NPs, the Director of Nursing Practice and Education and approved by the Professional Practice Executive Committee. Once approved, the CPAs should be signed by the NP(s), Chief of Division/Service and Program Director and circulated to the Medical Advisory Committee for information. CPAs are developed within the first 3 months of hire, reviewed after one year of practice and then every three years thereafter. As well, they may be updated to reflect changes in scope of practice, hospital policy and/or other relevant clinical requirements. If there are no changes when a CPA is renewed...
Collaborative Practice Agreements. Within 60 days from the ratification of this Agreement, the University will designate a contact person for APNs to serve as an information resource regarding issues such as the provision of documents pertaining to Collaborative Practice Agreements, as well as other issues relating to an APN's practice at the University.

Related to Collaborative Practice Agreements

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Sublicense Agreements Sublicenses under this Section 2.3 shall be granted only pursuant to written agreements, which shall be subject to and consistent with the terms and conditions of this Agreement. Such Sublicense agreements shall contain, among other things, provisions to the following effect: 2.3.2.1 all provisions necessary to ensure Licensee’s ability to comply with Licensee’s obligation under or not violate the provisions of Sections 4.4, 4.5, 4.6, 5.1, 5.3, 5.4, 8.1 and 11.1; 2.3.2.2 a section substantially the same as Article 9 (Indemnification), which also shall state that the Indemnitees (as defined in Section 9.1) are intended third party beneficiaries of such Sublicense agreement for the purpose of enforcing such indemnification; 2.3.2.3 in the event of termination of the license set forth in Section 2.1.1 above (in whole or in part (e.g., termination of the license as to a Licensed Product or in a particular country)), any existing Sublicense shall terminate to the extent of such terminated license; provided, however, that, for each Sublicensee, upon termination of the license, if the Sublicensee is not then in breach of the Sublicense agreement such that Licensee would have the right to terminate such Sublicense agreement, such Sublicensee shall have the right to obtain a license from Harvard on the same terms and conditions as set forth herein, which shall not impose any representations, warranties, obligations or liabilities on Harvard that are not included in this Agreement, provided that (a) the scope of the license granted directly by Harvard to such Sublicensee shall be coextensive with the scope of the license granted by Licensee to such Sublicensee, (b) if the Sublicense granted to such Sublicensee was non-exclusive, such Sublicensee shall not have the right to participate in the prosecution or enforcement of the Patent Rights under the license granted to it directly by Harvard and (c) if there are more than one Sublicensee, each Sublicensee that is granted a direct license shall be responsible for a pro rata share of the reimbursement due under Section 6.2.3 of this Agreement (based on the number of direct licenses under the Patent Rights in effect on the date of reimbursement); 2.3.2.4 the Sublicensee shall only be entitled to sublicense its rights under such Sublicense agreement on the terms set forth in this Section 2.3; and 2.3.2.5 the Sublicensee shall not be entitled to assign the Sublicense agreement without the prior written consent of Harvard, except that Sublicensee may assign the Sublicense agreement to a successor in connection with the merger, consolidation or sale of all or substantially all of its assets or that portion of its business to which the Sublicense agreement relates; provided, however, that any permitted assignee agrees in writing in a manner reasonably satisfactory to Harvard to be bound by the terms of such Sublicense agreement.

  • Supply Agreements For a period of three years from the consummation of the IPO, Odetics shall not unilaterally terminate or assign its guarantee obligation with respect to any supply agreement pursuant to which it has guaranteed the performance by ATL of ATL's obligations, unless such suppliers have consented to the termination or assignment of such guarantee.

  • License Agreements (a) Each Borrower and Guarantor shall (i) promptly and faithfully observe and perform all of the material terms, covenants, conditions and provisions of the material License Agreements to which it is a party to be observed and performed by it, at the times set forth therein, if any, (ii) not do, permit, suffer or refrain from doing anything that could reasonably be expected to result in a default under or breach of any of the terms of any material License Agreement, (iii) not cancel, surrender, modify, amend, waive or release any material License Agreement in any material respect or any term, provision or right of the licensee thereunder in any material respect, or consent to or permit to occur any of the foregoing; except, that, subject to Section 9.19(b) below, such Borrower or Guarantor may cancel, surrender or release any material License Agreement in the ordinary course of the business of such Borrower or Guarantor; provided, that, such Borrower or Guarantor (as the case may be) shall give Agent not less than thirty (30) days prior written notice of its intention to so cancel, surrender and release any such material License Agreement, (iv) give Agent prompt written notice of any material License Agreement entered into by such Borrower or Guarantor after the date hereof, together with a true, correct and complete copy thereof and such other information with respect thereto as Agent may request, (v) give Agent prompt written notice of any material breach of any obligation, or any default, by any party under any material License Agreement, and deliver to Agent (promptly upon the receipt thereof by such Borrower or Guarantor in the case of a notice to such Borrower or Guarantor and concurrently with the sending thereof in the case of a notice from such Borrower or Guarantor) a copy of each notice of default and every other notice and other communication received or delivered by such Borrower or Guarantor in connection with any material License Agreement which relates to the right of such Borrower or Guarantor to continue to use the property subject to such License Agreement, and (vi) furnish to Agent, promptly upon the request of Agent, such information and evidence as Agent may reasonably require from time to time concerning the observance, performance and compliance by such Borrower or Guarantor or the other party or parties thereto with the material terms, covenants or provisions of any material License Agreement. (b) Each Borrower and Guarantor will either exercise any option to renew or extend the term of each material License Agreement to which it is a party in such manner as will cause the term of such material License Agreement to be effectively renewed or extended for the period provided by such option and give prompt written notice thereof to Agent or give Agent prior written notice that such Borrower or Guarantor does not intend to renew or extend the term of any such material License Agreement or that the term thereof shall otherwise be expiring, not less than sixty (60) days prior to the date of any such non-renewal or expiration. In the event of the failure of such Borrower or Guarantor to extend or renew any material License Agreement to which it is a party, Agent shall have, and is hereby granted, the irrevocable right and authority, at its option, to renew or extend the term of such material License Agreement, whether in its own name and behalf, or in the name and behalf of a designee or nominee of Agent or in the name and behalf of such Borrower or Guarantor, as Agent shall determine at any time that an Event of Default shall exist or have occurred and be continuing. Agent may, but shall not be required to, perform any or all of such obligations of such Borrower or Guarantor under any of the License Agreements, including, but not limited to, the payment of any or all sums due from such Borrower or Guarantor thereunder. Any sums so paid by Agent shall constitute part of the Obligations. (c) No Borrower or Guarantor shall assign, sell, mortgage, lease, transfer, pledge, hypothecate, grant a security interest in or lien upon, encumber, grant an exclusive or non-exclusive license relating to any Intellectual Property, or otherwise dispose of any Intellectual Property, in each case without the prior written consent of Agent, except that any Borrower or Guarantor may, after written notice to Agent, grant a non-exclusive license relating to any Intellectual Property to another Borrower or Guarantor in the ordinary course of business.

  • Development License Subject to the terms and conditions of this XXXX, You are licensed to perform an installation of the SOFTWARE for an unlimited use in designing, testing and creating Developed Software by unlimited Developers on one or more computers.

  • Supply Agreement Seller and Buyer, or their Affiliates, shall have executed the Supply Agreement.

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services

  • HHSC Agreements A. To pay the Contractor for services provided under the Contract type specified in Section I of this Contract in amounts and under conditions determined by HHSC as defined in this Contract, the applicable Contractor manual, handbook, policy letter or program rules and standards and in accordance with applicable laws and regulations for all eligible persons receiving such services under Title XIX and or Title XX. B. To pay the Contractor within time limits set by HHSC and in accordance with applicable laws and regulations after a proper claim for payment is submitted and approved for payment in accordance with HHSC's Claims Administrator billing guidelines. C. To adjust payments to the Contractor to compensate for prior overpayment or underpayment. D. To give the Contractor reasonable notice of any impending change in its status as a participating Contractor, except that nothing in this section shall be construed to deny HHSC the right, for failure to comply with this Contract or regulations published in the Texas Register, to terminate this Contract, suspend payments or take any other legal remedy available to HHSC. E. To provide a hearing, in accordance with TAC, Title 1, Part 15, Chapter 357, Subchapter I, or its successor to the Contractor in the event HHSC imposes an adverse action on the Contractor under this Contract. F. To make available to the Contractor the applicable Contractor manual and any changes to that manual that change the requirements for participation. G. That a religious organization that contracts with HHSC does not by contracting with HHSC lose the exemption provided under Section 702 of the Civil Rights Act [42 U.S.C. §2000E-1(a)] regarding employment practices. A religious or charitable organization is eligible to be a Contractor on the same basis as any other private organization. The Contractor retains its independence from state and local governments, including the Contractor's control over the definition, development, practice and expression of its charitable or religious beliefs. Except as provided by federal law, HHSC shall not interpret this Contract to require a charitable or religious organization to alter its form of internal governance or remove religious art, icons, scripture or other symbols. Furthermore, if a religious or charitable organization segregates the government funds provided under this Contract, then only the financial assistance provided by these funds will be subject to audit. However, neither HHSC's selection of a charitable or faith-based Contractor nor the expenditure of funds under this Contract is an endorsement of the Contractor's charitable or religious character, practices or expression. The purpose of this Contract is the provision of community services. No state expenditures have as their objective the funding of sectarian worship, instruction or proselytization, and no state funds shall be expended for these purposes.

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