What software does a PCA agency in Minnesota need?

At minimum, a Minnesota PCA or CFSS agency needs a system that captures electronic visit verification (EVV) data and sends it to the HHAeXchange aggregator, schedules workers against the lead agency service authorization, produces 837P claims for MN-ITS or a clearinghouse, and stores worker training, competency visit, and background study records. Many agencies run these as one platform; the important part is that the visit, the schedule, the claim, and the worker file agree with each other.

Do I have to use HHAeXchange for EVV in Minnesota?

You must be enrolled with HHAeXchange and your visit data must reach it, but you do not have to use HHAeXchange's own caregiver app. Minnesota DHS provides the HHAeXchange EVV system at no cost. Providers may instead use a third-party EVV system, at their own expense, as long as it meets the state's technical specifications and integrates with HHAeXchange through the EDI or API process. Either way, HHAeXchange collects all visit data and produces the monthly compliance report DHS uses.

What should a caregiver EVV app do?

It should record the type of service, the client, the date, the location, the worker, and the start and stop times automatically at clock-in and clock-out, which are the six elements the 21st Century Cures Act requires. It should keep working without a signal and sync later, capture a client or representative signature, show the worker only the tasks on the client's plan, and make manual entry an exception with a reason code rather than a normal path.

How should software track CFSS service authorizations?

The system should store each service authorization letter with its start and end dates, authorized units, procedure code, and modifiers, and decrement remaining units as visits are verified. Scheduling should warn or block when a shift falls outside the authorization period or would exceed the remaining units. When the lead agency issues a new authorization, for example after a model switch, the old and new periods should not overlap on the same claim.

How is home care software usually priced?

Common models are a per-user or per-caregiver seat fee, a per-client or per-visit fee, a percentage of collections for systems that include billing services, tiered plans by feature set, and a flat monthly fee. Each has trade-offs: per-seat and per-client pricing scales with growth, percentage-of-collections pricing scales with revenue, and flat pricing is easiest to forecast. Ask for the total cost at your expected headcount and caseload, including implementation and support.

What HIPAA and security features should PCA agency software have?

The vendor should sign a business associate agreement, encrypt protected health information at rest and in transit, require multi-factor or one-time-code login, provide role-based access so a worker sees only assigned clients, keep an audit log that records who viewed or changed each record, and describe backup and retention practices. Ask where data is hosted and how long records are retained after you leave, since Minnesota providers must keep service records available for DHS audits.

PCA agency software in Minnesota: what CFSS providers should look for

Short answer

PCA agency software for a Minnesota CFSS provider has to do four things at once: capture every visit through electronic visit verification (EVV) and send it to the HHAeXchange aggregator, keep schedules inside the lead agency service authorization, turn verified visits into clean 837P claims, and hold the worker training, competency visit, and background study records DHS asks for. Evaluate a system on those four jobs, then on security, HIPAA terms, and a pricing model your agency can forecast.

Key takeaways

Any third-party EVV system in Minnesota must integrate with HHAeXchange, the state aggregator, and the provider pays for that system; the state-provided HHAeXchange system is free.
The caregiver app must capture the six Cures Act data elements at clock-in and clock-out, work offline, and support a client signature, because manually entered visits count as noncompliant.
Scheduling should be bounded by the service authorization period and remaining units so a shift cannot be created that the claim will later deny.
Claims should be built from verified visits with a pre-claim check on eligibility, authorization, worker enrollment, credentials, and modifiers, and the 835 remittance should reconcile automatically.
Worker files need training certificates, the 30-day and 90-day competency visits, NETStudy 2.0 background study results, and OIG exclusion checks, with alerts before anything lapses.
Ask for a signed business associate agreement, encryption at rest and in transit, role-based access, and an immutable audit log before you look at price.

PCA agency software is no longer a scheduling tool with a billing export. In Minnesota, as of September 2026, the system that runs a Personal Care Assistance (PCA) or Community First Services and Supports (CFSS) agency is also the system that decides whether the agency passes its electronic visit verification (EVV) threshold, whether claims survive pre-payment review, and whether the worker file can be produced when the Department of Human Services (DHS) asks.

