COLLABORATIVE PRACTICE AGREEMENT Sample Clauses

COLLABORATIVE PRACTICE AGREEMENT terms and provisions. A collaborative practice agreement must include the following information:
AutoNDA by SimpleDocs
COLLABORATIVE PRACTICE AGREEMENT. Under this collaborative practice agreement, UConn Health Anticoagulation Specialist(s), according to and in compliance with section 91 of Public Act 10-117 and Connecticut General Statues sSB186/File No. 213 “An ACT Concerning Collaborative Drug Therapy Management and Policies”, may design, implement, and monitor a therapeutic drug plan intended to manage anticoagulation therapies. Anticoagulation Specialists may sign patient summaries for assisted living facilities as well as orders for visiting nurses. Services offered by the Anticoagulation Specialist may include education on disease state and lifestyle modification, in addition to the drug therapy services listed above. Written educational materials and patient specific information may be provided to improve quality of care. The Anticoagulation Specialist(s) may initiate, discontinue, or adjust anticoagulation therapies in accordance with current treatment guidelines, may order laboratory tests appropriate to the disease or drug therapy. Education at office visits shall include appropriate counseling on all new medications. The results of all lab tests ordered under the protocol shall be reviewed and managed by the Anticoagulation Specialist(s) to assess efficacy of treatment and necessity for medication and/or therapeutic lifestyle change. Lab results will be relayed to clinic patients by a patient-specific predetermined method which may include face-to-face encounter, scheduled secure telephone/video visit, or written communication. Any lab outliers that require further investigation will be sent to the referring provider and/or PCP as appropriate and the patient will be told to contact that LIP immediately. If the LIP is not available, the patient will be sent to the UConn Health Emergency Department. A patient whose drug therapy is managed under this agreement must have established care with a provider within UConn Health and all aspects of the patient’s anticoagulation medication management will be followed in collaboration with the patient’s referring provider (or primary care as necessary). In addition, the patient must be seen by their UConn Health provider at least once per year, in addition to which cases may be reviewed with clinic medical directors as needed. All issues outside of the scope of anticoagulation medication management shall be referred to the patient’s primary care provider, daily supervising LIP or medical director(s). The Anticoagulation Specialist(s) will assure documentati...
COLLABORATIVE PRACTICE AGREEMENT adoption authorized. A school administrative unit or an approved private school may authorize adoption of a collaborative practice agreement for the purposes of stocking and administering epinephrine autoinjectors as provided under this section. The administration of an epinephrine autoinjector in accordance with this section is not the practice of medicine. [PL 2013, c. 526, §1 (NEW).]
COLLABORATIVE PRACTICE AGREEMENT adoption authorized. A school administrative unit or an approved private school may authorize adoption of a collaborative practice agreement for the purposes of stocking, possessing and administering naloxone hydrochloride as provided under this section. The administration of naloxone hydrochloride in accordance with this section is not the practice of medicine. [PL 2021, c. 115, §1 (NEW).]
COLLABORATIVE PRACTICE AGREEMENT. Under this collaborative practice agreement, UConn HealthXxxx Xxxxxxx Hospital Pharmacists, according to and in compliance with Section 91 of Public Act 10-7 and Connecticut General Statutes sec 20-631 “An Act Concerning Collaborative Practice Between Physicians and Pharmacists”, may design, implement, and monitor a therapeutic drug plan intended to manage IV Vancomycin therapy upon receipt of an order from the licensed provider to the Pharmacist for IV Vancomycin dosing. The specific services provided by the Pharmacists and the methods for providing these services are described in detail in this protocol document
COLLABORATIVE PRACTICE AGREEMENT. This collaborative practice agreement is an expanded scope of practice of the pharmacist identified herein. Upon approval of this agreement by the IWK Medical Advisory Committee, the Nova Scotia College of Pharmacists will approve the practice setting prior to the Collaborative Practice Agreement taking effect under section 3f of the Pharmacy Practice Regulations.
COLLABORATIVE PRACTICE AGREEMENT. SSM Physician
AutoNDA by SimpleDocs
COLLABORATIVE PRACTICE AGREEMENT. NOTICE OF INTENT advanced practice registered nurse by the. Requirements for Provider Type 09 Certified Registered. NYS Nursing Practice Information Collaborative Practice. 4723 8 04 Standard care arrangement for a certified nurse. How Does Nurse Practitioner Authority Vary By State. NURSE PROTOCOL AGREEMENT Georgia. Nurse practitioners can practice without physician. IMPORTANT Read the Complete Instructions on the Reverse. Collaborative Practice Agreement Protocols. Should a Written Collaborative Practice Agreement with a. Prescriptive Authority IL Society for Advanced Practice. Nurse Practitioner Jobs Patient Population. ADVANCED PRACTICE REGISTERED NURSE COLLABORATIVE AGREEMENTS.

Related to COLLABORATIVE PRACTICE AGREEMENT

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

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

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

  • Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

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

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

  • Quality Agreement If appropriate or if required by Applicable Law, the parties will also agree upon a Quality Agreement containing quality assurance provisions for the Manufacture of Product (“Quality Agreement”), which agreement will also be attached to the applicable Work Order and incorporated by reference in the Work Order.

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

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

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