Data Accuracy The Custodian has no responsibility for, or duty to review, verify or otherwise perform any investigation as to the completeness, accuracy or sufficiency of, any data or information provided by or on behalf of the Client, any persons authorized by the Client, any Third Party Agent, any Market Participant or any Authorized Data Sources, except to the extent the Custodian has agreed in writing to perform reconciliations, variance or tolerance checks or other specific forms of data review under this Agreement.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
Accuracy and Completeness of Information No written information, report or other papers or data (excluding financial projections and other forward looking statements) furnished to the Agent or any Lender by, on behalf of, or at the direction of, the Borrower, any other Obligor or any of their respective Subsidiaries in connection with or relating in any way to this Agreement, contained any untrue statement of a fact material to the creditworthiness of the Borrower, any other Obligor or any of their respective Subsidiaries or omitted to state a material fact necessary in order to make such statements contained therein, in light of the circumstances under which they were made, not misleading. The written information, reports and other papers and data with respect to the Borrower, any other Obligor or any of their respective Subsidiaries or the Unencumbered Assets (other than projections and other forward-looking statements) furnished to the Agent or the Lenders in connection with or relating in any way to this Agreement was, at the time so furnished, complete and correct in all material respects, or has been subsequently supplemented by other written information, reports or other papers or data, to the extent necessary to give in all material respects a true and accurate knowledge of the subject matter. All financial statements furnished to the Agent or any Lender by, on behalf of, or at the direction of, the Borrower, any other Obligor or any of their respective Subsidiaries in connection with or relating in any way to this Agreement, present fairly, in accordance with GAAP consistently applied throughout the periods involved, the financial position of the Persons involved as at the date thereof and the results of operations for such periods. All financial projections and other forward looking statements prepared by, or on behalf of the Borrower, any other Obligor or any of their respective Subsidiaries that have been or may hereafter be made available to the Agent or any Lender were or will be prepared in good faith based on reasonable assumptions. No fact or circumstance is known to the Borrower which has had, or may in the future have (so far as the Borrower can reasonably foresee), a Material Adverse Effect which has not been set forth in the financial statements referred to in Section 6.1(k) or in such information, reports or other papers or data or otherwise disclosed in writing to the Agent and the Lenders prior to the Effective Date.
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
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.
CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS 1. The Contractor certifies that it will provide a drug-free workplace by:
a. Publishing a statement notifying employees that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Contractor’s workplace and specifying the actions that will be taken against employees for violation of such prohibition;
Completeness and Modification This Agreement constitutes the entire understanding between the parties hereto superseding all prior and contemporaneous agreements or understandings among the parties hereto concerning the Employment Agreement. This Agreement may be amended, modified, superseded or canceled, and any of the terms, covenants, representations, warranties or conditions hereof may be waived, only by a written instrument executed by the parties or, in the case of a waiver, by the party to be charged.
Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.
B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.
Child Abuse Reporting Requirement Grantee will:
a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.
b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements.
c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency.
d. retain reporting documentation on site and make it available for inspection by the System Agency.
Certification of Accuracy The following parties have reviewed the information above and certify, to the best of their knowledge, that the information they have provided is true and accurate.
