1.I.A.1, 1.I.A.2, 1.II.A.1, 2.II.A.2, 1.II.A.3, 1.II.B.1, 1.II.B.2, 1.E

Uniform Data System

Validated using over 1,000 edit checks, both logical and specific.  These include checks for missing data and outliers and checks against history and norms.

1.II.B.3

Health Disparities Collaboratives database (Beginning in FY 2009, data will be collected through the Uniform Data System)

Reported by grantees participating in the Collaborative; checked as needed by data coordinator.

2.1.A.1, 2.I.A.2, 2.I.A.3

Free Clinics Medical Malpractice Coverage Program Database stores data on providers and clinics from free clinic applications

Data are edited and checked by program staff.

3.II.A.1

Disability/deformity data is collected from NHDP hand and foot screens (based on the World Health Organization scale) collected from Ambulatory care clinics, NHDFP outpatient clinics and private physicians

Data are validated by staff at the Hansen’s Disease Program.

3.II.A.2

National Hansen’s Disease Program annual training records

Data are validated by staff at the Hansen’s Disease Program

3.II.A.3

National Hansen’s Disease Program Registry

Data are validated by staff at the Hansen’s Disease Program

3.E

Fiscal year budget allocations and expenditures; Ambulatory Care Program database and National Hansen’s Disease Program Records

Data are validated by staff at the Hansen’s Disease Program

4.I.C.1, 4.I.C.2, 4.1.C.3, 4.I.C.5, 4.E

BHCDANET—A mainframe database containing information collected from individual scholarship and loan repayment applications, and recruitment and retention assistance applications and monitoring data from individual sites

BHCDANET is internally managed, and has the capability for display and correction of information on a continuous, as needed, basis.

 4.I.C.4

Survey of NHSC clinicians who have completed their service obligation

Contractor does consistency and logic checks on survey data

5.I.C.1, 5.I.C.2, 5.I.C.3, 5.I.C.4, 5.E

Information from applications entered into Nursing Information System (NIS).

Program staff and contractors monitor the data and make corrections as needed. Information is checked with appropriate sources, including lenders.

6.I.B.1, 6.1.C.1, 6.1.C.2, 6.E

Annual grantee data submitted through the Comprehensive Performance Management System/Uniform Progress Report System (CPMS/UPR).  

Data are entered through a web-based system that incorporates extensive validation checks.  Grantees are also required to describe methods and systems they used to collect and submit data.  Those with deficient systems are required to submit a corrective action plan.

7.I.A.1, 7.VII.C.1, 7.VII.C.2

Yearly reconciliation application data submitted by participating hospitals

Resident counts are audited annually by CHGME fiscal intermediaries. Other data are extracted from CMS Medicare Cost Reports audited by Medicare Fiscal Intermediaries.

7.E

HRSA payment data

Validated using letters of awards and vouchers generated by CHGME PP.

8.III.B.1, 8.III.B.2, 8.III.B.3, 8.III.B.4

NPDB and HIPDB operations statistics, augmented by a user survey.

Financial audits, which involve confirmation of query volumes, are done continuously.

8.E

NPDB and HIPDB operations statistics

The time required to process a query is carefully monitored by program and by contractor staff, because this is an explicit element of the performance-based contract.

10.I.A.1, 10.I.A.2, 10.III.A.4, 10.E

The Title V Information System (TVIS) collects data on grantee performance from grantee annual reports.

TVIS allows each State to enter data on performance.  TVIS provides preformatted and interactive data entry.  Calculations are done automatically and the system performs immediate checks for errors.  Data are validated by project officers and program staff.

10.IV.B.1,  10.III.A.1, 10.III.A.2, 10.III.A.3

Vital statistics compiled by the National Center for Health Statistics, Centers for Disease Control and Prevention (CDC)

Data are validated by CDC.

11.V.B.1, 11.V.B.2, 11.V.B.3, 11.E

Grantee annual reports

Data confirmed by project officers

13.III.A.1, 13.III.A.2, 13.III.A.3, 13.E

For FY 2005, data collected from grantees by Utah State University, National Technical Resource Center, based on survey of all States.  For FY 2006 and beyond, data obtained from the CDC Hearing Screening and Follow-up Survey.  

Through 2005, data validated against annual progress reports submitted by States.  For 2006 and subsequent years, data validated by CDC through ongoing communications with States.

14.V.B.1, 14.V.B.2, 14.E

Grantee reports

Data confirmed by project officers

12.III.A.1, 12.III.A2, 12.II.B.1, 12.E

Grantee reports

Data confirmed by project officers

16.I.A.1, 16.I.A.2,  16.II.A.2, 16.II.A.3, 16.III.A.1, 16.III.A.2, 18.I.A.1, 19, II.A.1, 20.II.A.1,

