What should ARMHS software enforce in Minnesota?

At minimum: the assessment chain in statutory order (diagnostic assessment, functional assessment with narratives in all ten § 245I.10, subd. 9 domains, level of care, then treatment plan); every § 245I.08, subd. 4 progress note element as a required field; goal selection from the current approved plan; unit calculation from clock times; supervisor approval within ten business days; mental health rehabilitation worker co-signature routing; 180-day plan review and 365-day functional assessment tracking; and a pre-claim check that holds H2017 lines when any of these is missing.

Do I need ARMHS-specific software or will a general EHR work?

A general behavioral health record can store ARMHS documentation, but it usually does not enforce the Minnesota-specific chain: the ten functional assessment domains, the ten-business-day approval rule, MHRW co-signature, H2017 units from note times, or the HM and HQ modifier logic. Agencies using general systems typically bolt on spreadsheets and manual review to cover those gaps. When evaluating, ask the vendor to demonstrate each 245I requirement in the product rather than describe it as configurable.

How are ARMHS software vendors typically priced?

Three models are common. Per-seat pricing charges per user per month, which grows with staff count. A flat monthly fee charges one price regardless of users and clients. Percentage-of-collections pricing takes a share of what the agency collects, which grows with billing volume and can be hard to forecast. None is inherently right; model the total annual cost at your actual staff count and claim volume, including implementation, training, and any per-claim or clearinghouse fees.

What security features are required for ARMHS software under HIPAA?

The HIPAA Security Rule requires administrative, physical, and technical safeguards for electronic protected health information, and any vendor that stores or processes it for you is a business associate that must sign a Business Associate Agreement. In practice, require encryption in transit and at rest, role-based access limited to the minimum necessary, unique user accounts with multi-factor authentication, automatic logoff, an audit log of who viewed and changed each record, and a documented backup and breach notification process.

How long does migrating an ARMHS agency to new software take?

It depends on the volume and condition of existing records and on whether the vendor includes migration. Plan for exporting client demographics, active assessments, current treatment plans, and open authorizations first, then historical notes. Ask the vendor for a written migration plan, a test import on a sample, and confirmation that historical records remain retrievable for DHS reviews. Some vendors include onboarding, migration, and training in the price; others charge separately. Get the scope in writing.

What are red flags when choosing ARMHS software?

A vendor that cannot show a § 245I.08, subd. 4 note with every element required; units typed by the biller instead of calculated from note times; no co-signature workflow; treatment plan review dates tracked outside the system; no BAA offered or a BAA with vague breach terms; audit logs that cannot be exported; no documented data return process if you leave; and long contracts with fees for exporting your own data. Each of these shifts compliance work back onto your staff.

How to choose ARMHS software in Minnesota: a buyer's checklist

Short answer

ARMHS software for a Minnesota agency has to do more than store notes. It must enforce the chapter 245I assessment chain (diagnostic assessment, functional assessment with ten domain narratives, level of care, treatment plan), require every § 245I.08, subd. 4 progress note element, track supervisor approvals and mental health rehabilitation worker co-signatures, keep supervision logs, generate H2017 claims from note times, and assemble a DHS audit binder on request. This checklist covers those requirements, the questions to ask vendors, pricing models, migration, HIPAA security, and red flags.

Key takeaways

Ask whether the system blocks a note or claim that is missing a 245I element, or only warns; enforcement is what prevents recoupment.
The treatment plan must be linked to the functional assessment and the note must be linked to a plan goal, or the chain is a set of unrelated forms.
Co-signature routing, dated supervisor approvals, and a supervision log should be in the same record as the notes, not in a separate spreadsheet.
Claims should be generated from note start and stop times with the modifier derived from the writer's credential, and held by a pre-claim check when the record is incomplete.
Pricing models differ (per seat, flat fee, percentage of collections); model the total cost at your staff count and claim volume before comparing.
Require a signed BAA, encryption in transit and at rest, role-based access, multi-factor login, and an audit log you can export before signing.

