System Generated Log Notes

The USTEPS system automatically records a log note when important operations are completed, such as recording an eligibility decision, activating a Person Centered Support Plan, etc.

USTEPS System generated log notes are intended to ease the support coordinator’s workload by automatically logging important events as they happen.

Because of the formal nature these notes have, the worker cannot change its original text, date, etc. The worker can, however, amend a system generated note to further elaborate on the conditions or circumstances that caused it to be created.

System generated notes are identified as such in the Contact Type column.

Table of USTEPS System Generated Logs:

System Events & Conditions that Spawn System Generated Logs
System Event/Condition	System Area/Screen	Screen Button/Condition that Triggers the Log	Log Text
Worker Creates the Applicant	faces/JSP/contact/ContactDecision.jsp	Clicking on "Save and Print Form" button triggers the log's creation	A contact was made with DSPD for [Consumer Name] that resulted in generating a Request for Determination of Eligibility for Services Form 1-1 on [Date]. [Consumer Name] entered Contact Status on [Date].
Worker Creates the Consumer	faces/JSP/contact/ ContactDecision.jsp	Clicking on the "Create Consumer" button triggers the log's creation	The Request for Determination of Eligibility for Services Form 1-1 for [Consumer Name] was returned to DSPD on [Date]. [Consumer Name] started the 90-Day Intake data collection period on [Date]. [Worker Name] was assigned as the Intake worker for [Consumer Name].
Intake Data Collection is not complete @ the End of the 90-Day Period	No screen - Managed by the night process	Day 90 has passed by	The 90-Day Intake data collection period expired before the minimum data required to make an eligibility decision for [Consumer Name] could be gathered. The missing items are [list the missing stuff]. As a result, [Consumer Name] was placed on inactive status on [Date].
The system changes the consumer's status from Intake to Eligibility Decision because all of the data required to make a decision are present and the 90-Day intake period has expired			[Worker Name] received the missing information required to make an eligibility decision for [Consumer Name]. As a result, [Consumer Name] has been reactivated on [Date] and the 90-Day intake data collection period has been restarted.
Worker makes an "Eligible" Decision	faces/JSP/eligibility/ Decision.jsp	Clicking on the "Eligible" button triggers the log's creation	[Name of QMRP] determined that [Consumer Name] is eligible to receive services from DSPD on [Date].
Worker makes an "Ineligible" Decision	faces/JSP/eligibility/ Decision.jsp	Clicking on the "Ineligible" button triggers the log's creation	[Name of QMRP] determined that [Consumer Name] is not eligible to receive services from DSPD on [Date].
Supervisor sends the case on the Region Eligibility Committee Rep	faces/JSP/eligibility/ Recommendation.jsp	Clicking on the "Send Up The Line" button triggers the log's creation	[Consumer Name] entered the 90-Day Eligibility Determination period on [Date] because their case was sent to [Field Representative Name] on [Date] for a preliminary review prior to being examined by the Eligibility Committee.
The system changes the consumer's status from Intake to Eligibility Decision because the supervisor sent the case to the Field Eligibility Committee Rep.	faces/JSP/eligibility/ Recommendation.jsp	Clicking on the "Send Up The Line" button triggers the log's creation	[Consumer Name] entered the 90-Day Eligibility Determination period on [Date] because their case was sent to [Field Representative Name] on [Date] for a preliminary review prior to being examined by the Eligibility Committee.
Field Rep. puts the case on the Eligibility Committee's agenda.	faces/JSP/eligibility/ Recommendation.jsp	Clicking on the "Send Up The Line" button triggers the log's creation	[Field Representative Name] added the eligibility case for [Consumer Name] to the Eligibility Committee’s agenda on [Date].
Field Rep. sends the case back to the worker	faces/JSP/eligibility/ Recommendation.jsp	Clicking on the "Send Back" button triggers the log's creation	[Field Representative Name] returned the eligibility case for [Consumer Name] to [Case Worker Name] along with a recommendation regarding how to address the issue(s) in question.
Worker sends out the NOA			A Notice of Agency Action was sent to [Consumer Name] regarding [purpose of the NOA] on [Date].
Consumer appeals a decision (e.g. a "Not Eligible" decision) within the first 10 days of the 30 day appeal period		Clicking on the button that records the appeal triggers the creation of this log	[Consumer Name] submitted notification to DSPD on [Date] that they desire to appeal the decision in question.
Consumer appeals a (e.g. a "Not Eligible" decision) decision in the 11 to 30 day window of the 30 day appeal period		Clicking on the button that records the appeal triggers the creation of this log	[Consumer Name] submitted notification to DSPD on [Date] that they desire to appeal the decision in question.
Consumer is put on the waiting list	faces/JSP/eligibility/Decision.jsp	"Eligibility" button	[Consumer Name] was placed on the waiting list on [Date].
The consumer has chosen to be taken off the waiting list			[Consumer Name] notified DSPD that they no longer want to be on the waiting list. As a result, [Consumer Name] was taken off the waiting list and their status was changed to Inactive on [Date].
The consumer has been transferred to another caseworker	faces/JSP/consumer/ConsumerTransfer.jsp	Clicking on consumer's name in the datatable on the screen triggers the creation of this log.	[Consumer Name] was transferred to [Case Worker's Name] case load on [Date].