> For the complete documentation index, see [llms.txt](https://ismms-md-program.gitbook.io/medinfoapp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ismms-md-program.gitbook.io/medinfoapp/acting-internships/pediatrics/work-schedule-duty-hours.md).

# Work Schedule/Duty Hours

## <mark style="color:blue;">Clerkship Work Hour Characteristics</mark>

The schedule for the pediatric acting internship is based on a pediatric intern's schedule in order to prepare medical students for residency. Students will be capped at being the frontline for a maximum of 3 patients per day.&#x20;

<mark style="background-color:blue;">**Blue, Green, Yellow, and Red Teams**</mark>: Students will arrive at 6:30am for IPASS structured team sign out, followed by time to pre-round on their patients from 7:30-8:15am. Morning Report is held from 8:15-9:00am M, W, F. Chief Rounds are at the same time on Tuesdays. Grand Rounds are from 8:00am-9:00am on Thursdays. Patient and Family Centered rounds run from approximately 9:00am-12:00pm. Afternoons are dedicated to patient care, documentation, and on the fly teaching if possible. Evening IPASS structured sign out rounds are from 5:30-6:30pm. Students will do a week of nights (Sun-Thurs) arriving at 5:30pm and finishing after morning sign-out at 7:30am on the floors. The AI team endeavors to be flexible by allowing students to choose which week they would like to do nights. The Sunday evening shift does not fulfill the weekend call requirement.&#x20;

<mark style="background-color:blue;">**NICU**</mark>: Students will arrive at 7:00am. Students will complete 4 extended shifts where they will stay until 9pm and return the next day. Students should do one extended shift per week. We recommend pairing up with an intern/resident and completing your 4 calls with them.&#x20;

<mark style="background-color:blue;">**PICU**</mark>: Students will arrive at 7:00am. Students will complete 4 extended shifts where they will stay until 9pm and return the next day. Students should do one extended shift per week. We recommend pairing up with an intern/resident and completing your 4 calls with them.

***

<mark style="background-color:blue;">**Weekend Shifts**</mark>: All students, regardless of site, must complete one weekend day shift. Students may pick a date that works best for them.   &#x20;

***

## <mark style="color:blue;">Orientation Day Reporting</mark>

Students will observe rounds prior to orientation. Instructions regarding orientation will be sent in an email the week before (location and time may vary).

***

## <mark style="color:blue;">Work Hour Policy</mark>

Please view the ISMMS Clinical Student Work Hour Policy, which outlines the instructional time limitations for third- and fourth-year students, [here.](https://ismms-md-program.gitbook.io/medical-student-handbook/policies-and-procedures/md-program-specific-policies-and-procedures/student-work-hours)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ismms-md-program.gitbook.io/medinfoapp/acting-internships/pediatrics/work-schedule-duty-hours.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
