Configure Planning Grid
If you wish to plan (preregistered) clinical order items and appointments in the planning grid using time-based planning, you must make the settings for the planning grid.
Caution
When configuring the planning grid, you should note that the planning grid displays a maximum of 50 tab pages (for planning objects or days).
You define Planning Objects for the Planning Grid.
You install the Planning Grid Work Station Component.
You define the Organizational Unit-Related Planning Grid Parameters.
You create the Planning Grid User Parameters.
You can define Customer-Specific Enhancements for the Planning Grid.
You can Create/Change Display Variants in the Planning Grid.
You determine the User Authorizations for the Planning Grid.
You define inpatient scheduling types in the Implementation Guide
under . You use this parameter to create appointments outside of the day program, but within the planning authority. See Organizational Unit-Related Parameters for Planning Grid
You define outpatient scheduling types in the Implementation Guide
under.
Note
In the Number of Patients column you determine how many patients (appointments) the user may plan in a time period of this scheduling type, before the system checks the authorization for overbooking.
You can define planning object classes in the Implementation Guide
under .
You can replace the GUI status of the planning grid with an alternative GUI status. This alternative GUI status can provide the user with additional functions (function exit EXIT_SAPLN1PLANT_USF
), which are not available in the standard planning grid function range.
You can replace the GUI status of the planning grid with an alternative GUI status. You can use an alternative GUI status to determine which functions (e.g. Create Clinical Order, Team Entry, etc.) are available to the user in the planning grid. Furthermore you can provide the user with additional functions which are not contained in the planning grid with the standard GUI status.
You define an alternative GUI status in the implementation guide
under .