Choosing ARMHS software in Minnesota is a compliance decision before it is a technology decision. Adult Rehabilitative Mental Health Services (ARMHS) are governed by Minn. Stat. § 256B.0623 and the Uniform Service Standards in chapter 245I, and the Department of Human Services (DHS) audits the record against those rules line by line. The software either enforces them at the point of writing or leaves that job to your staff.

The difference shows up in recoupments. A note filed without a treatment plan goal, a plan approved on day twelve instead of day ten, or a claim with more units than the clock times support are all things a system can refuse to let happen. Many general-purpose records will store whatever is typed.

This checklist is for owners, program managers, and billers evaluating a first system or replacing one. It covers what an ARMHS-specific system must enforce, vendor questions, pricing models, migration, security, and red flags, as of September 2026.

What ARMHS software must enforce

Use the statute as the requirements document. The ARMHS documentation requirements checklist explains each item; the table lists what the software should do about it.

Requirement	Rule	What the system should do
Assessment chain in order	§ 245I.10, subds. 6, 8, 9; § 256B.0623, subd. 9	Block a treatment plan until a current diagnostic assessment, a functional assessment, and a level of care assessment exist
Ten functional assessment domains with narratives	§ 245I.10, subd. 9	Require a narrative in each domain and a record of who contributed input
Treatment plan elements	§ 245I.10, subd. 8	Require goals linked to assessed domains, measurable objectives with dates, responsible staff, client approval or documented disagreement
Supervisor approval within ten business days	§ 245I.08, subd. 3	Route practitioner and trainee documents for approval, stamp the date, alert before day ten
Progress note elements	§ 245I.08, subd. 4	Require type, date, clock start and stop, location, goal and objective from the current plan, intervention, response, plan, observations, signature with credentials
MHRW co-signature	§ 256B.0623; DHS ARMHS manual	Route mental health rehabilitation worker notes to the supervisor for a dated co-signature before billing
Supervision and observation logs	§ 256B.0623; § 245I.06	Record monthly clinical supervision and the six-hours-per-40 direct observation for new MHRWs in the same record
Plan review and assessment update cadence	§ 245I.10, subds. 8 and 9	Track 180-day plan reviews and 365-day functional assessment updates with alerts
H2017 claim generation	DHS procedure grid; MHCP billing policy	Calculate units from note times, derive the modifier from the writer's credential, build the 837P
Pre-claim check	Agency policy	Hold any line where eligibility, assessment, plan, approval, co-signature, or times fail
Audit binder	DHS review practice	Produce the full record, supervision log, and staff qualifications for a client and date range on request

Two of these deserve emphasis: the plan must be linked to the functional assessment, and the note to a plan goal. Without those links the system stores three unrelated forms and the reviewer reconstructs the chain by hand. The functional assessment and treatment plan guide shows what the chain looks like when it works.

Audit tip: ask the vendor to file a note with the stop time missing, then to bill it. If either step succeeds, the system warns rather than enforces, and your staff are the control.

Questions to ask vendors

Ask for a demonstration of each question, not a description.

Documentation

Show me a progress note being filed. Which fields are required, and what happens when one is blank?
Show me the goal selector. Does it only list goals from the client's current, approved plan?
Show me the functional assessment. Are all ten domains present with narrative fields and a place to record input from natural supports?
Show me a treatment plan written by a practitioner. Where is the supervisor approval date, and what alerts fire before day ten?
Show me an MHRW note. How is it routed for co-signature, and can it be billed before the co-signature is recorded?

Billing

Show me how units are calculated. Can a biller change the unit count independently of the note times?
Show me how the modifier is chosen for H2017. Is it derived from the writer's credential?
Show me the pre-claim check. What conditions hold a line, and what does the biller see?
Show me an 835 remittance being reconciled and a denial being worked into an appeal packet.
How are the January 1, 2027 ARMHS hour limits in § 256B.0623, subd. 15 going to be tracked? (Four hours per week, 18 hours per month, prior authorization above 200 hours per year.)

