DATA RETENTION 3 Sample Clauses

DATA RETENTION 3. DATENSPEICHERUNG Upon the termination of the Licence for a specific Hosted Licensed Property, Customer Data will be pre- served for fifteen (15) days (the "Retention Period") and made available to Customer within a commercially reasonable timeframe. After the Retention Period the Customer Data will be permanently deleted from Ave- Point's Server and shall be irrecoverable by the Cus- tomer. After the Retention Period, AvePoint makes no representations or warranties as to the preservation or integrity of Customer Data. Customer hereby agrees that AvePoint shall have no obligation to retain Cus- tomer Data after the Retention Period, unless other- wise prohibited by law. If Customer purchases a new Licence for the same Hosted Licensed Property prior to the end of the Retention Period, Customer Data shall remain available to Customer. Nachdem die LIZENZ für einen spezifischen gehosteten LIZENZ- GEGENSTAND endet, wird AVEPOINT die Daten des KUNDEN für fünfzehn (15) Tage (die „SPEICHERFRIST“) aufbewahren und dem KUNDEN innerhalb einer angemessenen Frist zugänglich ma- chen. Nach Ablauf der SPEICHERFRIST werden die Daten des KUN- DEN dauerhaft und unwiederbringlich von AVEPOINTS Servern gelöscht. AVEPOINT haftet nicht für die Erhaltung oder die In- tegrität der Daten des KUNDEN. Der KUNDE willigt ein, dass AvePoint nach Ablauf der SPEICHERFRIST keine Pflicht zur weite- ren Aufbewahrung der Daten des KUNDEN hat, soweit nicht et- was anderes gesetzlich vorgeschrieben ist. Falls der KUNDE vor Ablauf der SPEICHERFRIST eine neue LIZENZ für die gleichen ge- hosteten LIZENZGEGENSTÄNDE erwirbt, bleiben die Daten des KUNDEN für diesen verfügbar.
AutoNDA by SimpleDocs

Related to DATA RETENTION 3

  • 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.

  • Contract Number All purchase orders issued by purchasing entities within the jurisdiction of this Addendum shall include the Participating State Addendum Number: 46151504-NASPO-17-ACS. This Addendum and Master Agreement number RFP-NK-15-001 (administered by the State of Colorado) together with its exhibits, set forth the entire agreement between the Parties with respect to the subject matter of all previous communications, representations or agreements, whether oral or written, with respect to the subject matter hereof. Terms and conditions inconsistent with, contrary or in addition to the terms and conditions of this Addendum and the Contract, together with its exhibits, shall not be added to or incorporated into this Addendum or the Contract and its exhibits, by any subsequent purchase order or otherwise, and any such attempts to add or incorporate such terms and conditions are hereby rejected. The terms and conditions of this Addendum and the Contract and its exhibits shall prevail and govern in the case of any such inconsistent or additional terms within the Participating State.

  • 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.

  • Appendix H Appendix H, Contractor’s Insurance Requirements, attached hereto, is hereby expressly made a part of this Contract as fully as if set forth at length herein. The Contractor shall maintain in force at all times during the terms of the resultant Contract, policies of insurance pursuant to the requirements outlined in Appendix H – Contractor’s Insurance Requirements.

  • Record Retention Audit and Confidentiality Section 7.1(A) is deleted in its entirety and replaced with the following

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!