Guide
How to Export OIG Screening Evidence for Auditors
By Keelstar Team · Updated July 11, 2026
The short answer
Auditors request proof that exclusion screening occurred on schedule — not verbal assurances. Export a structured report covering the audit period: every party screened, search dates, list sources, names searched, results, match dispositions, and reviewer identity. Tie each record to the vendor or employee master so reviewers can trace onboarding checks through recurring re-screens. Include overdue-screen exceptions and how they were resolved. CSV or PDF export from a screening log or monitoring tool is stronger than scattered email screenshots. Organize by date range, party type, or risk tier depending on the auditor's sample request. Retain exports with the audit response package and keep source records accessible for follow-up samples.
What auditors request
CMS, state surveyors, and payer auditors typically ask for a sample of exclusion checks during a defined period. They want to verify screening happened before engagement, re-screening occurred on schedule, potential matches were investigated, and records are complete. Expect requests segmented by employees, vendors, or high-risk categories.
Minimum fields for export
Every exported record should answer who, when, against what, with what result, and by whom.
- Party name and identifier (employee ID or vendor number)
- Legal names and aliases searched
- Search date and time
- List source and version (OIG LEIE download date)
- Result: clear, potential match, or confirmed match
- Reviewer or system identity
- Match disposition notes when applicable
Organizing exports by audit scope
Structure exports to match the auditor sample methodology. Date-range exports work for period-based reviews. Party-type exports (employees vs. vendors) work for targeted samples. Risk-tier exports demonstrate your risk-based program. Include a summary cover sheet with total parties screened, overdue exceptions, and confirmed matches during the period.
Common export failures
Teams lose credibility when exports are incomplete: missing re-screens, no list version dates, only clear results without names searched, or evidence stored outside the system of record. Gaps in a sample often trigger expanded review — prepare complete exports the first time.
Using automated export from screening tools
Manual assembly from spreadsheets and inbox screenshots does not scale and introduces errors. Exclusion monitoring tools that log every check produce one-click exports by date range, party, or result type. Use these for audit responses and internal compliance reporting.
Frequently asked questions
- What format do auditors prefer for screening evidence?
- Structured logs — CSV, PDF, or system-generated reports — beat unstructured email attachments. Include consistent fields across every record so reviewers can validate completeness.
- How far back should export cover?
- Match the auditor sample period, typically 12 to 36 months. Many healthcare organizations retain exclusion screening records for at least six years.
- Do I need to export match investigation records separately?
- Yes. Potential and confirmed matches should include disposition documentation — identifiers compared, outcome, and reviewer — as part of the export or as linked attachments.
- Can I redact employee or vendor data in exports?
- Provide enough identifying information for the auditor to verify the sample — usually legal name, role or vendor category, and screening dates. Follow your organization's data sharing policy policy for sensitive fields.
Related guides
Put this into a monitored workflow
Exclusion Monitor handles this continuously — with reminders and an audit trail.