Operations

Show me the supervision log and the direct observation record for a new MHRW.
Show me the audit binder. How long does it take to assemble a client's full record for a twelve-month range?
What happens to our data if we leave? In what format, at what cost, and how quickly?

The ARMHS billing guide covers the claim rules behind questions 6 through 10 in detail.

Pricing models, described neutrally

Vendors price in three main ways; compare total annual cost at your real numbers.

Model	How it works	Grows with	What to check
Per seat	A monthly charge per user (sometimes per active client as well)	Staff count	Whether supervisors, billers, and part-time staff each need a paid seat; the cost of adding a worker mid-contract
Flat monthly fee	One price for the agency regardless of users and clients	Nothing, within the plan's terms	What is included (implementation, training, support, clearinghouse), and whether there are tiers
Percentage of collections	The vendor takes a share of what the agency collects	Billing volume	Whether the percentage applies to all payers, how it is calculated on recoupments and adjustments, and how it is audited

Beyond the base model, ask about implementation fees, training fees, per-claim or clearinghouse charges, data export fees, contract length, and what happens to the price on renewal. The Procentive alternatives guide walks through a side-by-side comparison method for Minnesota agencies.

Migration and onboarding

Switching systems is where ARMHS agencies are most exposed, because active clients have assessments, plans, and authorizations in flight. A migration plan should cover:

Active records first. Demographics, current diagnostic assessments, functional assessments, level of care, treatment plans with approval dates, open authorizations, and eligibility. These have to be right on day one so notes can be written and billed.
Historical notes second. Old notes must be retrievable for DHS reviews but need not be editable; a read-only archive is often enough.
Dates preserved. Supervisor approval dates, plan review dates, and co-signature dates must survive migration, or every migrated plan looks unapproved.
A test import. Run a sample of real records through before the full migration and check them against the source.
Staff training by role. MHRWs, practitioners, supervisors, and billers each use different parts of the system.
A cutover date. One date after which all new documentation is in the new system, with a short overlap for billing the last claims from the old one.

Ask whether onboarding, migration, and training are included and how long the vendor expects it to take for an agency your size, and get the answer in writing.

Security requirements: HIPAA, BAA, and audit logs

An ARMHS record is electronic protected health information. The HIPAA Security Rule requires administrative, physical, and technical safeguards, and any vendor that stores or processes that information for you is a business associate that must sign a Business Associate Agreement (BAA) before it touches your data. The HIPAA compliance guide for Minnesota agencies covers the agency-side obligations; the vendor-side minimums are:

A signed BAA that spells out permitted uses, safeguards, subcontractors, breach notification timelines, and data return or destruction at termination.
Encryption of data in transit and at rest.
Unique user accounts, role-based access that limits each role to the minimum necessary, and multi-factor authentication on login.
An audit log that records who viewed, created, changed, or exported each record, that cannot be edited, and that you can export for your own review or for DHS.
Retention that meets Minnesota and federal record requirements for the full period, including after you leave the vendor.
Documented backup, disaster recovery, and incident response procedures.

Ask to see the audit log for a sample record, how long entries are retained, where the data is hosted, and whether the hosting provider signs its own BAA with the vendor. A vendor that cannot produce the log in a demo will not produce it in a breach investigation.

Red flags

The vendor describes 245I compliance as "configurable" but cannot show it working.
Units are typed by the biller rather than calculated from note times.
There is no co-signature workflow, or MHRW notes can be billed before co-signature.
Treatment plan review dates and supervisor approval dates are tracked in a spreadsheet outside the system.
Historical data is not searchable after migration, or old notes are lost.
No BAA is offered, or the BAA is silent on breach notification and data return.
Audit logs cannot be exported, or can be edited.
The contract is multi-year with a fee to export your own data.
Pricing depends on a variable you cannot forecast, with no cap.
The vendor has no answer for the 2027 ARMHS billing limits or the move to ARMHS licensure under chapter 245I that Laws 2026, chapter 121, sets for January 1, 2028.

