Ansicht
Dokumentation

ISH_PRG_BADI_STAT - BAdI: Set Preregistration Status

Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Use

This Business Add-In (BAdI) is used in the Clinical Order component (IS-HMED-CO).

With this business add-in the system will either set specific clinical order data (e.g. waiting list data, order status) automatically when certain process steps are performed or prompt the user to do so.

Based on the clinical order (or the preregistration in IS-H) you can execute waiting list management. You can interpret the term "waiting list" as follows:

• A patient can be included in a waiting list as long as he has no appointment. Once an appointment has been allocated, the patient is removed from the waiting list.

• A patient can be included in a waiting list as long as he has not yet arrived for his visit or admission.

• A patient can be included in a waiting list as long as his surgery has not yet been carried out. The patient is removed from the waiting list following surgery.

The order status indicates the processing status of the clinical order (e.g. entered, added to waiting list, etc.). The user can always set the status manually in the Create/Change Clinical Order dialog box. With this BAdI the system can also automatically set the order status at specific events, or prompt the user to do so. This is particularly helpful if the user is currently processing a workstep for which he does need to use the clinical order dialog.

The system can automatically set the order status, or prompt the user to do so, at the following events:

• In the Create/Change Clinical Order dialog during the Check and Save events

• When planning the admission or surgery/treatment appointment for a clinical order

It is irrelevant whether the appointment is planned in the Create/change Clinical Order dialog or from an overview, e.g. a view of the Preregistrations view type. It is also irrelevant whether you plan a day-based appointment or a time-based appointment for a clinical order.

• When canceling an admission or surgery/treatment appointment for a clinical order

• When admitting a patient with the Clinical Process Builder (transaction NV2000)

• For users of IS-H Outpatient Clinic Management, when creating a visit for a preregistered surgery/treatment appointment

• For users of i.s.h.med when registering a patient in the outpatient clinic/service facility (outpatient visit is created for this treatment appointment), if you have preregistered the patient for a treatment appointment in an outpatient clinic or service facility

• For users of i.s.h.med, if you do not use the Register Patient function and perform or release the preregistered service which should be performed during the treatment appointment (visit is created)

• For users of i.s.h.med when executing the Start Surgery function if you have preregistered the patient for a surgery appointment

It is irrelevant whether the user manually triggers Start Surgery or it is automatically triggered when a time stamp is entered.

• When documenting a surgery using transaction NP37

• When entering a discharge

Requirements

You must have completed customzing of the clinical order.

Standard settings

The BAdI is not active as standard.

The BAdI can be used multiple times.

The BAdI is not filter-dependent.

Activities

If you wish to set the order status automatically, you must determine the events and conditions, at which the status should be set, in this BAdI. The triggered event and the overall instance of the clinical order and the clinical order item are available in the source code as a basis for your decisions.

• This BAdI is available for changing the following fields of the clinical order:

• Preregistration Status

• Waiting List

• Date of Inclusion in Waiting List

• Reason for Removal

• Date of Removal from Waiting List

• Further-Treating Hospital

• Customer-specific fields

You should note that you can also change other fields of the clinical order using this BAdI. These changes are, however, ignored by the caller of the BAdI. They are therefore not effective.

• The BAdI's changes to the clinical order are saved by the standard and not by the BAdI. The BAdI itself cannnot save changes in the database.

Example

With this BAdI you receive a sample implementation with the following features:

• When determining an admission or surgery/treatment appointment for a clinical order, the system should remove the clinical order from the waiting list.

• At events which plan the appointment of the clinical order, the user receives a dialog box for selecting the order status.

• The user can choose an order status, e.g. Planned, and thereby removes the clinical order from the waiting list.

To display the sample code, Select Goto --> Sample Coding --> Display.

Further Information

Method

EXIT_STATUS_SET

Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 6682 Date: 20240424 Time: 112609     sap01-206 ( 87 ms )