Ansicht
Dokumentation

Customizing Requests (Enhanced) ( RELNISHMED_463B_BASIS_30 )

Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Short text

Customizing Requests (Enhanced)

Use

In the current release we have made the following improvements to the management of requests, as described in this chapter of the release notes:

• Inclusion of the patient's department when selecting requests

• Revision of the request definition function

• Integration of the definition function in the Transport Organizer

• Integration of the request definition function in the IMG

Inclusion of the Patient's Department when Selecting Requests

In IS-H*MED Release 4.63B you can define hit lists for selecting requests for departments. This selection should be the default if there is no request definition based on the requesting nursing organizational unit.

Revision of the Request Definition Function

The previous functions used to define request types, requestable organizational unit and request type use assignments have been replaced by a new request type definition. You can find this function in the IMG under Clinical System -> Service Management -> Requests.

You should note that the request type is always defined from the organizational unit which will perform the request.

Integration of the Definition Function in the Transport Organizer

You can transfer all request type attributes, for example, the indicator, the availability and the tab pages, into a transport request using the function Request Type -> Transport. You should also read the release information in the "Transport Support for Customizing and Master Data".

Integration of the Request Definition Function in the IMG

Until now the request definition function was located in the IS-H*MED basic data menu. From Release 4.63B this function is located in the IMG under Clinical System -> Service Management -> Requests.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

You can activate the new assignment of requests based on the patient's department from a certain key date.

Effects on Customizing

Inclusion of the Patient's Department when Selecting Requests

Delta customizing is necessary if you wish to use this functionality. If you do not make any changes in customizing the request will function in the same way as in Release 4.63.

In the logic of the "Create Request" function, which you can call from various work environments, an organizational unit is always the requesting OU. The system will apply the customizing settings from this OU. The system will decide which OU is the requesting OU (either the requesting nursing OU or the requesting departmental OU), using the following algorithm:

1. Does at least one assigned request type exist for the requesting nursing OU of a request? If so, the system will only use request types of the requesting nursing OU.
2. If not, the system will search for all request types which come from the requesting departmental OU. If the system finds at least one request type, then it will use this.
3. If you have also not defined a request type based on the requesting departmental OU, then you cannot create any requests.

This logic will always result in a requesting OU.

You should start customizing in an inter-departmental care unit. You should change the validity periods of the request types so that there is no single request possibility for this care unit from a specified time.

You then maintain new entries, with departments, in this tab page. The OU-specific parameters concerned with changes should also be maintained for this department. The request based on the patient's department will then be available to you from the key date onwards.

Further Information

rdisp/max_wprun_time - Maximum work process run time   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4379 Date: 20240602 Time: 172023     sap01-206 ( 76 ms )