The differences between systems show up in whether the visit record, the schedule, the claim, and the worker's credentials are the same data or four copies that drift apart. This guide lists what to evaluate: EVV and the HHAeXchange aggregator, the caregiver app, scheduling against the authorization, timesheets to claims, worker credentials, payroll, security, pricing, and demo questions.

It describes the jobs the software has to do under the rules in the PCA to CFSS transition guide and the Minnesota EVV requirements guide; it does not rank vendors. If your agency is new to the program, what CFSS is explains the two models and the records they generate.

EVV integration with the HHAeXchange aggregator

HHAeXchange is Minnesota's state EVV aggregator. It collects visit data from every EVV system in the state, produces the monthly compliance report DHS uses, and, since January 1, 2026, every provider subject to EVV must be enrolled with it regardless of which system captures the visits. Providers have two paths:

The state-provided system. DHS provides the HHAeXchange EVV portal and caregiver app at no cost to the provider.
A third-party system. The provider may use another EVV system at its own expense, provided the system meets DHS's business and technical requirements and integrates with HHAeXchange through the Electronic Data Interchange (EDI) process.

For a third-party system, the HHAeXchange getting-started checklist describes what the integration has to do: an API configuration ticket, a caregiver data import before visits can flow, ongoing visit submission, and a process for resolving import rejections. Ask a vendor to show you a visit HHAeXchange rejected and how a scheduler fixes and resubmits it; unresolved rejections never count toward compliance.

Also ask whether the system submits noncompliant visits. DHS requires complete data for all visits, including manual and edited ones, and a system that sends only clean visits will show a better rate inside the app than on the report DHS reads.

Caregiver mobile app requirements

The caregiver app is where compliance is won or lost, because a visit is only compliant if it was captured electronically at the time it happened. The 21st Century Cures Act requires the EVV system to verify six elements: the type of service, the individual receiving it, the date, the location, the individual providing it, and the start and stop times. Check the app against that list, then against how caregivers actually work.

Requirement	Why it matters in Minnesota
GPS clock-in and clock-out	Location is one of the six required elements; the app should capture it automatically, not ask the worker to type an address
Offline capture and later sync	Rural routes and apartment buildings lose signal; a visit captured offline and synced is still electronic, a visit typed in afterward is manual
Client or representative signature	Supports the time and activity documentation MHCP requires and helps resolve disputes about whether a visit occurred
Task list from the service delivery plan	The worker records what was done against the participant's plan, which is the documentation DHS reviews for CFSS
Shared-services support	One worker, two or three participants, same time and place, billed under the CFSS shared-services rule
Manual entry as an exception	Manual visits count as noncompliant; the app should require a reason code and route the visit to a supervisor
iOS and Android, low-end devices	Workers use their own phones; the app must run on what they have

Scheduling and authorization tracking

In the CFSS agency model, the lead agency authorizes units, and Minnesota Health Care Programs (MHCP) pays only for services on the service authorization. Scheduling therefore has to know the authorization. Look for:

The service authorization letter stored with its start and end dates, procedure code, modifiers, and unit total.
Remaining units that decrement as visits are verified, not just as shifts are scheduled.
A block or warning when a shift falls outside the authorization period or would exceed the remaining units.
Handling for authorization changes, such as a participant switching from the budget model to the agency model, so the two periods do not overlap on one claim.
Eligibility checks each month so a schedule is not built for a participant whose MHCP coverage lapsed.

Timesheets to claims

The claim should be built from the verified visit. Units are 15 minutes each and are computed from the clock times, so a system that lets a biller type units independently of the EVV record creates a gap an auditor will find. The CFSS billing guide lists the code table and the pre-claim checks; the software should run those checks before a line is released:

