Collaborative Practice Agreements Sample Clauses

Collaborative Practice Agreements. (a) 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. 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. 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
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 shall be granted only pursuant to written agreements, which shall be subject and subordinate to the terms and conditions of this Agreement. Such Sublicense agreements shall contain, among other things, provisions to the following effect:

  • 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.

  • 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 We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

  • Pharmacovigilance Agreement Within [***] after the Effective Date, BMS and the Company (under the guidance of their respective Pharmacovigilance Departments, or equivalent thereof) shall define and finalize the responsibilities the Parties shall employ to protect patients and promote their well-being in connection with the use of the Licensed Compound(s) until such time that all pharmacovigilance responsibilities have transferred from BMS to Company. These responsibilities shall include mutually acceptable guidelines and procedures for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of adverse event reports, pregnancy reports, and any other information concerning the safety of any Licensed Compound(s). Such guidelines and procedures shall be in accordance with, and enable the Parties and their Affiliates to fulfill, local and international regulatory reporting obligations to government authorities. Furthermore, such agreed procedures shall be consistent with relevant International Council for Harmonization (ICH) guidelines, except where said guidelines may conflict with existing local regulatory safety reporting requirements, in which case local reporting requirements shall prevail. Until such guidelines and procedures are set forth in a written agreement between the Parties (hereafter referred to as the “Pharmacovigilance Agreement”), the Party responsible for pharmacovigilance prior to execution of this Agreement shall have sole Pharmacovigilance responsibility for the Licensed Compound(s) subject to all applicable regulations and guidelines. In the event that this Agreement is terminated, the Parties agree to implement the necessary procedures and practices to ensure that any outstanding pharmacovigilance reporting obligations are fulfilled. Certain information marked as [***] has been excluded from this exhibit because it is both (i) not material and (ii) would be competitively harmful if publicly disclosed.

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