MedRez.net Announcement and Support Forum

An update to the MedRez.net Scheduling Tool with a focus on the Call and Shift Scheduling has been released.

See a Resident's Shifts and Calls from other schedules

When you select a resident icons appear in the calendar where that resident is assigned to Calls, Shifts or Clinics on a separate schedule or on the previous or next block. The calendar displays a few days prior to and after the block you are currently editing to help you make good block-to-block transitions.

Note that the Randomizer is also aware of these external commitments and treats them as conflicts to avoid. In addition, it will attempt to continue a resident's day-to-night progression from the previous block if the Progressive Schedules feature is enabled.

View Day-Off Requests directly in the Call/Shift schedule

Selecting a Resident displays that resident's requests as a timeline within the calendar.

Manage Requests from the Call/Shift Scheduling page

In addition to seeing the Requests on the calendar you can now manage all Requests relevant to the schedule you are editing. This means you can: accept pending requests, add/edit requests, grant/deny requests, and show/hide their status.

The data table includes a new column that shows requests granted and denied in that block. It will also display a warning if there is a conflict.

Edit Tally Targets quickly and efficiently

A completely new interface for editing Tally Targets lets you edit just one Tally Target or every staff's Targets with a minimal amount of fuss.

Other changes:

- Improved scrolling and space management for the data table in the Edit Call/Shift Schedule tab.

- Rewritten Call/Shift scheduling rules back-end significantly improves the response time for large schedules and paves the way for future improvements.

- Additional use of visual elements supported by FireFox, Chrome and Safari browsers, including drop shadows and rounded corners.

Note: This is a significant update and many parts of the code have changed. If you spot a bug please do report it in the comments below. Thank-you.