✓Illinois Compliance Automation
Illinois · HHAeXchange integration opportunity

Add Illinois workforce compliance to the HHAeXchange ecosystem.

A production-tested automation layer for IDPH / HCWR, background and registry checks, fingerprinting, TTP profiles and compliance documents — with HHAeXchange staying at the center.

Production API in use today5,000+ background checks50,000+ compliance documents2.5+ years live Illinois operations
See the integration pattern →
HHAeXchange supplies
HHAeXchange
Caregiver dataHire · update · position · terminationDocuments / training evidence
↓
Illinois Compliance Automation LayerIllinois-specific orchestration behind the source system
ReconciliationWorkflow orchestrationStatus exchangeDocument delivery
↓
IDPH / HCWR
Background Check / Registries
Fingerprinting
TTP
↺ Statuses · delivery confirmations · exceptions · reports return to HHAeXchange
Why this fits the moment

Illinois enforcement is active — and provider priorities already point to this problem.

This is less about adding another portal and more about turning state-specific compliance work into a connected operational workflow.

Illinois · August 1, 2026

TTP is now part of routine compliance monitoring.

OCCS will use TTP to monitor staff training.
Alternate tracking methods do not substitute for TTP.
Incomplete information may lead to corrective or contract action.
Source: Illinois Department on Aging / OCCS TTP compliance email communication, August 2026.
HHAeXchange · 2026 Provider Voices

The top two provider priorities align with the same workflow.

#1
Compliance
Top business priority for the second year in a row.
#2
Reduce administrative work
The next priority providers ranked after compliance.
63.9%
of providers say EVV / compliance is their top technology investment.
That makes this an intersection of both priorities: stronger compliance with less manual back-office work.
Based on 465 agencies in HHAeXchange's 2026 Provider Voices survey. View source ↗
Integration pattern

HHAeXchange stays central — and becomes the operational source of truth for caregiver data.

After a one-time baseline reconciliation, the Illinois-specific complexity can sit behind HHAeXchange while results return to the same operational context providers already use.

Operational source of truth

HHAeXchange

Caregiver profile · employment data · documents · training evidence · lifecycle events
→
Compliance layer

Illinois Compliance Automation API

Select a capability.
Reconciliation: match existing caregivers, compare source and state records, surface missing fields and conflicts, and establish a trusted baseline before automation.
→
Illinois systems

State workflow

IDPH / HCWR · background and registry checks · fingerprinting · TTP
Source-of-truth principle: once the baseline is validated, HHAeXchange drives ongoing caregiver-data synchronization. Official eligibility and state statuses continue to come from the authoritative Illinois systems and return to HHAeXchange.
Baseline once. Automate continuously.

The first reconciliation is controlled and human-reviewed. The payoff is everything that comes after.

Real provider data is messy. The migration identifies missing Illinois-required fields and real discrepancies, then creates a clean baseline that can safely drive ongoing automation.

1
Match caregivers

Use identifiers such as SSN to align HHAeXchange records with existing state records.

2
Compare records

Identify mismatches, missing fields, duplicates and profile gaps across HHAeXchange, IDPH and TTP.

3
Human review & complete gaps

Confirm correct values and add Illinois-specific data that needs to live in the source system.

4
Establish the baseline

Synchronize validated records, close initial compliance gaps and turn on ongoing automation.

It is a one-time cleanup step. After that, HHAeXchange can remain the operational source of truth and normal caregiver events can drive the appropriate Illinois workflow automatically.

See what happens after go-live

Choose a normal caregiver event.
New caregiver is added
The caregiver enters the normal HHAeXchange workflow with available profile and employment data.
→
Run initial compliance workflow
Create or reconcile required profiles, run background and registry checks, support fingerprinting, and establish TTP status.
→
Normalized status returns
HHAeXchange receives completed, pending or exception statuses plus available evidence and delivery confirmations.
Production proof

Shared customer. Live Illinois operations. Proven workflow.

