Designed specifically for PGME organizations, the Cross-Block Request Banning setting ensures that resident requests remain within the boundaries of a single academic period.
This feature prevents residents from submitting requests that span across different academic blocks, even if those blocks are not yet published. By enabling this, you can:
Maintain Consistency: Ensure all request periods are uniform.
Prevent Conflicts: Avoid scheduling complications at block boundaries.
Ensure Alignment: Keep all resident requests strictly within defined academic periods.
How to Activate
This setting must be enabled manually by an administrator. To activate it:
Navigate to Organization Settings.
Click on the Details tab.
Locate and check the box labeled "Prevent associates from creating cross-block schedules."
How It Works: Cross-Block Request Banning
When this setting is active, the system ensures all resident requests stay within the boundaries of a single academic block.
Automated Restrictions: The system automatically blocks any request that spans across more than one academic block.
Total Coverage: This rule is enforced regardless of whether the blocks have been officially published yet.
Real-Time Feedback: If a resident attempts to submit a request that crosses a block boundary, they will see a red warning message. This alert explains the issue and prompts them to split their submission into two separate requests (one for each block).
Who Is This For?
This setting is exclusively available for Postgraduate Medical Education (PGME) organizations.
It provides administrators with an additional layer of oversight regarding how and when availability requests are submitted. This is particularly beneficial for maintaining order within the structured scheduling environments common in academic medicine.