Case and Data Retention Sample Clauses

Case and Data Retention. All records received by FTB-COD and any database created, copies made, or files attributed to the records received will be destroyed when no longer needed for the business purpose for which it was originally obtained. Data will be destructed in accordance with established FTB Data Retention Guidelines, which are four (4) years from the date the last active case on the account was withdrawn or closed. The records shall be destroyed in a manner to be deemed unusable or unreadable and to the extent that an individual record can no longer be reasonably ascertained. Exception: Accounts will not be destroyed per the Data Retention Guideline if: • A payment was received within four (4) years • A payment issue is being reviewed • A credit balance exists on the account • A refund, fund transfer or general fund credit existed within the last four (4) years Agreement# 3464 Agreement#29220 EXHIBIT A SCOPE OF WORK (continued) FTB-COD Responsibilities
AutoNDA by SimpleDocs
Case and Data Retention. All records received by FTB-COD and any database created, copies made, or files attributed to the records received will be destroyed when the information is no longer needed for the business purpose it was obtained for in accordance with established Data Retention Guidelines which are four (4) years from the date the last active case on the account was withdrawn or closed. The records shall be destroyed in a manner to be deemed unusable or unreadable and to the extent that an individual record can no longer be reasonably ascertained. Exception: Accounts will not be destroyed per the Data Retention Guideline if: • A payment was received within four (4) years • A payment issue is being reviewed • A credit balance exists on the account • A refund, fund transfer or general fund credit existed within the last four (4) years FTB-COD Responsibilities

Related to Case and Data Retention

  • 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 Deletion As stated in the Student Data Transfer or Destruction Section of this Agreement, Provider shall ensure that all Student Data in its possession and in the possession of any subcontractors, or agents to whom Provider may have transferred Student Data, is destroyed or, as directed by the Board, transferred to the Board in a format determined by the Board within the time periods provided in the Student Data Transfer or Destruction Section of this Agreement.

  • Optional Xactimate Response Attachment (Part 2)

Time is Money Join Law Insider Premium to draft better contracts faster.