> 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-3/activities.md). # Activities - Mildly Ill 101630 (a) Notwithstanding Section 101230, the following shall apply: (b) The licensee shall develop, maintain and implement a written plan to ensure the provision of indoor and outdoor activities designed to meet the needs of mildly ill children. Such activities shall include but not be limited to: (1) Quiet and active play. (2) Rest and relaxation. (3) Eating. (4) Toileting. (5) Individual attention. (6) Infants being held by care providers. (c) The licensee shall ensure the participation of mildly ill children in the activities specified in Section 101630(b) as appropriate. (d) Each child, unless it is not appropriate because of the nature of his/her illness, shall be given the opportunity to nap/sleep whenever he/she wishes without being disturbed by other activities at the center. (1) No child shall be forced to sleep, to stay awake or to stay in the napping area. > NOTE: Authority cited: Section 1596.81, Health and Safety Code. Reference: Sections 1596.72, 1596.73 and 1596.81, 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-3/activities.md?ask=&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.