Abuse and Neglect of Children and Vulnerable Adults: Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).
Trade Errors The Sub-Advisor will notify the Manager of any Trade Error(s), regardless of materiality, promptly upon the discovery such Trade Error(s) by the Sub-Advisor. Notwithstanding Section 5, the Sub-Advisor shall be liable to the Manager, the Fund or its shareholders for any loss suffered by the Manager or the Fund resulting from Trade Errors due to negligence, misfeasance, or disregard of duties of the Sub Advisor or any of its directors, officers, employees, agents (excluding any broker-dealer selected by the Sub-Advisor), or affiliates. For purposes under this Section 6, “Trade Errors” are defined as errors due to (i) erroneous orders by the Sub-Advisor for the Series that result in the purchase or sale of securities that were not intended to be purchased or sold; (ii) erroneous orders by the Sub-Advisor that result in the purchase or sale of securities for the Series in an unintended amount or price; or (iii) purchases or sales of financial instruments which violate the investment limitations or restrictions disclosed in the Fund’s registration statement and/or imposed by applicable law or regulation (calculated at the Sub-Advisor’s portfolio level), unless otherwise agreed to in writing.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
Mail Order Catalog Warnings In the event that, the Settling Entity prints new catalogs and sells units of the Products via mail order through such catalogs to California consumers or through its customers, the Settling Entity shall provide a warning for each unit of such Product both on the label in accordance with subsection 2.4 above, and in the catalog in a manner that clearly associates the warning with the specific Product being purchased. Any warning provided in a mail order catalog shall be in the same type size or larger than other consumer information conveyed for such Product within the catalog and shall be located on the same display page of the item. The catalog warning may use the Short-Form Warning content described in subsection 2.3(b) if the language provided on the Product label also uses the Short-Form Warning.
Policy Grievance – Employer Grievance The Employer may institute a grievance alleging a general misinterpretation or violation by the Union or any employee by filing a written grievance with the Bargaining Unit President, with a copy to the Labour Relations Officer within twenty (20) days after the circumstances have occurred. A meeting will be held between the parties within ten (10) days. The Union shall reply within ten (10) days after the meeting, and failing settlement, the matter may be referred to arbitration. (a) Where a difference arises between the parties relating to the interpretation, application or administration of this Agreement, including any questions as to whether a matter is arbitrable, or where an allegation is made that this Agreement has been violated, either of the parties may, after exhausting the grievance procedure established by this Agreement, notify the other party in writing of its decision to submit the difference or allegation to arbitration, and the notice shall contain the name of the first party's appointee to an Arbitration Board. The recipient of the notice shall, within ten (10) days, inform the other party of the name of its appointee to the Arbitration Board. The two appointees so selected shall within ten (10) days of the appointment of the second of them, appoint a third person who shall be the Chairperson. If the recipient of the notice fails to appoint a nominee, or if the two nominees fail to agree upon a Chairperson within the time limit, the appointment shall be made by the Minister of Labour for Ontario upon the request of either party. (b) Within thirty (30) calendar days of the receipt of notice referred to in Article 8.12(a) above, either party may require a process for a sole arbitrator where the grievance concerns: i) a job posting ii) a short term layoff
Policy Grievance Where either Party disputes the general application, interpretation or alleged violation of an article of this Agreement, the dispute shall be discussed initially with the Employer or the Union, as the case may be, within thirty (30) days of the occurrence. Where no satisfactory agreement is reached, either Party may submit the dispute to arbitration, as set out in Article 10.
System Description The wet detention basin is designed to trap 80% of sediment in runoff and maintain pre-development downstream peak flows. The basin has two forebays (smaller ponds) located at the low end of two grass xxxxxx. In addition to runoff conveyance, the grass xxxxxx also allow infiltration and filtering of pollutants, especially from smaller storms. The forebays are each 4 feet deep. They are connected to the main pool by 18 and 24-inch metal pipes that outlet onto a rock chute. The forebays will trap coarse sediments in runoff, such as road sands, thus reducing maintenance of the main basin. The main pool will trap the finer suspended sediment. To do this, the pond size, water level and outlet structures must be maintained as specified in this Agreement (see Figures 1, 2 and 3). The main basin receives runoff from a 67.1 acre drainage area (41.2 acres within the subdivision and 25.9 acres off-site drainage coming from the east). During high rainfall or snow melt events, the water level will temporarily rise and slowly drain down to the elevation of the control structure. The water level is controlled by a 12-inch concrete pipe extending through the berm in the northwest corner of the basin (see Figures 1 and 3). On the face of the 12-inch pipe, there is metal plate with a 3-inch drilled hole (orifice) with stone in front of it. This orifice controls the water level and causes the pond to temporarily rise during runoff events. Washed stone (1- 2” diameter) is placed in front of the orifice to prevent clogging. High flows may enter the grated concrete riser or flow over the rock lined emergency spillway. “As-built” construction drawings of the basin, showing actual dimensions, elevations, outlet structures, etc. will be recorded as an addendum(s) to this agreement within 60 days after [Municipality Name] accepts verification of construction from the project engineer.
Hot Weather Guidelines For the purposes of site based discussions regarding the need to plan and perform work during expected periods of hot weather, the following issues shall be considered in conjunction with proper consideration of Occupational Health and Safety issues.
General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:
Verification of Coverage Prior to beginning any work under this Agreement, Consultant shall furnish City with certificates of insurance and with original endorsements effecting coverage required herein. The certificates and endorsements for each insurance policy are to be signed by a person authorized by that insurer to bind coverage on its behalf. The City reserves the right to require complete, certified copies of all required insurance policies at any time.
