Change in a risk management SC/PA or Provider Approval strategy that is described in the org./Foster prov. ISP Risk Management Plan Revision to provider support SC/PA or Provider Approval Examples include attempting to implement documents that changes the org./Foster prov. restrictions or limitations on the person’s scope of the supports provided rights or discontinuing supports that are written into the person’s ISP. Revision to provider support Provider Notification Examples include reasonable adjustments to document that does not change org./Foster prov. only support documents that the person’s the of the supports provided preferences and remain consistent with supports that are written into the person’s ISP. *Send copy of changed document including Change Form to SC/PA Revision to provider’s SC/PA or Provider Notification *Send copy of changed document including implementation strategies, such org./Foster prov. only Change Form to SC/PA as Action Plans Revision to One Page Profile or Local changes may be made by any ISP team member following local Person Centered Information documentation practices. No formal approval or notification is required. When approval of a change is required it must be sought and obtained from (or attempted to be obtained from): the person, the person’s legal or designated representative, if any, and Services Coordinator/Personal Approval may be given verbally or in writing. The signature, email, or verbal acknowledgement is expected from any service provider impacted by a change. If approval is not required for a specific change, notification of the change must still occur. Examples of notification options include telephone call, email, or fax. Record how the approval or notification was obtained in the provided on the ISP Change form.
Change in a risk management strategy that is described in the ISP Risk Management Plan SC/PA or Provider org./Foster prov. Approval Revision to provider support documents that changes the scope of the supports provided SC/PA or Provider org./Foster prov. Approval Examples include attempting to implement restrictions or limitations on the person’s rights or discontinuing supports that are written into the person’s ISP. Revision to provider support document that does not change the of the supports provided Provider org./Foster prov. Notification only Examples include reasonable adjustments to support documents that the person’s preferences and remain consistent with supports that are written into the person’s ISP. *Send copy of changed document including Change Form to SC/PA Revision to provider’s implementation strategies, such as Action Plans SC/PA or Provider org./Foster prov. Notification only *Send copy of changed document including Change Form to SC/PA Revision to One Page Profile or Person Centered Information Local changes may be made by any ISP team member following local documentation practices. No formal approval or notification is required. When approval of a change is required it must be sought and obtained from (or attempted to be obtained from): the person, the person’s legal or designated representative, if any, and Services Coordinator/Personal Approval may be given verbally or in writing. The signature, email, or verbal acknowledgement is expected from any service provider impacted by a change. If approval is not required for a specific change, notification of the change must still occur. Examples of notification options include telephone call, email, or fax. Record how the approval or notification was obtained in the provided on the ISP Change form.
Oregon-ISP-Instructions-02-28-2018.docx