X

Attach Documents to the Request

After the worker has selected the service code(s), they should load the documentation that will be used to explain why the person satisfies the conditions of the code's criteria.  The document's selection should not be based on a capricious or arbitrary argument.  Rather, the document should be the best source of information about the person's need and give clear evidence about why the person satisfies the specific criterion associated with it.  In order for it to be suitable, the document should be current and otherwise pertinent to the person's life.  Regardless of which document is chosen, the worker should make every effort to clearly note and reference the portion of it that substantiates the justification made for the criterion.  The worker should avoid loading documents in the RFS that are unrelated, overly generalized, vague or otherwise disassociated with the person's new need.  

View a demonstration about how to load documents in the RFS.

The document can be any one of the following:

Pre-loaded Documents (these documents are automatically loaded into the request when it is created).

1. The person's Social History (it pulls a variety of social history data from USTEPS into a single document that can be used in the request).

2. The person's Person Centered Profile (it pulls the data from the person's profile and makes it available for use in the request)/

3. The person's most recent SIS (it pulls the SIS report from the most recently completed SIS).

Manually Loaded Documents (these documents have to be manually selected and loaded into the request by the worker)

1. Log Note (the worker selects the specific log note they want to use in the request).

2. Incident Report (the worker selects the specific incident report they want to use in the request).

3. Electronic Document (the worker selects the specific document they want to use in the request).