Federal AI Intelligence
Menu
Snapshot · OMB 2025 inventory · processed Oct 11, 2026
DHS · DHS-180 · record R1948

Automated Name and Date of Birth (DOB) Harvesting Service

Department of Homeland Security · USCIS

Overview

Development stage
DeployedSource: c) Deployed – The use case is being actively authorized or utilized to support the functions or mission of an agency.
High-impact designation
Presumed high-impact, determined notSource: b) Presumed high-impact, but determined not high impact
Impact justification
The use case improves case processing efficiency by reducing the amount of time USCIS staff must spend to manually find aliases and dates of birth (DOBs) in existing records of an individual. The AI outputs do not serve as a principal basis for a decision or action concerning a specific individual or entity that has a legal, material, binding, or similarly significant effect on that individual’s or entity’s civil rights, civil liberties or privacy, equal opportunities, or access to or the ability to apply for critical government resources or services. The use case increases efficiency of tasks associated with accurate and timely identification, analysis, and review of biographical information needed for adjudication. The AI outputs are suggested aliases and DOBs related to the individual query, which USCIS staff must review to accept, reject, or ignore the suggested information. The AI outputs reduce the amount of adjudicative time spent manually harvesting aliases and DOBs. The use case increases efficiency of tasks associated with reviewing existing records for adjudicating requests for immigration benefits. Completing such adjudications are not dependent on the use case however lack of this tool would significantly increase human processing times and potentially reduce the accuracy of information consulted during the human review process.
Start date
2022-06-27 (day precision)Source: 2022-06-27T00:00:00
Withheld from public reporting
Not reported

Mission

Topic area
Service Delivery
Operational functions
Claims and case processing Derived by keyword rules; see methodology

Problem the AI is intended to solve

Adjudicators spend significant amount of time manually harvesting aliases and dates of birth (DOBs) from identity history summary (IdHS) report attached to the ELIS case as part of the Manual Name Harvesting Task during case processing.

Expected benefits

To reduce the amount of adjudicative time spent manually harvesting aliases and dates of birth (DOBs) from identity history summary (IdHS) report attached to the ELIS case as part of the Manual Name Harvesting Task during case processing.

System outputs

Suggested Names and DOBs from IdHS record.

Technology

AI classification
Classical / predictive MLSource: Classical/Predictive Machine Learning: Models trained on data to make predictions or classifications based on identified patterns or relatio…
System name(s)
ELIS
Custom-developed code
Yes
Public source code
Not reported

Sourcing

How it was built
Contract and in-houseSource: c) Developed with both contracting and in-house resources
Vendor (as reported)
SAIC and DV United
Vendors (standardized)
SAIC

A vendor is the supplier named by the agency. It does not identify the underlying model or AI technology.

Data and privacy

Involves PII
Yes
Privacy Impact Assessment
www.dhs.gov ↗
Authorization to Operate
Yes
Demographic features
Not reported
Training and evaluation data
Training and evaluation for ANH was performed using a large set of previously annotated IdHS records (raw text) in a secure environment separate from our standard development environment. The system uses Spark NLP and distilbert embeddings for the model input, so no raw text from these files is stored or accessible from the final model or associated logged artifacts. Annotations were sourced from results of previously completed manual name harvesting tasks.
Federal Data Catalog
Not reported

Governance

0 of 8 minimum-practice questions answered. A blank answer means the agency reported nothing; it does not mean the practice is absent.

Pre-deployment testingNo answer reported
AI impact assessmentNo answer reported
Independent reviewNo answer reported
Ongoing monitoringNo answer reported
Operator trainingNo answer reported
Fail-safeNo answer reported
Appeal processNo answer reported
User and public consultationNo answer reported

Potential impacts and how they were identified

Not reported