Each of these means the compliance work stays with your staff, and you should price that in.

How Trustora helps

Trustora is one platform for ARMHS, 245D, PCA/CFSS, EIDBI, and adult day services, and its ARMHS module is built on the enforcement table in this guide. The record requires the diagnostic assessment, a functional assessment with narratives in all ten domains, and a level of care assessment before a treatment plan can be finalized; progress notes require every § 245I.08, subd. 4 element with a goal selected from the current approved plan; supervisor approvals, MHRW co-signatures, and supervision logs live in the same record; and H2017 claims are generated from note times with a pre-claim gate that holds incomplete lines. A one-click audit binder assembles the record for any client and date range.

Trustora is priced as one flat monthly fee with unlimited users and clients, no per-seat fees, no percentage of collections, and month-to-month terms, with onboarding, migration, and training included and typically completed in one to two weeks. Security includes HIPAA-eligible AWS hosting, 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, with a BAA included. See the pricing page and the security overview for details.

Frequently asked questions

What should ARMHS software enforce in Minnesota?: At minimum: the assessment chain in statutory order (diagnostic assessment, functional assessment with narratives in all ten § 245I.10, subd. 9 domains, level of care, then treatment plan); every § 245I.08, subd. 4 progress note element as a required field; goal selection from the current approved plan; unit calculation from clock times; supervisor approval within ten business days; mental health rehabilitation worker co-signature routing; 180-day plan review and 365-day functional assessment tracking; and a pre-claim check that holds H2017 lines when any of these is missing.
Do I need ARMHS-specific software or will a general EHR work?: A general behavioral health record can store ARMHS documentation, but it usually does not enforce the Minnesota-specific chain: the ten functional assessment domains, the ten-business-day approval rule, MHRW co-signature, H2017 units from note times, or the HM and HQ modifier logic. Agencies using general systems typically bolt on spreadsheets and manual review to cover those gaps. When evaluating, ask the vendor to demonstrate each 245I requirement in the product rather than describe it as configurable.
How are ARMHS software vendors typically priced?: Three models are common. Per-seat pricing charges per user per month, which grows with staff count. A flat monthly fee charges one price regardless of users and clients. Percentage-of-collections pricing takes a share of what the agency collects, which grows with billing volume and can be hard to forecast. None is inherently right; model the total annual cost at your actual staff count and claim volume, including implementation, training, and any per-claim or clearinghouse fees.
What security features are required for ARMHS software under HIPAA?: The HIPAA Security Rule requires administrative, physical, and technical safeguards for electronic protected health information, and any vendor that stores or processes it for you is a business associate that must sign a Business Associate Agreement. In practice, require encryption in transit and at rest, role-based access limited to the minimum necessary, unique user accounts with multi-factor authentication, automatic logoff, an audit log of who viewed and changed each record, and a documented backup and breach notification process.
How long does migrating an ARMHS agency to new software take?: It depends on the volume and condition of existing records and on whether the vendor includes migration. Plan for exporting client demographics, active assessments, current treatment plans, and open authorizations first, then historical notes. Ask the vendor for a written migration plan, a test import on a sample, and confirmation that historical records remain retrievable for DHS reviews. Some vendors include onboarding, migration, and training in the price; others charge separately. Get the scope in writing.
What are red flags when choosing ARMHS software?: A vendor that cannot show a § 245I.08, subd. 4 note with every element required; units typed by the biller instead of calculated from note times; no co-signature workflow; treatment plan review dates tracked outside the system; no BAA offered or a BAA with vague breach terms; audit logs that cannot be exported; no documented data return process if you leave; and long contracts with fees for exporting your own data. Each of these shifts compliance work back onto your staff.

Sources and further reading

Cite this article

Trustora Editorial Team. (2026, September 1). How to choose ARMHS software in Minnesota: a buyer's checklist. Trustora. https://trustora.com/blog/armhs-software-buyers-guide-minnesota

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.