Transitional Semi-Private Provision Sample Clauses

Transitional Semi-Private Provision. The Parties agreed to eliminate semi-private and private hospital room coverages from the Plan, effective the first of the month following ratification of the 1996 - 1999 Agreement. All Employees were advised that this coverage is no longer available and if an Employee wants a semi-private or private room, they will pay for same directly. However, where Area Hospitals xxxx Employees for semi-private or private rooms without the Employee having requested same, those bills will be paid by the Employer on presentation of invoices to the Human Resources and Organizational Development Division, and the issue of improper bills will be taken up by the Employer and the Hospital involved. The issue of improper billing will not exist where only semi-private/private rooms are available and the carrying agency can legally force the premium for the room to be paid. In such instances the premium for the room will be paid by the Employer. This arrangement only applies to semi- private/private rooms and will not be extended to current/future daily fees for chronically ill patients, or other accommodation charges which are not contemplated by our Plan design.
AutoNDA by SimpleDocs

Related to Transitional Semi-Private Provision

  • Transitional Period At the end of the transitional period as defined in Article 10(2) of the Directive, the contracting parties shall cease to apply the withholding/retention tax and revenue sharing provided for in this Agreement and shall apply in respect of the other contracting party the automatic exchange of information provisions in the same manner as is provided for in Chapter II of the Directive. If during the transitional period either of the contracting parties elects to apply the automatic exchange of information provisions in the same manner as is provided for in Chapter II of the Directive it shall no longer apply the withholding/retention tax and the revenue sharing provided for in Article 9 of this Agreement.

  • Transitional (a) The parties recognise that certain determinations (for example, the annualised amount of HCF and HCV) may have been made to date in respect of a current Financial Year before the variations in this deed were agreed.

  • Transition Provisions Any person engaged as an apprentice at the date this Agreement commenced operation shall be deemed to be an apprentice for all purposes of this Agreement until the completion or cancellation of their apprenticeship contract.

  • ATTACHMENT E BUSINESS ASSOCIATE AGREEMENT This Business Associate Agreement (“Agreement”) is entered into by and between the State of Vermont Agency of Human Services, operating by and through its Department of Vermont Health Access (“Covered Entity”) and OptumInsight, Inc. (“Business Associate”) as of June 6, 2014 (“Effective Date”). This Agreement supplements and is made a part of the contract/grant to which it is attached. Covered Entity and Business Associate enter into this Agreement to comply with standards promulgated under the Health Insurance Portability and Accountability Act of 1996 (“HIPAA”), including the Standards for the Privacy of Individually Identifiable Health Information, at 45 CFR Parts 160 and 164 (“Privacy Rule”), and the Security Standards, at 45 CFR Parts 160 and 164 (“Security Rule”), as amended by Subtitle D of the Health Information Technology for Economic and Clinical Health Act (HITECH), and any associated federal rules and regulations. The parties agree as follows:

  • Transition Period Due to the nature of our purchasing process, the District often requires an existing service provider to continue to provide goods and/or services while the District is in the process of advertising, evaluating, and awarding a contract for the provision of the same goods and/or services in the future. To accommodate this process, the Contractor shall agree to maintain the same terms and conditions set forth in this Agreement for a period up to ninety (90) days after the automatic termination of this Agreement at the end of its term, if requested by the District, as a transition period. In addition, if the Contractor is not the successful bidder for a future solicitation for the same or similar services, he or she shall agree to provide the same goods and/or services provided in this Agreement for a period up to ninety (90) days to allow for an orderly transition to the new provider. The District and the Contractor may mutually agree to a longer transition period.

  • Transition Seller will not take any action that is designed or intended to have the effect of discouraging any lessor, licensor, customer, supplier, or other business associate of the Company from maintaining the same business relationships with the Company after the Closing as it maintained with the Company prior to the Closing. The Seller will refer all customer inquiries relating to the business of the Company to the Purchaser from and after the Closing.

  • Transitional provision Schedule 3.2 contains a schedule of certain letters of credit issued for the account of the Borrower prior to the Closing Date. Subject to the satisfaction of the conditions contained in Sections 5.1 and 5.2, from and after the Closing Date such letters of credit shall be deemed to be Letters of Credit issued pursuant to this Article III.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Service Level Agreement Subject to the terms and conditions of this Agreement, Bank agrees to perform the custody services provided for under this Agreement in a manner that meets or exceeds any service levels as may be agreed upon by the parties from time to time in a written document that is executed by both parties on or after the date of this Agreement, unless that written document specifically states that it is not contractually binding. For the avoidance of doubt, Bank’s Service Directory shall not be deemed to be such a written document.

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