An Alora home care software alternative is worth evaluating when your Minnesota agency's programs go beyond skilled and non-skilled home care: Community First Services and Supports (CFSS) with its worker file and authorization rules, Adult Rehabilitative Mental Health Services (ARMHS) under Chapter 245I, 245D home and community-based services, Early Intensive Developmental and Behavioral Intervention (EIDBI), or attendance-based adult day services. Alora Health, an Atlanta company founded in 2005, describes a national home health and home care platform with Minnesota-specific electronic visit verification (EVV) that transmits to HHAeXchange. Nothing in this guide argues that it is a poor product.
The question is fit against Minnesota's rules. The Department of Human Services (DHS) now enforces an 80 percent EVV threshold, runs pre-payment review on PCA/CFSS claims, and asks for the complete record by client and date range during Revalidate 2026 site visits. A system built around home health episodes and aide visits may handle those well; it may or may not enforce ARMHS note elements, 245D incident timelines, or adult day attendance.
This guide covers why agencies look, what Alora Health says about itself (attributed to its own website), a neutral comparison table, a migration checklist, and the questions to put to any vendor, including Trustora. It reflects Minnesota rules as of September 2026.
Why Minnesota agencies evaluate an Alora alternative
Five pressures come up in most evaluations. None is a criticism of any one product.
- Program-specific enforcement. ARMHS notes must carry the elements in Minn. Stat. § 245I.08, subd. 4. 245D incident reports are due within 24 hours under § 245D.06. CFSS agencies document worker competency at 30 days and every 90 days in the first year. EIDBI plans must justify the 97155 proportion. Adult day billing rests on attendance. A note designed for home health does not know those rules unless it was built for them.
- Pre-payment review. DHS pre-payment review applies to 14 high-risk services, including PCA/CFSS and individualized home supports. The claim must carry its evidence before payment.
- The EVV threshold. Since January 1, 2026, providers subject to EVV must be enrolled with HHAeXchange and submit complete data for all visits, including noncompliant ones. At least 80 percent of visits billed after July 1, 2026 must be EVV compliant, and corrective action for providers under 80 percent begins in October 2026. The Minnesota EVV requirements guide explains the escalation.
- Audit readiness. Revalidate 2026 site visits and record requests ask for the complete record for a client and date range, including the worker file behind each claim.
- Pricing model. Per-user or percentage-of-collections pricing grows with the agency; some owners want a cost they can forecast.
What Alora Health says about itself
Everything in this section comes from Alora Health's own website or its own press release. Confirm current details with Alora Health before relying on them.
- Company. Alora Health's homepage lists a headquarters address in Atlanta, Georgia. Its December 8, 2016 press release announcing AideConnect states that Alora was founded in 2005 by Sathish John.
- Scope. The homepage describes a cloud platform for home health, home care (personal care, companion care, private duty, homemaker, respite), hospice, and pediatric home care, with native offline apps for iPhone, iPad, and Android and one-click electronic faxing.
- Minnesota pages. Alora Health publishes a Minnesota home health software page and a Minnesota EVV page. They state that Alora handles both skilled and non-skilled home care for Minnesota, including Personal Care Assistance (PCA), homemaker, and respite care, with clinical documentation by discipline (assessment, plan of care, and note) and plan-of-care-based visit notes.
- EVV. The Minnesota EVV page describes a "Minnesota Medicaid Certified" EVV solution, states that Alora captures visit information and automatically transmits it to the EVV data aggregator, HHAeXchange, and describes telephony as a backup to GPS-based EVV. It describes capture of patient and caregiver signatures with visit start and end times and GPS location, live monitoring with alerts for delayed visits and no-shows, and use without internet connectivity. The general EVV page lists connectivity with the Sandata, Netsmart, HHAeXchange, and CareBridge aggregators.
- Billing. The Minnesota page lists billing for all payers: Medicare, Minnesota Medicaid/Waiver, managed care, private insurance, VA, and private pay, and names UCare, Blue Cross, HealthPartners, and UnitedHealthcare among the Minnesota payers handled.
- AideConnect. Alora Health describes AideConnect as an optional integrated solution for non-skilled care. Aides view schedules, capture start and end times with GPS, capture their own and the patient's signature, and complete care-plan-based visit notes. Agencies see a live, color-coded view of visits as started, completed, delayed, or no-show, and a completed visit is readied for billing and payroll.
Alora Health's Minnesota pages name PCA, homemaker, respite, and skilled care; they do not mention CFSS, ARMHS, 245D, EIDBI, or adult day services by name, worker competency visit tracking, or a DHS audit export. That is not a finding that the product lacks any of it; each is a question for the demo.
A comparison framework for Minnesota agencies
Use the same criteria for every candidate and for whatever you run today, and ask for a live demonstration of each row with your own client files.
| Criterion | What to ask any vendor |
|---|---|
| EVV to HHAeXchange | Show a rejected visit, the correction, and the resubmission. Are noncompliant, manual, and telephony visits transmitted too? |
| Caregiver app | GPS clock-in and clock-out, offline capture with later sync, client signature, tasks from the service delivery plan, manual entry only with a reason code and supervisor review |
| Live monitoring | How do delayed and missed visits reach a scheduler, and how is a late visit documented without becoming a manual entry? |
| Authorization tracking | Does scheduling warn or block when a shift is outside the service agreement or exceeds remaining units? |
| Program templates | Show the CFSS visit record, the ARMHS progress note with § 245I.08 elements, the 245D incident report, the EIDBI ITP, and the adult day attendance sheet |
| Pre-claim gate | Which checks run before an 837P line is released: eligibility, authorization, worker enrollment and affiliation, credentials, modifiers, EVV match? |
| Remittance | Is the 835 posted automatically, with denied lines queued and adjustment reason codes attached? |
| Audit export | Can you produce the complete record for one client and one date range in one step? |
| Security | Signed BAA, encryption at rest and in transit, second factor at login, role-based access, append-only audit log |
| Pricing | Per user, per client, percentage of collections, tiers, or flat fee; which modules are optional add-ons; minimum term; export cost |
Compliance note: when a vendor names a Minnesota program, ask to see the completed record next to the statute or rule it satisfies. A demo that cannot point to § 245I.08 or § 245D.06 will not help you point to it during a DHS review.
The PCA and CFSS software buyer's guide expands the EVV and authorization rows and covers the worker file, the ARMHS software buyer's guide covers the 245I rows, and the HIPAA compliance guide explains the BAA and audit log.
Pricing models, described neutrally
Vendors price this software per user or caregiver, per client or visit, as a percentage of collections, in feature tiers, or as a flat monthly fee, and none is wrong in itself. Model each at the size you expect in two years, add implementation, migration, support, and add-on modules, and read the contract for minimum terms and export fees.
Migration checklist
Switching platforms is a data and billing project first. Work through these steps in order.
- Inventory the data. Clients, workers, service agreements, schedules, visits with GPS and signature data, timesheets, plans, claims, and remittance history, plus anything kept outside the platform.
- Request a full export in a documented format with a data dictionary, and check the contract for export cost and timing before giving notice.
- Decide what to import. Demographics, active authorizations, and current plans usually import as structured data; older visits and notes may arrive as documents. Confirm how signatures are preserved.
- Keep EVV continuous. Update HHAeXchange enrollment to name the new system, complete the API configuration, and import caregivers before the first visit. Do not let two systems send the same day's visits.
- Work open claims from the old system until every one is adjudicated, and decide who does that and in which system.
- Configure and validate each program's templates against the framework table with your compliance lead.
- Run in parallel for one full billing cycle, then cut over just after a remittance with MN-ITS, clearinghouse, managed care, and HHAeXchange setups confirmed.
- Retain the old record for the longer of the HIPAA six-year period and the five-year MHCP billing record rule in Minn. R. 9505.2190.
Audit tip: before cutover, pull the same client's record for the same month from both systems and compare them field by field. Any difference is a question a reviewer may ask later.
The Caretap alternatives guide and Billiyo alternatives guide apply this framework to two Minnesota-based platforms, and the Procentive alternatives guide covers agencies leaving a behavioral health EHR.
Questions to ask any vendor
Send the same list to every vendor, including Trustora, in writing, and keep the answers with the contract.
- Will you sign a BAA, and do your subcontractors sign one with you?
- Which Minnesota programs do you support with program-specific templates? Show the CFSS visit record, the ARMHS progress note, the 245D incident report, the EIDBI ITP, and the adult day attendance record.
- How do visits reach HHAeXchange, how does a rejection appear, who resubmits it, and are manual and telephony visits transmitted?
- Which pre-claim checks run automatically, and can we see the 835 reason codes on each claim line?
- What is the pricing model, which modules are optional, what is the term, and what does an export cost?
- What does onboarding include, how long does it typically take, and who does the migration work?
- What is in the audit log, how long is it kept, and can we export it for a date range?
How Trustora helps
Trustora is one platform for PCA/CFSS, ARMHS, 245D, EIDBI, and adult day services, built for Minnesota agencies that run more than one program. The caregiver EVV app on iOS and Android captures GPS clock-in and clock-out and client signatures, visits are transmitted to the HHAeXchange aggregator, and clinical documentation enforces the required fields for each program. The compliance engine runs a pre-claim gate and gap-day alerts, the claims lifecycle covers eligibility, 837P, ERA reconciliation, denials, and appeal packets, and the one-click DHS audit binder assembles a client's record for any date range. The Minnesota home care software, Minnesota EVV software, and ARMHS software pages show each workflow.
On the questions above: pricing is one flat monthly fee with unlimited users and clients, no per-seat fees, no percentage of collections, and a month-to-month term. Trustora runs on HIPAA-eligible AWS with AES-256 encryption at rest, TLS 1.3 in transit, a one-time code on every login, role-based field-level access, and an append-only SHA-256-chained audit log retained for seven years; a BAA is included. Onboarding, migration, and training are included and typically take one to two weeks.