Layoff List A list of all ASF Members laid-off within the prior three (3) year period shall be maintained by the System office. The list shall indicate if an individual has recall rights. The Association President shall be provided a copy of the list, and notified promptly of changes.
Layoff Lists The names of employees who have been laid off or demoted in lieu of layoff, or whose position has been reallocated down shall be placed on a Seniority Unit Layoff List for the seniority unit, classification, geographic location and employment condition from which they were laid off or demoted in lieu of layoff in order of Classification Seniority. Employees may also indicate, in writing, other geographic locations for which they are available. Employees may change their availability at any time through written notice to the Employer. Unless removed via 1-4, names shall be retained on the layoff list for a minimum of one (1) year or for a period of time equal to the employee's State Seniority, to a maximum of four (4) years. A copy of such list shall be made available to the Council upon request. Upon request, the names of employees who have been laid off or demoted in lieu of layoff, or whose position has been reallocated down shall be placed on a bargaining unit layoff list for the bargaining unit, classification, geographic location, and employment condition from which they were laid off or demoted in lieu of layoff in order of Classification Seniority. Employees may also indicate, in writing, other geographic locations for which they are available. Employees may change their availability at any time through written notice to the Employer. Unless removed via 1-4, names shall be retained on the layoff list for a minimum of one (1) year or for a period of time equal to the employee's State Seniority, to a maximum of four (4) years. A copy of such list shall be made available to the Council upon request. Employees shall be removed from all layoff lists for any of the following reasons:
Removal from Layoff Lists Employees shall be removed from all layoff lists for any of the following reasons:
DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.
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.
Layoff Notification The Appointing Authority shall send a layoff notice to the employee in the position to be eliminated. The layoff notice shall be provided to the employee in person whenever practicable and shall otherwise be sent by priority mail. At the Appointing Authority’s discretion, an employee under notice of permanent layoff may be granted up to one hundred and sixty (160) hours of paid leave, ending at the date of layoff. Hours of leave may be granted at any time throughout the layoff notice period and shall not be subject to the Application and Reinstatement provisions of Article 10. Upon request, an Appointing Authority shall provide an employee on notice of layoff assistance in searching for State employment. Provisional, temporary and emergency employees shall be terminated before any layoff of probationary or permanent employees in the same class, employment condition and geographic location/principal place of employment. Provisional employees shall be separated in inverse order of the date of their provisional appointment.
When Lift Required The passenger/materials lift shall be in operation from the date of commencement of formwork erection above the floor level of the fifth storey when counted from the lowest adjacent street level. Floor level means that stage of construction which, in the completed building, would constitute the walking surface of each particular floor level.
DRUG-FREE WORKPLACE REQUIREMENTS Contractor will comply with the requirements of the Drug-Free Workplace Act of 1990 and will provide a drug-free workplace by taking the following actions:
Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.
TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.
