States · Minnesota

Built under 245D — not adapted to it afterward.

ClientCentric's workflows come from real operations under Minnesota's Home and Community-Based Services licensing (Minn. Stat. ch. 245D) — one of the country's most demanding HCBS program contexts. Minnesota is the platform's first preconfigured state.

Support status: Minnesota 245D is ClientCentric’s first state configuration — service categories, documentation defaults and the state timezone come preconfigured, and terminology and workflow defaults are set up deliberately for 245D providers at onboarding, never assumed from another state’s rules. Supported workflows include client records with services and support plans, assignment-based access, scheduling for basic and intensive support services, visit capture with EVV evidence, case notes with a locked lifecycle, documentation periods, timesheets, incidents, consents with expiry, and append-only audit history.

What 245D actually demands of software

245D licensing turns on documentation discipline: who served whom under which service, what was done toward the person’s outcomes, and whether the record can be trusted after the fact. That is why ClientCentric’s case notes lock, why corrections preserve originals, why access follows assignments, and why the audit history is append-only — the reviewer’s questions are designed in, not bolted on.

Program terminology configured for 245D at setup — sources: Minn. Stat. ch. 245D (mn.gov, Office of the Revisor)
EVV evidence captured at clock-in and clock-out, with exceptions queued for review — Minnesota EVV context per DHS guidance
Services that do not require verification display 'not applicable', and compliance math excludes them
Record requests, disclosure logs, and exports as audited events
Migration in with a confidence report, written approval, and rollback window

Honest status lines

Minnesota 245D configuration: service categories, documentation defaults and state timezone preconfigured
EVV evidence capture: available in product
Aggregator transmission: configured per deployment; described as connected only after verification for your agency
Migration: available — the pipeline is part of the product
Other states: configured deliberately per agency, never assumed from another state's rules

Program references: Minnesota Statutes chapter 245D (available from the Minnesota Office of the Revisor of Statutes) and Minnesota DHS provider guidance. This page describes software configuration, not legal advice; licensing obligations remain the provider’s own.

ClientCentric administrator overview for a Minnesota 245D provider: needs-attention queues for exceptions, notes, consents, and credentials, each opening its list

The morning view of a 245D operation. Exceptions, notes awaiting review, clients without assigned staff, expiring credentials — every figure opens the list behind it.

See the Minnesota-shaped workflows in the demo Book a walkthroughNo signup. Fictional data. Everything resets on refresh.

Keep reading

Written and maintained by the ClientCentric team from the working product. Last reviewed 2026-09-03. Minnesota 245D is the platform's first preconfigured state: service categories, documentation defaults and state timezone.