Help caregivers move from their scheduled visit to check-out with the care plan, visit documentation and Electronic Visit Verification connected in Elixir.
Know what to prepare, what to record and what happens after submission. Follow the caregiver’s visit through six practical steps.
Explore the visit journey
Follow a home visit from preparation through review and acceptance. Select each step to explore the workflow.
Illustrative workflow panels. These explain the experience and are not screenshots of the application.
Step 01 / 30 seconds
Pre-Departure
Review assigned visits and care tasks. Download the information needed for offline work while connected.
Visit information
Assignment, service window and care plan
Offline preparation
Visit details and forms downloaded
Freshness
Last-updated time visible
Download assigned visits, permitted client details, care plans and forms before going offline. Capture check-in and check-out, complete downloaded tasks, record notes and collect signatures or attestations securely on the device. Offline authorization checks use downloaded information. Current authorization and schedule details are revalidated when the visit synchronizes.
Connectivity is needed to download updates, send records to the server and receive current review or aggregator responses. Queued records upload automatically when a connection returns, preserving original visit timestamps. Temporary failures retry without creating duplicate visits. Conflicts retain the original information for supervisor review, and unsynced records remain stored until receipt is confirmed.
Saved on device
Stored encrypted
Pending sync
Queued for network
Synced
Confirmed on server
Needs attention, if flagged
Triage queue
While connected, download assigned visits, permitted client details, care plans, required forms and authorization information. Check the last-updated indicator before heading out.
Continue check-in and check-out, downloaded care tasks, notes, signatures and attestations offline. Records save securely on the device and remain pending synchronization until connectivity returns.
Saved on device means the record is stored locally. Pending sync means it is awaiting upload. Synced confirms server receipt. Internal verification and aggregator acceptance are separate statuses.
The original caregiver record and the updated information are preserved for supervisor review. The visit shows that attention is needed, including whether the caregiver must take action. Corrections retain the review history.
Temporary upload failures retry automatically without creating duplicate visits. Records remain on the device until receipt is confirmed. Issues requiring intervention are routed for review.
No. Submission, synchronization and internal verification are separate steps. Required aggregator acceptance, authorization and documentation checks must also be completed before billing.
See where the visit stands without confusing submission with acceptance. Caregiver submission, server receipt and internal verification are separate milestones. Aggregator acceptance is tracked where applicable, and billing follows the required verification, authorization and documentation checks.
Caregiver submitted
Point-of-care upload initiated
Synchronized
Server receipt confirmed
Internally verified
Rules and schedules match
Aggregator accepted, where required
State/payer EVV approved
Eligible for billing after checks
Clean claim generation
An aggregator rejection returns the visit for correction. It does not erase the original visit record or mean that payment has been approved.
Talk to Elixir about your Salesforce setup, caregiver workflows and state or payer EVV requirements.
