> For the complete documentation index, see [llms.txt](https://t22.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t22.caqualityearlylearning.org/continuing-requirements/postural-supports-protective-devices.md).

# Postural Supports/Protective Devices

101223.1

(a) Postural supports may be used with prior approval by the Department as specified in (1) through (5) below. 

   (1) Supportive restraints shall be limited to appliances or devices, including straps, spring-release trays or soft ties, that are used to support a child in a bed, chair or wheelchair to prevent falling. 

   (2) All requests to use supportive restraints shall be in writing and shall include a written order from a physician indicating the need for such restraints. The Department is authorized to require additional documentation in order to evaluate the request. 

   (3) Approved supportive restraints shall be fastened or tied in a manner that permits quick release. 

   (4) The Department shall approve the use of supportive restraints only after the appropriate fire clearance, as required by Section 101171, has been secured. 

   (5) The Department has the authority to grant conditional and/or limited approvals to use supportive restraints.

> NOTE: Authority cited: Section 1596.81, Health and Safety Code. Reference: Sections 1596.72, 1596.73, 1596.81 and 1597.05, Health and Safety Code.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://t22.caqualityearlylearning.org/continuing-requirements/postural-supports-protective-devices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.