Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.
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.
Record and File Retention Grantee must maintain these files for five years after the end of the applicable fiscal year, except that, if any litigation, claim or audit is commenced with respect to the transactions documented by such files before the end of the aforementioned five-year period and extends beyond the expiration of the five-year period, these files must be retained until all litigation, claims, or audit findings involving the files have been resolved.
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.
Records Retention PROVIDER will preserve all contracting information, as defined under Texas Government Code, Section 552.003 (7), related to the Agreement for the duration of the Agreement and for seven years after the conclusion of the Agreement.
DATA RETENTION AND DELETION 7.1. No party shall retain or process Shared Personal Data for longer than is necessary to carry out the Agreed Purposes. parties shall continue, however, to retain Shared Personal Data in accordance with any statutory retention periods applicable in their respective countries and/or states.
Medical Records Retention Grantee shall retain medical records in accordance with 22 TAC §165.1(b) or other applicable statutes, rules and regulations governing medical information.
Contractor Certification for Contractor Employees Introduction Texas Education Code Chapter 22 requires entities that contract with school districts to provide services to obtain criminal history record information regarding covered employees. Contractors must certify to the district that they have complied. Covered employees with disqualifying criminal histories are prohibited from serving at a school district. Definitions: Covered employees: Employees of a contractor or subcontractor who have or will have continuing duties related to the service to be performed at the District and have or will have direct contact with students. The District will be the final arbiter of what constitutes direct contact with students. Disqualifying criminal history: Any conviction or other criminal history information designated by the District, or one of the following offenses, if at the time of the offense, the victim was under 18 or enrolled in a public school: (a) a felony offense under Title 5, Texas Penal Code; (b) an offense for which a defendant is required to register as a sex offender under Chapter 62, Texas Code of Criminal Procedure; or (c) an equivalent offense under federal law or the laws of another state. I certify that: NONE (Section A) of the employees of Contractor and any subcontractors are covered employees, as defined above. If this box is checked, I further certify that Contractor has taken precautions or imposed conditions to ensure that the employees of Contractor and any subcontractor will not become covered employees. Contractor will maintain these precautions or conditions throughout the time the contracted services are provided. OR SOME (Section B) or all of the employees of Contractor and any subcontractor are covered employees. If this box is checked, I further certify that: (1) Contractor has obtained all required criminal history record information regarding its covered employees. None of the covered employees has a disqualifying criminal history. (2) If Contractor receives information that a covered employee subsequently has a reported criminal history, Contractor will immediately remove the covered employee from contract duties and notify the District in writing within 3 business days. (3) Upon request, Contractor will provide the District with the name and any other requested information of covered employees so that the District may obtain criminal history record information on the covered employees. (4) If the District objects to the assignment of a covered employee on the basis of the covered employee's criminal history record information, Contractor agrees to discontinue using that covered employee to provide services at the District. Noncompliance or misrepresentation regarding this certification may be grounds for contract termination. None Texas Business and Commerce Code § 272 Requirements as of 9-1-2017 SB 807 prohibits construction contracts to have provisions requiring the contract to be subject to the laws of another state, to be required to litigate the contract in another state, or to require arbitration in another state. A contract with such provisions is voidable. Under this new statute, a “construction contract” includes contracts, subcontracts, or agreements with (among others) architects, engineers, contractors, construction managers, equipment lessors, or materials suppliers. “Construction contracts” are for the design, construction, alteration, renovation, remodeling, or repair of any building or improvement to real property, or for furnishing materials or equipment for the project. The term also includes moving, demolition, or excavation. BY RESPONDING TO THIS SOLICITATION, AND WHEN APPLICABLE, THE PROPOSER AGREES TO COMPLY WITH THE TEXAS BUSINESS AND COMMERCE CODE § 272 WHEN EXECUTING CONTRACTS WITH TIPS MEMBERS THAT ARE TEXAS GOVERNMENT ENTITIES. 7 5 Texas Government Code 2270 Verification Form Texas Government Code 2270 Verification Form Texas 2017 House Xxxx 89 has been signed into law by the governor and as of September 1, 2017 will be codified as Texas Government Code § 2270 and 808 et seq. The relevant section addressed by this form reads as follows: Texas Government Code Sec. 2270.002. PROVISION REQUIRED IN CONTRACT. A governmental entity may not enter into a contract with a company for goods or services unless the contract contains a written verification from the company that it: (1) does not boycott Israel; and (2) will not boycott Israel during the term of the contract engaged by: ESC Region 8/The Interlocal Purchasing System (TIPS) 0000 Xxxxxxx 000 Xxxxx Xxxxxxxxx,XX,00000 I verify by this writing that the above-named company affirms that it (1) does not boycott Israel; and (2) will not boycott Israel during the term of this contract, or any contract with the above-named Texas governmental entity in the future. I further affirm that if our company’s position on this issue is reversed and this affirmation is no longer valid, that the above-named Texas governmental entity will be notified in writing within one (1) business day and we understand that our company’s failure to affirm and comply with the requirements of Texas Government Code 2270 et seq. shall be grounds for immediate contract termination without penalty to the above-named Texas governmental entity. AND Our company is not listed on and we do not do business with companies that are on the the Texas Comptroller of Public Accounts list of Designated Foreign Terrorists Organizations per Texas Gov't Code 2270.0153 found at xxxxx://xxxxxxxxxxx.xxxxx.xxx/purchasing/docs/foreign-terrorist.pdf I swear and affirm that the above is true and correct. YES
