Continuity work, with the boundary visible.

What it draws on.

Depending on platform access: the documented nutrition intervention or ADIME note, appointment status, cancellations and no-shows, patient messages, questionnaires, food logs, and other practice records that are actually available. Each proposed decision should identify its source and what is still unknown.

What reaches the RDN.

Exceptions, not every patient. A booked visit can mean ABSTAIN. A missing fact can mean ASK RDN. A question clearly covered by the documented intervention can produce a SUPPORT draft for review. An expired intervention, medication decision, concerning symptom, or other boundary can RETURN CONTROL.

Prior silence never increases KeyRD’s authority to contact a patient. No reply is uncertainty, not permission to intensify outreach.

Where you see it.

The current evaluation uses a bounded review workflow rather than pretending a finished Healthie or Practice Better placement already exists. Platform-native placement and which staff roles may act on which items remain product requirements to validate with practices.

Four responses, one vocabulary.

SUPPORT proposes help within what the RDN documented. ASK RDN returns a missing fact or judgment to the RDN. ABSTAIN avoids an unnecessary next step. RETURN CONTROL stops when the next step exceeds the intervention or belongs elsewhere.

In shadow mode, these are proposals for RDN review. Nothing is automatically sent to patients.

Visit limits are context, not instructions.

If a patient reaches an MNT visit limit, KeyRD should surface that constraint—not infer coverage or manufacture an outreach opportunity. The practice may need benefits verification, scheduling, a self-pay discussion, pause, discharge, or no action.