Data Cleansing Clause Samples

The Data Cleansing clause defines the process and responsibilities for identifying, correcting, or removing inaccurate, incomplete, or irrelevant data within a dataset. Typically, this clause outlines which party is responsible for performing data cleansing, the standards or methods to be used, and any timelines or reporting requirements. Its core practical function is to ensure that the data used or delivered under the agreement is accurate and reliable, thereby minimizing errors and improving the quality of outcomes based on that data.
Data Cleansing. 11.2.1 If the Solution Architecture requires that data cleansing is to be performed by the Service Provider, the Service Provider must process the Health Data and make modifications to the Health Data by: (a) eliminating records that are clearly duplicates; (b) correcting obvious misspellings and errors; (c) ensuring that there are consistent descriptions, punctuation and syntax; and (d) resolving any other obvious inaccuracy, omission or inconsistency issues, to meet the level of accuracy and consistency stated in the Solution Architecture.
View SourceView Similar (4)
Data Cleansing. The Contractor shall support the State, which is responsible for cleaning source data before phased migration conversions. (1) The Contractor shall test and perform ETL processes, which generate anomaly reports when running ETL scripts. The Contractor shall provide these error reports to the State to assist its efforts in cleaning any legacy data that may require work. There are generally two dimensions of data cleansing: (a) Compliance with required structural format; and (b) Accuracy of the data. Testing and validating the structural format of data ensures that actual production data is structured in compliance with defined requirements for CIVLS. Data accuracy testing ensures that the data is accurate and up to date, typically through the State using sample random testing techniques. (2) The Contractor shall use the then existing State suite of tools to identify anomalies in State legacy application source data that require cleaning. The State then can use this suite and other methods to clean the source data so it no longer presents anomalies for final conversion. (3) When the source data is declared by the Project Administrator to be clean and ready for the State to convert, the Contractor shall perform a final test against the cleansed legacy data to ensure all issues have been resolved. Issues may be resolved by conversion business rules or direct intervention (e.g., replacement) of the data by authorized State employees. The Contractor shall either validate the data as being ready for conversion or identify additional anomalies for State resolution.
View SourceView Similar (2)

Related to Data Cleansing

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union ▇▇▇▇▇▇▇ or in their absence, the Local Union President, or Area ▇▇▇▇▇▇▇, or Chief ▇▇▇▇▇▇▇, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union ▇▇▇▇▇▇▇, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union ▇▇▇▇▇▇▇ or in their absence, the Local Union President, or Area ▇▇▇▇▇▇▇, or Chief ▇▇▇▇▇▇▇, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

  • Screening The Health Plan must work with contracted providers to conduct interperiodic EPSDT screens on RIte Care and all ACA Adult Expansion Population members under age 21 (i.e. 19 and 20-year old under this Agreement) to identify health and developmental problems in conformance with ATTACHMENT ED to this Agreement. Additional screens should be provided as Medically Necessary. At a minimum, these screens must include: • A comprehensive health and developmental history, including health education, nutrition assessment, immunization history, and developmental assessment • Immunizations according to the Rhode Island EPSDT Periodicity Schedule • An unclothed physical examination • Laboratory tests including lead, TB, and newborn screenings as medically indicated • Vision testing • Hearing testing • Dental screening oral examination by PCP as part of a comprehensive examination required before age one (1) • All other medically indicated screening services • And provide EOHHS with a list of established CPT/HCPC codes used to identify all billable services included in the EPSDT schedule.

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act. (B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S. (C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.