DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A.
b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915.
c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.
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.
DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.
Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act.
(B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S.
(C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.
Quality Assurance/Quality Control Contractor shall establish and maintain a quality assurance/quality control program which shall include procedures for continuous control of all construction and comprehensive inspection and testing of all items of Work, including any Work performed by Subcontractors, so as to ensure complete conformance to the Contract with respect to materials, workmanship, construction, finish, functional performance, and identification. The program established by Contractor shall comply with any quality assurance/quality control requirements incorporated in the Contract.
Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.
Third Party Verification 4.8.1 The SPD shall be further required to provide entry to the site of the Power Project free of all encumbrances at all times during the Term of the Agreement to SECI and a third Party nominated by any Indian Governmental Instrumentality for inspection and verification of the works being carried out by the SPD at the site of the Power Project.
4.8.2 The third party may verify the construction works/operation of the Power Project being carried out by the SPD and if it is found that the construction works/operation of the Power Project is not as per the Prudent Utility Practices, it may seek clarifications from SPD or require the works to be stopped or to comply with the instructions of such third party.
Inspection/Testing In order to assess Supplier’s work quality and/or compliance with this Order, upon reasonable notice by Buyer: (a) all goods, materials and services related to the items purchased hereunder, including, raw materials, components, assemblies, work in process, tools and end products shall be subject to inspection and testing by Buyer, its customer, representative or regulatory authorities at all places, including sites where the goods are made or located or the services are performed, whether at Supplier’s premises or elsewhere; and (b) all of Supplier’s facilities, books and records relating to this Order shall be subject to inspection by Buyer or its designee. If specific Buyer and/or Buyer’s customer tests, inspection and/or witness points are included in this Order, the goods shall not be shipped without an inspector’s release or a written waiver of test/inspection/witness with respect to each such point; however, Buyer shall not be permitted to unreasonably delay shipment; and Supplier shall notify Buyer in writing at least twenty (20) days prior to each of Supplier’s scheduled final and, if applicable, intermediate test/inspection/witness points. Supplier agrees to cooperate with such/audit inspection including, completing and returning questionnaires and making available its knowledgeable representatives. Buyer’s failure to inspect or test goods, materials or services or Buyer’s failure to reject or detect defects by inspection or testing shall not relieve Supplier from its warranty obligations or any of its other obligations or responsibilities under this Order. Supplier agrees to provide small business as well as minority and/or women owned business utilization and demographic data upon request.
