Information and Data Requirements Clause Samples
Information and Data Requirements
Information and Data Upon request of the Union, the Employer agrees to furnish the Union with the following information: budgets for the Board of Regents; budgets for each College; public information used in the preparation of budgets as provided by law such as salaries; minutes of meetings of the Board; policies of the Board of Regents which apply to faculty members. Voluminous information shall be made available for inspection or will be provided at reproduction cost.
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.
Information Requirements The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder and take such further reasonable action as any Holder may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company’s most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.
Information and Records (a) Lessee shall promptly furnish to Lessor all such information as Lessor may from time to time reasonably request regarding the Aircraft or any part thereof, its use, registration, location and condition. In addition, Lessee shall, on each Maintenance Payments Date and the Termination Date, furnish to Lessor a monthly maintenance status report substantially in the form of Schedule 5. (b) Lessee shall keep, or procure that there are kept, (i) the Aircraft Documents and shall keep as part thereof accurate, complete and current records of all flights made by the Aircraft during the Term, including all Flight Hours and Cycles of the Airframe, each Engine and the Parts, and of all maintenance and repairs carried out on the Aircraft and each Engine and every Part and (ii) historical records for condition monitored, hard time and life-limited Parts (including tags from the manufacturer of such Part or a repair facility which evidence that such Part is new or overhauled and establish authenticity, total time in service and time since overhaul for such Part). Such Aircraft Documents and historical records referred to in subclause (ii) shall be kept for the duration of the Term and maintained in English and in such manner, form and location as the Aviation Authority and any applicable law may from time to time require and the Aircraft Documents shall disclose the location of all Engines and Parts not installed on the Aircraft. In addition, the Aircraft Manuals shall be kept in such manner, form and location as the FAA may require to the extent that the requirements of the FAA do not conflict with the requirements of the Aviation Authority. Except as required by applicable law, the Aircraft Documents and historical records referred to in subclause (ii) shall be the property of Lessor. Lessee may maintain all Aircraft Documents (or any subset thereof) in electronic format, provided, that Lessee shall send to Lessor all hard copies of all such Aircraft Documents. (c) Lessee shall promptly on becoming aware of the same notify Lessor of: (i) any Total Loss with respect to the Aircraft, the Airframe or any Engine; (ii) any loss, theft, damage or destruction to the Aircraft or any part thereof if (A) the potential cost of repairs or replacement may exceed the Damage Notification Threshold or its equivalent in any other currency, or (B) Lessee is required to report the same to the Aviation Authority; (iii) any loss, arrest, hijacking, confiscation, seizure, requisition, impound, taking in execution, detention or forfeiture of the Aircraft or any part thereof; and (iv) any event, accident or incident in respect of the Aircraft that might reasonably be expected to involve Lessor or Lessee in loss or liability in excess of the Damage Notification Threshold or its equivalent in any other currency, or which is required to be reported to the Aviation Authority. (d) Lessee shall provide Lessor with prior written notice of each 6Y/4C-Check, 12Y/8C-Check, Engine Performance Restoration, APU Heavy Repair and Landing Gear Overhaul, provided that if any such maintenance event is to occur less than thirty days after the scheduling thereof, Lessee shall provide written notice of such maintenance event promptly upon the scheduling thereof.
Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.