Vehicle Requirements The following shall be considered minimum Vehicle requirements. The Authorized User shall include supplemental required specifications for Vehicles specified in a Mini-Bid. Unless otherwise indicated, all items specified which are listed on the OEM Pricelist as standard or optional equipment shall be factory installed and operative. Vehicles delivered to an Authorized User in a condition considered to be below retail customer acceptance levels will not be accepted. Items which determine this acceptance level shall include, but not be limited to, the general appearance of the interior and exterior of the vehicle for completeness and quality of workmanship, lubrication and fluid levels, with any leaks corrected, mechanical operation of the vehicle and all electrical components operational. Product specified to be furnished and installed which is not available through the OEM shall conform to the standards known to that particular industry, both product and installation.
Agreement Requirements This agreement will be issued to cover the Janitorial Service requirements for all State Agencies and shall be accessible to any School District, Political Subdivision, or Volunteer Fire Company.
Minimum Vendor Legal Requirements Vendor shall remain aware of and comply with this Agreement and all local, state, and federal laws governing the sale of products/services offered by Vendor under this contract. Such applicable laws, ordinances, and policies must be complied with even if not specified herein.
Support Requirements If there is a dispute between the awarded vendor and TIPS Member, TIPS or its representatives may assist, at TIPS sole discretion, in conflict resolution or third party (mandatory mediation), if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded vendors TIPS project files, documentation and correspondence. TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.
Contractor Requirements The Firm shall be construed, during the entire term of this contract, to be an independent contractor. Nothing in this contract is intended to nor shall be construed to create an employer- employee relationship, or a joint venture relationship. The Firm represents that it is qualified to perform the duties to be performed under this contract and that it has, or will secure, if needed, at its own expense, applicable personnel who are qualified to perform the duties required under this contract. Such personnel shall not be deemed in any way, directly or indirectly, expressly or by implication, to be employees of the District. Any person assigned by the firm to perform the services hereunder shall be the employee or a subcontractor of the Firm, who shall have the sole right to hire and discharge its employee or subcontractors. The Firm or its subcontractors shall pay, when due, all salaries and wages of their employees and accepts exclusive responsibility for the payment of federal income tax, social security, unemployment compensation and any other withholdings that may be required. Neither the Firm, its subcontractors nor their employees are entitled to state retirement or leave benefits. It is further understood that the consideration expressed herein constitutes full and complete compensation for all services and performance hereunder, and that any sum due and payable to the Firm shall be paid as a gross sum with no withholdings or deductions being made by the District for any purpose from said contract sum, except as permitted in paragraphs 16, 17 and 18.
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.
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.
