E-VERIFICATION The Vendor represents and warrants that it will ensure its compliance with the Mississippi Employment Protection Act of 2008, and will register and participate in the status verification system for all newly hired employees. Mississippi Code Annotated §§71-11-1 et seq. The term “employee” as used herein means any person that is hired to perform work within the State of Mississippi. As used herein, “status verification system” means the Illegal Immigration Reform and Immigration Responsibility Act of 1996 that is operated by the United States Department of Homeland Security, also known as the E-Verify Program, or any other successor electronic verification system replacing the E-Verify Program. Vendor agrees to maintain records of such compliance. Upon request of the State and after approval of the Social Security Administration or Department of Homeland Security when required, Vendor agrees to provide a copy of each such verification. Vendor further represents and warrants that any person assigned to perform services hereafter meets the employment eligibility requirements of all immigration laws. The breach of this agreement may subject Vendor to the following: termination of this contract for goods or services and ineligibility for any state or public contract in Mississippi for up to three (3) years with notice of such cancellation/termination being made public; the loss of any license, permit, certification, or other document granted to Vendor by an agency, department or governmental entity for the right to do business in Mississippi for up to one (1) year; or,
Identity Verification In the case that the Subscriber provides telecommunication services to any Subscriber’s Customers pursuant to Section 8.1, the Subscriber is responsible for performing and shall perform personal identification of Subscriber’s Customer. SORACOM shall not bear any responsibility in relation to dealing with such matters.
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., ▇▇▇▇▇▇▇ 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 ▇▇▇▇▇▇▇▇▇▇, 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.
Compliance Verification (1) The recipient shall periodically interview a sufficient number of employees entitled to DB prevailing wages (covered employees) to verify that contractors or subcontractors are paying the appropriate wage rates. As provided in 29 CFR 5.6(a)(6), all interviews must be conducted in confidence. The recipient must use Standard Form (SF) 1445 or equivalent documentation to memorialize the interviews. Copies of the SF 1445 are available from EPA on request.
(2) The recipient shall establish and follow an interview schedule based on its assessment of the risks of noncompliance with DB posed by contractors or subcontractors and the duration of the contract or subcontract. At a minimum, the recipient must conduct interviews with a representative group of covered employees within two weeks of each contractor or subcontractor’s submission of its initial weekly payroll data and two weeks prior to the estimated completion date for the contract or subcontract. Recipients must conduct more frequent interviews if the initial interviews or other information indicates that there is a risk that the contractor or subcontractor is not complying with DB. Recipients shall immediately conduct necessary interviews in response to an alleged violation of the prevailing wage requirements. All interviews shall be conducted in confidence.
(3) The recipient shall periodically conduct spot checks of a representative sample of weekly payroll data to verify that contractors or subcontractors are paying the appropriate wage rates. The recipient shall establish and follow a spot check schedule based on its assessment of the risks of noncompliance with DB posed by contractors or subcontractors and the duration of the contract or subcontract. At a minimum, the recipient must spot check payroll data within two weeks of each contractor or subcontractor’s submission of its initial payroll data and two weeks prior to the completion date the contract or subcontract. recipients must conduct more frequent spot checks if the initial spot check or other information indicates that there is a risk that the contractor or subcontractor is not complying with DB. In addition, during the examinations, the recipient shall verify evidence of fringe benefit plans and payments thereunder by contractors and subcontractors who claim credit for fringe benefit contributions.
(4) The recipient shall periodically review contractor and subcontractor use of apprentices and trainees to verify registration and certification with respect to apprenticeship and training programs approved by either the U.S Department of Labor or a state, as appropriate, and that contractors and subcontractors are not using disproportionate numbers of, laborers, trainees and apprentices. These reviews shall be conducted in accordance with the schedules for spot checks and interviews described in Item 5(b) and (c) above.
(5) Recipients must immediately report potential violations of the DB prevailing wage requirements to the EPA DB contact listed above and to the appropriate DOL Wage and Hour District Office listed at ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/whd/america2.htm.
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
