What a Minnesota 245D service-recipient record actually requires
A sourced map of the record categories in Minn. Stat. § 245D.095 and why a completed packet is only one part of the evidence.
Admissions & reviewsResearch & evidence8 min readPublished 2026-09-12Evidence review due 2026-12-01
Short answer
Section 245D.095 requires a uniform, legible, current record for each person served. The record includes signed admission information; the support plan and addendum; assessments; health-service documentation; provider coordination; rights orientation; financial authorization; complaints; incidents; progress and review information; and discharge documentation. It must be protected against loss, tampering, and unauthorized disclosure.
The record is a chain, not a folder name
The statute identifies categories of information, but accountability comes from the relationship between them. The current support plan should connect to staff instructions, documented services, progress, team review, and any revision. A form that exists but describes a different version of the plan weakens the chain.[1][2]
Location and protection matter too. Records must be maintained where services are provided or coordinated as the statute specifies, and protected from loss, tampering, or unauthorized disclosure. Electronic storage does not remove those duties.[1]
Four tests for every record category
For each required category, ask whether it is present, current, attributable, and connected. Present means it exists. Current means the applicable version and date are clear. Attributable means the author, source, signature, or decision owner can be identified. Connected means a reviewer can trace it to the person, service, action, and next obligation.
Presence: can staff retrieve it promptly?
Currency: is the active version unmistakable?
Attribution: who supplied, decided, completed, and reviewed it?
Connection: what plan, event, service, or deadline does it support?
Source-first automation
nnipa is built for this chain. It reads the documents a provider already received, structures supported facts with provenance, generates the applicable packet, and keeps unresolved items visible. Most software begins after a person has typed the record. nnipa begins at the source document, where drift and duplicate entry start.
Questions people ask
Can the service-recipient record be electronic?
Yes, but the statutory protection, access, location, legibility, and record-content duties still apply. Evaluate any additional privacy and security obligations with qualified counsel.[1]
Is a blank form evidence of compliance?
No. It may support a workflow, but compliance evidence depends on the required action and the completed, timely, person-specific record.
Minnesota Statutes, Chapter 245DMinnesota Office of the Revisor of Statutes · accessed 2026-09-12 · The Revisor page may not yet incorporate every effective-dated 2026 amendment; cited session laws control where noted.
This resource is educational, not legal, licensing, tax, accounting, clinical, or investment advice. Rules, rates, and agency implementation can change. Check the linked primary sources and obtain advice for your specific service, person, property, and license before acting.