The Ryan White CARE Act Data Report (CADR) [now called The Ryan White HIV/AIDS Program Annual Data Report (RDR) and beginning January 2009 it will be called The Ryan White HIV/AIDS Program Services Report (RSR)] is completed by all Ryan White HIV/AIDS Program Part A, B, C, and D-funded grantees and service providers

This web-based data collection method communicates errors and warnings in the built in validation process.  To ensure data quality the Program conducts data verification for all CADR submissions.  Reports detailing items in need of correction and instructions for submitting revised data are sent to grantees.

16.II.A.1, 16.E

ADAP Quarterly Report data provided by State ADAPs

Web-based data checked through a series of internal consistency/validity checks.  Also HIV/AIDS program staff review submitted Quarterly reports, and provide technical assistance on data-related issues.

21.V.B.1

AETC Participant Information Form from training program participants

Participant Information Forms are scanned into a Web-based system that communicates errors and inaccuracies in the built in validation process.

22.I.D.1

Dental Reimbursement Program, Application Form

Database Utility, a Web-based tool, is used to electronically complete and submit the Dental Reimbursement application.  The Database Utility application validates the report prior to the submission to the Program.  To ensure data quality, the Program also conducts data verification for all Dental Reimbursement Program Application Form submissions.  Reports detailing items in need of correction and instructions for submitting revised data are sent to grantee.

23.II.A.1, 23.II.A.2, 23.II.A.3, 22.II.A.4, 23.II.A.5, 23.II.A.6, 23.II.A.7,

The Organ Procurement and Transplantation Network (OPTN) data system collects information from transplant centers, organ procurement organizations and histocompatibility laboratories on all organ transplants that  involve the use of deceased donor organs.

Data entry screens include a variety of data element checks and cross checks that must be satisfied before the data are accepted by the system.  The contractor for the OPTN conducts additional data quality checks and follows-up with relevant entities to resolve discrepancies in the data.  An additional level of data quality review is performed by the contractor for the Scientific Registry of Transplant Recipients (SRTR) to verify the that number of deaths reported pre- and post-transplant are accurate.

23.E

OPTN contract budget and OPTN financial statements

OPTN financial statements are independently audited in accordance with OMB A-133 Circular.

24.II.A.1, 24.II.A.2,

Data are captured within the Search, Tracking and Registry (STAR) system, which is a computerized system, containing information  pertaining to unrelated volunteers willing to donate blood stem cells and patients in need of blood stem cell transplants.  Monthly reports generated from the STAR system are used to collect information on donors and cord blood units.

Validated by project officers analyzing comprehensive monthly reports.  An additional level of data quality review is performed by the program contractor utilizing value protected screens to decrease the likelihood of data entry errors and conducting site visits to validate data and review patient records.

24.E

Data are derived from the contractor and copies of contracts with human leukocyte antigen typing laboratories.

Validated through Project Officer monitoring the contractor’s budget and vouchers submitted for payment.

25.III.D.1, 25.III.D.2, 25.III.D.3, 25.E

On-line grant applications and grantee reports

Data are regularly reviewed by project officers.

27.IV.A.1, 28.V.A.1, 29.IV.A.1, 30.V.B.3, 31.V.B.1, 31.V.B.2

Annual grantee reports

Validated by project officers.

27.V.B.1, 27.E, 30.V.B.!, 30.V.B.2,

Medicare Cost Reports

Validated by Centers for Medicare and Medicaid Services

32.I.A.1, 32.I.A.2, 32.E

Annual grantee data reports

Verified by project officers

33.I.A.1, 33.I.A.2, 33.E

Grantee reports

Reviewed by program staff

34.III.D.1, 34.III.D.2, 34.II.A.1, 34.E

Annual grantee profiles, 6-month progress reports from grantees

Program staff validate data through reviews of grantee submissions, discussions with grantees, and site visits when applicable.

9.VII.C.1

Quarterly Lender Reports of Loans Outstanding entered into program’s Online Processing System (HOPS)

Program conducts routine validation checks of the data received with information in HOPS database on a quarterly basis

9.E

Online Processing System (HOPS)

Reports reviewed by program staff

26.II.A.1, 26.II.A.2, 26.II.A.3, 26.II.A.4, 26.II.A.5, 26.E

VICP internal data system and DOJ Office of Management Information system.

Validated by program staff through internal consistency checks.

35.VII.B.1

Chief Information System Security Officer, FISMA Reports which includes OIG audit results, training logs

Chief Information Security Officer examines alternative sources to confirm and validate the annual security performance metrics.

36.II.A.1, 36.II.A.2, 36.II.A.3, 36.II.B.1, 36.II.C.1, 36.II.C.2, 36.E

Family Planning Annual Report (FPAR), consisting of 14 tables in which grantees report data.

Data are checked for inconsistencies and returned to grantees for correction.  Data found by the contractor compiling the data submits these to the data coordinator who works with the regional offices to make corrections.