The small 245D provider's operating system: five records that must agree

The five-record test

Start with authorization and current plans. Link them to person-specific staff competence, then to delivery and incident evidence, then to the progress and review record. Section 245D.095 names many of these categories; sections 245D.071, 245D.081, and 245D.09 connect them to planning, oversight, and staff competence. [1][2][3][4]

The operational question is not whether every document exists. It is whether a coordinator can explain which version governed a shift, which staff had been trained on it, what changed, and which later review absorbed the change.

Design the handoff before adding volume

One excellent owner can hold a first home together through memory. That is not a transferable operating system. Name the identifiers, record owners, version rules, review cadence, exception route, and minimum evidence before adding another site or delegating coordination.

• One durable identifier per person—never a name-based folder key.
• One visible current version and a retained history.
• One owner for every deadline and unresolved item.
• One documented handoff from source document to staff instruction.
• One review loop that turns incidents and progress into plan changes.

nnipa owns the source-to-packet layer

nnipa is deliberately not a generic EHR or EVV system. It is a Minnesota-first document operations system: it reads the county and provider documents already held, structures facts with provenance, prepares admission and review packets, and keeps the statutory and plan-driven review clock visible. Its MCP interface gives an authorized AI assistant a governed way to call those operations instead of improvising against folders.