What does a meaningful plan connection look like?
It shows which participant-selected goal the service addressed, what the peer did within role, how the participant responded, what changed or remained difficult, and what the participant and peer agreed to do next.
CMS describes Medicaid peer support as coordinated within a person-centered plan of care, while SAMHSA's peer competencies emphasize recovery orientation, person-centered practice, strengths, choice, and role clarity. The connection should preserve those principles instead of turning the note into a clinical treatment narrative.[1][2]
Which records and versions should be linked?
Link references rather than copy whole documents. The note should retain the goal and plan version relevant to the service date so later plan changes do not alter historical meaning.
| Criterion | How to evaluate it |
|---|---|
| Current plan | Plan identifier, effective date, participant involvement, status, responsible roles, and review date are visible. |
| Selected goal | The exact goal or objective addressed is understandable and preserves the participant's own priorities and language. |
| Service action | The peer's support, skill, navigation, connection, advocacy, modeling, or other approved activity is specific. |
| Participant response | The record describes what the participant said, chose, tried, learned, accepted, declined, or identified. |
| Progress or barrier | The note connects evidence to the goal without unsupported clinical interpretation or a copied generic phrase. |
| Next step | The participant's decision, peer follow-up, responsible person, timing, and any needed referral or supervision are clear. |
How should the workflow handle change?
A participant can revise priorities, decline an activity, or make progress that changes the next step. The system should preserve history and support a new plan decision without rewriting earlier records.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Plan active | Peer selects an appropriate current goal before or during documentation | Note stores goal and plan-version reference |
| Goal not addressed | Encounter remains truthful and is routed under the correct service or exception process | No forced or invented goal connection |
| Priority changed | Participant choice is documented and the responsible person reviews whether the plan should change | Old plan remains historical; new version has effective date |
| Goal completed | Progress and participant view are recorded before closure or replacement | Completion does not erase prior services |
| Plan expired or missing | Workflow holds any decision that requires a current plan and routes the gap | Software does not silently select an obsolete goal |
What should plan-connected software demonstrate?
Use a plan with multiple goals, a mid-period revision, a participant-declined activity, and a note correction. Confirm what each role can see and change.
- Can the peer see only the plan context needed for the service, with appropriate permissions and consent?
- Does the note preserve the selected goal and plan version as of the service date?
- Can the participant's language be retained without converting it into a clinical conclusion?
- Who can revise the plan, close a goal, approve a change, and correct a note?
- Can reports distinguish services linked to active, expired, missing, completed, or changed goals?
What should never be automated?
Software should not invent a goal connection, decide what the participant values, reinterpret a peer service as treatment, or silently change a signed note when a plan changes.
Use automation to present current choices, carry reliable references, detect missing links, and route review. The participant, peer, supervisor, and other authorized roles retain their real responsibilities for goal choice, service truth, plan changes, record accuracy, and scope.
Frequently asked questions
Must every peer contact connect to a recovery-plan goal?
Requirements vary by program, funder, state, payer, service, and contract. Confirm the controlling source. Never invent a connection when one did not exist.
Should the full recovery plan appear in every note?
Usually the useful approach is a controlled reference to the relevant current goal and plan version, not copying unnecessary sensitive content into every record.
Can a peer change the recovery plan?
Follow the program's person-centered planning process, role definitions, and applicable rules. The software should make authority and approval clear rather than assuming every user has the same rights.
What if the participant changes priorities during the service?
Document the participant's actual choice and route any needed plan review. Preserve the plan and note history with effective dates.
Sources and product pages
Government sources establish the legal and program requirements covered here. Official vendor pages document the product capabilities and positioning used in this guide.
- Medicaid and CHIP Coverage of Peer Support Services FAQ: Centers for Medicare & Medicaid Services. Federal baseline explaining state authority over peer qualifications, supervision, and benefit design.
- Core Competencies for Peer Workers in Behavioral Health Services: Substance Abuse and Mental Health Services Administration. Federal framework for recovery-oriented peer work, role clarity, and person-centered practice.
- Document: Notes, Assessments, and Supervisor Review: Peerakeet. Peerakeet structured notes, assessments, signatures, and review workflows.