Abcor Home Health — also featured by HHAeXchange in an Illinois customer case study — is where this compliance automation has been running in production for more than two years.

Abcor Home Health · live operations

A real provider environment both teams already know.

HHAeXchange's own case study describes Abcor's integrated ecosystem and HRIS integration. In the same provider environment, the Illinois compliance engine has processed background checks, compliance documents and ongoing caregiver lifecycle workflows at scale.
5,000+background checks processed
50,000+compliance documents processed
2.5+ yrslive automated compliance operations
Production workflows include IDPH / HCWR, background and registry checks, fingerprinting, TTP profile management, document delivery, training records, position changes, terminations and ongoing synchronization.
HHAeXchange Abcor case study ↗
Sample background check first page
Sample evidence

Background check with a reviewable evidence trail.

The sanitized demo report summarizes HCWR eligibility and required background / registry checks, then retains supporting source evidence in a single report.
8 source / registry checksHCWR eligibilityEvidence by source
Download PDF
What normalized compliance data can unlock

Automation is the first value. Visibility can be the next.

Once Illinois compliance data is normalized and continuously synchronized, HHAeXchange can decide how much provider-facing visibility belongs inside its own product.

Embedded status

Show background, HCWR, TTP and document states inside the provider workflow.

Exception queues

Surface who needs attention and why — missing data, due screening, training gaps or failed delivery.

Audit-ready evidence

Keep source evidence, delivery confirmation and workflow history available for compliance review.

Optional executive reporting

Use the same normalized data for provider-level compliance views without making a new portal mandatory.

Illustrative Compliance Dashboard

One possible embedded view — not required for the integration
SAMPLE DATA
Active workers1,200
Background checks missing26
Documents missing252
94%
Current & eligible
Background checks
94%
Training complete
78%
Docs complete
79%
Profiles synced
97%
Common questions

A few practical details.

Enough context to understand the integration opportunity without turning the presentation into technical documentation.

A production API is already in use today, with two-way data exchange and webhook support for asynchronous status updates. HHAeXchange can remain the provider-facing source system while the compliance layer performs Illinois-specific workflows behind it and returns normalized statuses, confirmations and exceptions.
SSN can be used to match an existing caregiver. Additional Illinois-required profile fields are needed when creating or updating IDPH and TTP records. The baseline reconciliation identifies what is missing or inconsistent so HHAeXchange and the provider can agree what needs to live in the source data model before go-live.
Any field used by the relevant IDPH or TTP workflow can be synchronized when it changes. Critical identity changes — first name, middle name, last name or date of birth — can also trigger a new background check automatically because the prior screening is no longer sufficient for the updated identity. Other changes, such as address updates, are synchronized without unnecessarily rerunning the background check.
Yes. The automation already supports both. Each TTP document or training category has required data associated with it; once the required file and metadata are available, the compliance layer can submit it to the appropriate TTP workflow and return delivery status. The exact source and mapping of those fields would be validated during integration.
Yes. The same decision logic is already used for API-driven updates and bulk operations such as running background checks and synchronizing documents across selected caregivers. Manual CSV import is also available as a migration or operational tool, but it is not required for an API-based HHAeXchange integration.
We are open to different structures, including embedded or white-labeled API integration, a partner-operated solution, licensing or usage-based economics, or another model aligned with HHAeXchange's product strategy. The better sequence is to validate the Illinois workflow and data fit first, then decide how the capability should be packaged and commercialized.
A low-friction next step

Validate one Illinois workflow against HHAeXchange data.

A focused working session can determine whether the opportunity is real before either team commits to a larger project.

1 · Workflow mapConfirm IDPH / HCWR, background checks, fingerprinting and TTP steps.
2 · Field mapCompare the HHAeXchange data model with Illinois requirements and identify gaps.
3 · Integration pathValidate one data flow, one workflow and the returned statuses.
4 · RecommendationDefine pilot scope and the operating / commercial model that fits.
Schedule a working session →
Dmitriy Fridlyand · Lotatechdmitriy.f@lotatech.com773-592-3430