iConnect · Guide · updated Sep 6, 2026
Open iConnect APD's iConnect system expects each visit as an 'activity' inside an Activities Import file. WaiverSoft builds that file from your documented visits and delivers it to APD's server automatically. APD answers with a result for each visit, which WaiverSoft reads back.
- Ready to send: the visits that can go to APD now, grouped by consumer, plus anything blocked and why.
- Batches: every send, with a tracker (Built → Sent to APD → APD's result) and APD's reason for any rejection.
- Set up / Connection: the five-step connection, then a health page once connected.
What makes a visit sendable
- The shift is in the past and the caregiver clocked out or wrote a note.
- The consumer and the caregiver are matched to their iConnect records.
- The shift has a service line, and an approved authorization for that service covers the date.
- The visit is at least one unit long and has a note.
- It hasn't been sent already.
Anything that fails one of these shows under Blocked with a button that takes you to the fix.
Related
- Connect to iConnect: the five steps · Bring in the report, confirm who you are, match people, ask APD for the certificate, enter the credentials.
- Send visits to APD · Review who's included, run the checks, confirm, and watch the batch until APD answers.
- Why APD rejected a visit, and what to do · The common rejection reasons in plain language, each with the fix.