Overview
Form 8665 captures who the individual is, what matters to them, and the outcomes and services the team agreed on. In most HCS agencies the signed PDF lands in a folder and the goals live in the heads of the staff who attended the meeting. Six months later a new DSP writes notes that never mention an outcome, and the surveyor notices before you do.
Sereniq keeps the PDP as an uploaded care-plan document with an effective date and a 365-day expiry. Read this plan runs once per upload: the AI lists every service block and drafts up to three measurable objectives for the services staff support, and a program manager accepts, edits, or rejects each row before anything is saved. Accepted goals become selectable entries in the note screen, so the Form 4119 note a DSP writes at 9pm references the actual outcome from the plan, in the plan’s words. Typing the goals in by hand still works.
The same read feeds the HCS planning packet. The PDP is card 2 on the individual’s Plan of care tab, and step 3 of the plan of care walk, Build the IPC and the IPs, uses the confirmed rows to build the Form 3608 IPC and a Form 2125 Implementation Plan per service, with the LAR and service coordinator carried over. Units never come from the PDP, and a person finishes every form.
Sereniq also checks that the PDP belongs to the right person. If the name on the uploaded PDP does not match the individual, Sereniq warns that it looks like it is for a different person and holds the build, new goals, and drafted objectives until someone confirms it is the right PDP or removes it.
The PDP also appears where auditors expect it: the Individual Binder packet pulls the current IRP or PDP alongside the MAR month, incidents, and latest notes, and the nursing binder tracks its upload and due date next to the CNA and delegation forms.
What you get
- PDP stored as a care-plan document with effective date and 365-day auto-expiry
- Read once: goals, services, LAR, and service coordinator drafted by AI, confirmed row by row by a person
- Confirmed goals selectable from the DSP note screen, with the goal text saved on each note
- Form 3608 IPC and Form 2125 Implementation Plans built from the confirmed rows in the plan of care walk
- Name check: a PDP whose name does not match the individual holds the build until someone checks it
- Expiry reminders at 30 days, 7 days, and on expiry, per individual
- Current PDP included in the one-click Individual Binder audit packet
What agencies ask before switching.
Does Sereniq generate or fill in Form 8665?
No. Form 8665 is completed by the planning team through the LIDDA service coordinator. Sereniq stores the finished PDP as a tracked document, reads it once into rows a person confirms, and uses those rows for note goals and the IPC and Implementation Plan drafts; it does not render the form.
How do PDP goals reach the DSP note?
Once goals are confirmed, from the AI read or typed in by hand, DSPs pick them from a list when writing a note, and the note stores the goal text as written at that moment. HCBS Supervised Living notes go one step further and require at least one linked IRP goal before submission.
When does Sereniq warn about an expiring PDP?
The expiry sweep notifies at 30 days before, 7 days before, and on expiry, using the effective date on the uploaded plan. IRPs use a 90-day window; PDPs use 365 days.
Where does the PDP show up during a survey?
In the Individual Binder packet, which assembles demographics, the current IRP or PDP, the MAR month, incidents, latest notes, and consents in one click, and in the nursing binder as a tracked document with its due date.
What if the wrong PDP was uploaded?
Sereniq compares the name on the PDP with the individual’s record. If they do not match, it shows that the PDP looks like it is for a different person, and nothing is built from it until someone presses It is the right PDP or an admin removes it.
Is the PDP signed in Sereniq?
No. The PDP is the LIDDA’s document, signed by the planning team, and Sereniq stores the finished copy. The IPC and Implementation Plans built from it, and the ID/RC, are signed in Sereniq.
Does the AI change anything on its own?
No. The read produces a list of pending rows. A program manager accepts, edits, or rejects each one, and only accepted rows become goals or feed the IPC and Implementation Plan drafts. Every AI action is recorded in the audit log.