A Caretap alternative is worth evaluating when the programs your Minnesota agency runs need more than visit capture and billing: program-specific record enforcement, a pre-claim gate built for Department of Human Services (DHS) pre-payment review, an audit export by client and date range, or a price that stays flat as you hire. Caretap, sold by SRS Web Solutions, Inc. of Ramsey, Minnesota, describes itself as a home care platform with scheduling, electronic visit verification (EVV), electronic timesheets, billing, payroll, and two-way texting. Nothing in this guide argues that it is a poor product.
The question is fit. A Personal Care Assistance (PCA) agency moving to Community First Services and Supports (CFSS) now lives under the 80 percent EVV threshold and pre-payment review. An Adult Rehabilitative Mental Health Services (ARMHS) provider is audited against Chapter 245I record elements. A 245D provider needs incident reports and support plan timelines. Each program adds rules a general home care platform may or may not enforce.
This guide covers why agencies look, what Caretap says about itself (attributed to its own website), a neutral comparison framework, 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 a Caretap alternative
Five pressures come up repeatedly. None is a criticism of any one product. They are the points where Minnesota enforcement has tightened and where an agency should check whether its current system keeps up.
- Program-specific enforcement. DHS reviews ARMHS notes against Minn. Stat. § 245I.08, subd. 4, 245D incident reports against § 245D.06, CFSS visit records against the service delivery plan, EIDBI plans against the 97155 proportion, and adult day billing against attendance. A template that leaves those fields optional pushes the work onto staff memory.
- Pre-payment review. DHS pre-payment review applies to 14 high-risk services, including PCA/CFSS and individualized home supports. A claim now has to carry its evidence before it is paid, not after.
- The EVV threshold. Since January 1, 2026, every provider 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 notices for providers under 80 percent begin in October 2026. The Minnesota EVV requirements guide explains the thresholds and 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-caregiver, per-client, or percentage-of-collections pricing grows with the agency; some owners want a cost they can forecast.
What Caretap says about itself
Everything in this section comes from Caretap's own website. Confirm current details with Caretap before relying on them.
- Company. Caretap is a product of SRS Web Solutions, Inc. Its About page states that since 2014 SRS Web Solutions has built software for the healthcare market, and its headquarters address is in Ramsey, Minnesota.
- Markets named. The homepage lists home care agencies, Applied Behavior Analysis (ABA), mental health services (ARMHS), group homes, adult day care, private duty nursing, and interpreting and translation.
- EVV. The homepage describes a "100% EVV Compliance System" that logs the time, date, and location of visits, with "mobile & landline-based clock-ins." The EVV page describes GPS tracking, the option of clock-in from the client's landline, capture of date, time, and location per the 21st Century Cures Act, point-of-care client signatures, and electronic timesheets signed by caregiver and recipient each pay period.
- Mobile app and telephony. The site lists a caregiver mobile app plus telephony access on iOS, Android, and landlines, two-way texting described as HIPAA-secure messaging, and paperless client intake.
- Billing and payroll. The homepage lists "Automated Billing & Payroll" with Medicaid and private pay automation. The ARMHS page adds direct Medicaid and insurance claim submission, batch claims, a billing dashboard, and weekly and monthly client eligibility updates.
- ARMHS documentation. The mental health page describes electronic diagnostic assessments, functional assessments, individual treatment plans (ITPs), and progress notes.
- Adult day. The adult day care page describes a client attendance mobile app that records attendance and counts hours, with automated billing and claim status tracking.
- HHAeXchange. As of September 2026, DHS's page of third-party EVV systems that providers have reported and that have integrated with HHAeXchange includes Caretap. DHS states that the list is not complete and that the cost of any third-party system is the provider's responsibility.
Caretap's pages we reviewed do not mention CFSS by name, 245D, EIDBI, or offline visit capture. That is not a finding that the product lacks them; it is a list of questions for a 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 visit HHAeXchange rejected, how a scheduler fixes it, and how it is resubmitted. Are noncompliant visits sent too? |
| Caregiver app | GPS clock-in and clock-out, offline capture with later sync, client signature, tasks pulled from the service delivery plan, manual entry only with a reason code |
| Telephony | Is landline clock-in available, and how are those visits flagged and matched to the schedule? |
| Authorization tracking | Does scheduling warn or block when a shift falls 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, credentials, modifiers, EVV match)? |
| Remittance | Is the 835 posted automatically, with denied lines in a queue showing adjustment reason codes? |
| 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 caregiver, per client, percentage of collections, tiers, or flat fee; what is extra; minimum term; export cost |
Compliance note: for each program, ask the vendor to show a completed record next to the statute or rule it is meant to satisfy. If the demo cannot point to the rule, the software will not help you point to it during a DHS review either.
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 from any home care platform is a data and billing project first and a training project second. 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 Procentive alternatives guide covers agencies leaving a behavioral health EHR; the Billiyo alternatives guide and Alora alternatives guide apply this framework to two other platforms.
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, and the adult day attendance record.
- How do visits reach the HHAeXchange aggregator, how does a rejection appear, and who resubmits it?
- Which pre-claim checks run automatically, and can we see the 835 reason codes on each claim line?
- What is the pricing model, what is included, what is extra, and what is the term?
- Who owns the data, what does an export include, what format is it in, and what does it cost?
- What does onboarding include, how long does it typically take, and who does the migration work?
How Trustora helps
Trustora is built for Minnesota agencies that run more than one program. It covers PCA/CFSS, ARMHS, 245D, EIDBI, and adult day services in one platform. The caregiver EVV app on iOS and Android captures GPS clock-in and clock-out and client signatures, visits flow to the HHAeXchange aggregator, and clinical documentation enforces the required fields for each program before a note is complete. The compliance engine runs a pre-claim gate and gap-day alerts, the claims lifecycle handles eligibility, 837P, ERA reconciliation, denials, and appeal packets, and the one-click DHS audit binder assembles a client's record for any date range. See the Minnesota home care software and Minnesota EVV software pages for each workflow, and the PCA and CFSS software page for the agency-model specifics.
On the questions above, the answers are short. 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.