Day-Related Planning Authority
Every surgery, examination and treatment appointment requires a Planning Object, that represents the resource (e.g. operating room, treatment room, organizational unit), which is occupied due to a planned appointment. The day-related planning authority determines for specific days, within which time periods a planning organizational unit (OU) can plan appointments for a resource.
Caution
The day-related planning authority overrides the planning authority for the day program for individual days.
You can use a wildcard entry (*) to grant all organizational units (OUs) planning authority for a specific planning object for a specific time period of a day program, with one single entry.
Note that excessive use of the wildcard entry can adversely affect the performance when the planning grid is called. This is particularly relevant if you have not defined display variants for the planning grid. In such a case, the system calls the planning grid with the standard variant which contains all the planning objects in which the planning OU has planning authority.
Each surgery/treatment appointment requires a planning object with free time slots where it can plan appointments. The day program planning authority determines on which days and within which time periods a planning organizational unit (OU) can plan appointments.
The day program planning authority can be replaced by the day-related planning authority
for individual days.
You use the day-related planning authority in the Surgeries
or Appointment Planning
view type in the clinical work station or in the planning grid. See Changing Planning Authority
Note
You can restrict the access to the planning authority, by only using the Change Planning Authority
function in the function variants of those views of the Surgeries
view type, which you make available to the appointment coordinators. There is no authorization object for the day-based planning authority.
For customer-specific checks the system administrator can integrate a Business Add-In (BAdI). You can find this BAdI in the Implementation Guide
under .