Data Completeness Clause Samples
The Data Completeness clause requires that all data provided under an agreement is accurate, up-to-date, and fully comprehensive. In practice, this means that the party supplying data must ensure there are no omissions or inaccuracies, and that all relevant information is included as required by the contract. This clause helps prevent disputes or operational issues that could arise from missing or incomplete data, ensuring both parties can rely on the information exchanged for decision-making and compliance purposes.
Data Completeness. The data completeness MQO was 75% for all species and all measurements. Table 2-1 summarizes data completeness for this study. PM1.0 mass cyclone / gravimetric 24-hour 04/13/01-06/30/02 94.1 % PM2.5 mass(a) HI / gravimetric 24-hour 04/13/01-06/30/02 99.1 % PM10 mass HI / gravimetric 24-hour 04/13/01-06/30/02 98.2 % PM2.5 mass CAMMS 1-hour 04/15/01-06/30/02 92.3 % size distributions UMN / PSD system 5-minute 04/01/01-04/30/02 76.0 % PM2.1 sulfate HEADS / IC 24-hour 04/13/01-06/30/02 97.1 % PM2.1 nitrate HEADS / IC 24-hour 04/13/01-06/30/02 98.4 % PM2.1 ammonium HEADS / IC 24-hour 04/13/01-06/30/02 94.8 % PM2.5 sulfate PILS - IC 1-hour 06/22/01-04/30/02 74.5 % PM2.5 nitrate PILS - IC 1-hour 06/22/01-04/30/02 73.8 % PM2.5 nitrate R&P 8400N 1-hour 02/05/02-06/30/02 75.4 % PM2.5 EC UWM / TOT 24-hour 04/11/01-06/30/02 95.7 % PM2.5 OC UWM / TOT 24-hour 04/11/01-06/30/02 97.3 % PM2.5 EC Sunset Field ECOC 1-hour 04/12/01-06/30/02 70.0 % PM2.5 OC Sunset Field ECOC 1-hour 04/12/01-06/30/02 70.0 % PM2.5 BC & UV-C Aethalometer 5-minute 04/11/01-06/30/02 95.7 % SO2 HEADS denuder 24-hour 04/13/01-06/30/02 98.0 % HNO2 HEADS denuder 24-hour 04/13/01-06/30/02 98.0 % HNO3 HEADS denuder 24-hour 04/13/01-06/30/02 98.0 % NH3 HEADS denuder 24-hour 04/13/01-06/30/02 96.8 % SO2 IEPA analyzer 1-hour 04/15/01-06/30/02 98.8 % CO IEPA analyzer 1-hour 04/15/01-06/30/02 97.3 % NO/NOx IEPA analyzer 1-hour 04/15/01-06/30/02 95.5 % O3 IEPA analyzer 1-hour 04/15/01-06/30/02 98.9 % Wind Speed see description of each sensor in the report text 5-minute 05/08/01-06/30/02 99.8% Wind Direction 5-minute 05/08/01-06/30/02 99.8% Temperature @ 10m 5-minute 05/08/01-06/30/02 94.3% Temperature @ 2m 5-minute 05/08/01-06/30/02 97.6% Relative Humidity 5-minute 05/08/01-06/30/02 99.8% Solar Radiation 5-minute 05/08/01-06/30/02 99.8% Barometric Pressure 5-minute 05/08/01-06/30/02 100.0% Precipitation 5-minute 05/08/01-06/30/02 100.0%
(a) PM2.5 “A” channel only; a second channel “B” was collected each day which could be used to impute void records for “A” channel data.
Data Completeness. The Contractor shall monitor the completeness and accuracy of the encounter data from all Providers and shall initiate corrective action, as necessary.
Data Completeness. As specified in the open-source QAPP, the goal of the NAEMS was to measure emissions from lagoons at nine farms that represented the dominant manure management systems for each animal type. At each of the nine sites, data were collected on a continuous and intermittent basis.
Data Completeness. The PCO is responsible for submission of records each time a Member has an Encounter with a Health Care Provider. The PCO must have a data completeness monitoring program in place that:
a. Demonstrates that all Claims and Encounters submitted to the PCO by the Health Care Providers, including Subcontractors, are submitted accurately and timely as Encounters to the Department. In addition, demonstrates that denied Encounters are resolved and/or resubmitted;
b. Evaluates Health Care Provider and Subcontractor compliance with contractual reporting requirements; and
c. Demonstrates the PCO has processes in place to act on the information from the monitoring program and takes appropriate action to ensure full compliance with Encounter Data reporting to the Department.
Data Completeness. The PH-MCO is responsible for submission of records each time a Member has an Encounter with a Health Care Provider. The PH-MCO must have a data completeness monitoring program in place that:
i. Demonstrates that all Claims and Encounters submitted to the PH-MCO by Health Care Providers, including Subcontractors, are submitted accurately and timely as Encounters to the Department and that demonstrates denied Encounters are resolved and resubmitted;
ii. Evaluates Health Care Provider and Subcontractor compliance with contractual reporting requirements; and
iii. Demonstrates the PH-MCO has processes in place to act on the information from the monitoring program and takes appropriate action to ensure full compliance with Encounter Data reporting to the Department. The PH-MCO must submit an annual Data Completeness Plan for review and approval. This Data Completeness Plan must include the three elements listed above.
Data Completeness. Data Completeness is usually one of the first pieces of overall data quality that is addressed because it is the simplest to measure - it is easy to report on what is or is not in HMIS, based on what is required to be in HMIS for any given project type. Data Completeness looks at how much of the data fields for any given client, their project enrollment, and any required other provider, agency, or system data is complete to the degree to which all required data is known and documented. Data Completeness is reviewed on all HUD Universal Data Elements and specifically looks at missing or null values; “data not collected” values; and depending on the data field, “client doesn’t know”, “client refused”, and / or “other” values. HMIS reports identify the areas that need to be reviewed. It is the agency’s responsibility to gather as much information including by aiming to complete data. Working with Agency Administrators, the HMIS Lead will help set up the Data Completeness reports in HMIS that can be run anytime or setup on a monthly or quarterly schedule. Those providers who fall below the baseline requirement for Data Completeness for their project type will be asked to clean up their data within two weeks after the end of the quarter. The ROCC recommends that agencies complete the data cleanup monthly to avoid difficulties meeting this timeline each quarter. Review the encouragement section of this document to understand how the ROCC will acknowledge those agencies meeting and/or exceeding required expectations. The ROCC agreed upon data quality benchmarks for a minimum 95% of data required for all project types: Coordinated Entry, Homeless Prevention, Rapid Rehousing, Permanent Supportive Housing and Transitional Housing. Street Outreach 95% requirement only applies after client has a Date of Engagement.