Active service authorization for the date of service and remaining units.
Participant eligibility for the month.
Rendering worker enrolled with MHCP and affiliated with the agency on the service date, with the UMPI or NPI on the line.
Agency credentials (surety bond, fidelity bond, liability, workers' compensation) current on the provider record.
Modifiers that match the worker's training status and the authorization.
One line per date of service per code and modifier, with no duplicates.

Then the claim goes out as an 837P to MN-ITS or a clearinghouse, and the 835 electronic remittance advice comes back. Ask whether the system posts the 835 automatically and puts denied lines in a queue with the adjustment reason attached. The MHCP claim denials guide describes what that queue should let a biller do.

Worker credential tracking

DHS reviews the worker file against the claim dates. Under Minn. Stat. § 256B.85, a CFSS agency must verify a new worker's competency by direct observation within 30 days of the worker starting, keep evidence of competency, and complete performance reviews at least annually; DHS guidance describes competency visits every 90 days, in person during the first year. The worker file should hold, with dates and alerts:

Individual PCA/CFSS training certificate (workers with a certificate dated before April 15, 2020 need a new one).
NETStudy 2.0 background study result under Minn. Stat. ch. 245C.
OIG exclusion list check.
MHCP individual enrollment and affiliation start and end dates.
Competency visits at 30 days and every 90 days, with who observed and what was observed.
Trainings that qualify the worker for the enhanced rate, and the date the agency verified them with DHS.
Cumulative PCA and CFSS hours for tier placement.

The test: ask the system to list every worker with a competency visit due in the next 14 days, and every worker who billed after a credential expired. If it cannot answer both, the file is a filing cabinet, not a control. The CFSS support worker requirements guide explains each item in the file and the statute behind it.

Payroll

Agency-model rates are tiered by worker experience, and § 256B.85 requires that at least 72.5 percent of CFSS revenue go to worker wages and benefits. Most agencies keep a dedicated payroll provider; what to look for in the agency software is an auditable export of verified hours per worker per pay period and a report that compares hours paid to units billed, because a gap between those numbers is one of the first things a DHS reviewer computes.

HIPAA and security

Every participant record is protected health information. Before price, confirm the vendor will sign a business associate agreement, encrypts data at rest and in transit, requires a second factor at login, offers role-based and field-level access so a worker sees only assigned participants, and keeps an audit log of who viewed and changed each record that cannot be edited afterward. Ask where data is hosted, how backups work, and how you get your data out if you leave. The HIPAA compliance guide for Minnesota home care agencies covers what a BAA should say, and Trustora's security page is an example of how a vendor should describe these controls in writing.

Pricing models, described neutrally

Home care software is priced in several ways, and none is wrong in itself. What matters is that you can forecast the cost at the size you expect to be in two years.

Model	How it scales	What to ask
Per user or per caregiver seat	With headcount, including turnover and part-time workers	Are inactive or seasonal workers charged?
Per client or per visit	With caseload and visit volume	Is there a minimum? What counts as a visit?
Percentage of collections	With revenue, usually bundled with billing services	What is included, and what is the effective rate at your volume?
Tiered feature plans	With the features you need, which often means the top tier for compliance	Which tier includes EVV integration, claims, and the audit log?
Flat monthly fee	Does not change with users or clients	Are implementation, training, migration, and support included?

Add implementation, migration, training, and support to every quote. Trustora's pricing page shows one flat-fee approach; compare it against the others with your own numbers. If you are replacing a general behavioral health EHR rather than spreadsheets, the Procentive alternatives guide has a migration checklist that applies to any vendor switch.

Questions to ask on a demo

Show me a visit that HHAeXchange rejected and how it gets fixed and resubmitted.
Show me the monthly compliance rate for last month, by worker, and how it was computed.
Schedule a shift that exceeds the remaining authorized units. What happens?
Release a claim for a worker whose affiliation ended last week. What happens?
List every worker with a competency visit due in the next 14 days.
Post an 835 and show me the denied lines and their reason codes.
Show me the audit log entry for the last change to a participant's service delivery plan.
What is in the BAA, and where is the data hosted?
What is the total cost at our headcount and caseload, including onboarding?
How do we export everything if we leave?

Run the same ten questions with each vendor. The EVV compliance checklist is a good companion, because the system you choose is the one you will run that checklist in.

How Trustora helps

Trustora is one platform for PCA/CFSS, ARMHS, 245D, EIDBI, and adult day services. For a PCA or CFSS agency, the caregiver app on iOS and Android captures GPS clock-in and clock-out, works offline and syncs later, and records the client's signature; visits flow to the HHAeXchange aggregator, and manual entries are flagged with a reason code for supervisor review. Scheduling is bounded by the stored service authorization, and the pre-claim gate checks authorization, eligibility, worker enrollment, credentials, and modifiers before an 837P line is released. The 835 remittance is reconciled automatically.

Worker files track training, background studies, and the 30-day and 90-day competency visits with alerts, and the one-click audit binder assembles a participant's record and worker qualifications for any date range. 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 audit log retained for seven years; a BAA is included. Pricing is one flat monthly fee with unlimited users and clients, month to month, with onboarding, migration, and training included. See the features page for details.

Frequently asked questions

What software does a PCA agency in Minnesota need?: At minimum, a Minnesota PCA or CFSS agency needs a system that captures electronic visit verification (EVV) data and sends it to the HHAeXchange aggregator, schedules workers against the lead agency service authorization, produces 837P claims for MN-ITS or a clearinghouse, and stores worker training, competency visit, and background study records. Many agencies run these as one platform; the important part is that the visit, the schedule, the claim, and the worker file agree with each other.
Do I have to use HHAeXchange for EVV in Minnesota?: You must be enrolled with HHAeXchange and your visit data must reach it, but you do not have to use HHAeXchange's own caregiver app. Minnesota DHS provides the HHAeXchange EVV system at no cost. Providers may instead use a third-party EVV system, at their own expense, as long as it meets the state's technical specifications and integrates with HHAeXchange through the EDI or API process. Either way, HHAeXchange collects all visit data and produces the monthly compliance report DHS uses.
What should a caregiver EVV app do?: It should record the type of service, the client, the date, the location, the worker, and the start and stop times automatically at clock-in and clock-out, which are the six elements the 21st Century Cures Act requires. It should keep working without a signal and sync later, capture a client or representative signature, show the worker only the tasks on the client's plan, and make manual entry an exception with a reason code rather than a normal path.
How should software track CFSS service authorizations?: The system should store each service authorization letter with its start and end dates, authorized units, procedure code, and modifiers, and decrement remaining units as visits are verified. Scheduling should warn or block when a shift falls outside the authorization period or would exceed the remaining units. When the lead agency issues a new authorization, for example after a model switch, the old and new periods should not overlap on the same claim.
How is home care software usually priced?: Common models are a per-user or per-caregiver seat fee, a per-client or per-visit fee, a percentage of collections for systems that include billing services, tiered plans by feature set, and a flat monthly fee. Each has trade-offs: per-seat and per-client pricing scales with growth, percentage-of-collections pricing scales with revenue, and flat pricing is easiest to forecast. Ask for the total cost at your expected headcount and caseload, including implementation and support.
What HIPAA and security features should PCA agency software have?: The vendor should sign a business associate agreement, encrypt protected health information at rest and in transit, require multi-factor or one-time-code login, provide role-based access so a worker sees only assigned clients, keep an audit log that records who viewed or changed each record, and describe backup and retention practices. Ask where data is hosted and how long records are retained after you leave, since Minnesota providers must keep service records available for DHS audits.

Sources and further reading

Cite this article

Trustora Editorial Team. (2026, September 10). PCA agency software in Minnesota: what CFSS providers should look for. Trustora. https://trustora.com/blog/pca-cfss-agency-software-minnesota-buyers-guide

ShareLinkedIn X Facebook Email

This article is general information for Minnesota agencies, not legal, clinical, or billing advice. Minnesota DHS policy changes often. Confirm current requirements in the MHCP Provider Manual, the Minnesota Statutes, and DHS provider notices before acting on anything here.