Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NORD (Package) R/3MED: Services processing EDV-G
IMG Activity
| ID | SIMG_ISHMED_USEREXIT | Display Available User Exits and BAdIs |
| Transaction Code | S_KK4_74000621 | IMG Activity: SIMG_ISHMED_USEREXIT |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_ISHMED_USEREXIT | Display Available User Exits |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_USEREXIT |
User Exits and BAdIs in i.s.h.med
You can find the vast majority user exits and Business Add-Ins (BAdIs) in the implementation guide assigned to the corresponding chapters. This document contains only the user exits and BAdIs which are not assigned to the chapters of the implementation guide.
- User exits, for which the name of an enhancement is entered must be processed using project management (transaction CMOD).
- User exits, for which an event is entered, must be implemented as function module with a default interface and the module name must be entered in the table IS-H: Customer User Exits. You can find this table in the SAP menu under -> Hospital -> Basic Data Administration -> Environment -> Configuration -> Technical Settings -> User Exits -> Customer.
You must process business add-ins using the implementation maintenance function (transaction SE19).
Outpatient Clinic Management
- Accident Entry (Event: UNFA)
You can use this user exit to toggle between IS-H accident entry and i.s.h.med accident entry in the transactions Create Outpatient Admission and Change Outpatient Admission (menu: Outpatient Admission -> Goto -> Accident Data). The Clinical Process Builder (transaction NV2000) does not support this exit).
Service Request
- Create Request (Enhancement Component SAPMN1PA)
You can use this user exit to preset the request and the surgery request. The structures NLEI, NLEM and N1ANF can be transferred in their complete form.
With a collective request, you can only preset fields which can be seen on the screen (for example, no services).
- Check Request (Enhancement Component SAPLN1LA)
The plausibility of a request can be checked in this user exit. When called, the following information is transferred that can be treated differently in the user exit: whether this concerns a surgery request or a normal request, whether the request is being created, displayed, or changed, whether the request will be checked, saved, or confirmed, (default: checked). The user exit sets the indicator which states whether an error occurred.
- Requests Confirmed (Enhancement Component SAPLN1AC)
This user exit is called after a request is confirmed. The module is supplied with the current requests with the corresponding services. This user exit can, for example, forward request data to a subsystem.
Set Requests to "In Processing" (Enhancement Component SAPLN1AB)
This user exit is processed after a request/group of requests has been set to "In Processing". It can be used to inform subsystems of the status change of the request. The module is supplied with the changed requests in a table for further processing.
- Request Printout - Sorting the List (Enhancement Component SAPLN1AD)
You can use this user exit to determine the sequence in which the system should print the requests. The module is supplied with the tables formatted for the printout; these can be customer-specifically re-sorted and returned to the caller.
- Selection Hit List for Services ( Business Add-In (BAdI) N1_HLST_NEW_FIELDS ) Method EXIT_NEW_FIELDS
You can use this BAdI to define new columns in the service hit list. These can be used to display additional information concerning a request type or preregistration type (services at request or order type level, additional comments, etc.).
Treatment Register
- Treatment Register (Enhancement Component RN1BBUCH)
In the above-mentioned report a string is available for each entry, which can be filled using this user exit. For example, the contents of clinical documents can be integrated into the treatment register.
Document Processing
- Document List (Enhancement Components N2DOKL01, N2DOKL02, N2DOKL03)
With the enhancements, you can activate three additional processing functions (in the GUI status DOKLIST1) in the document list. The functions are available as pushbuttons and are accessed via the Extras menu. When one of the three functions is executed, a table of the selected documents will be transferred to the appropriate user exit.
Clinical Work Station
- Clinical Work Station: Diagnoses - Checks (Event: N1MS)
You can use this user exit to determine whether, in the Occupancy, Arrivals, Departure view types, the system should display a comment text in the Diagnosis column when a diagnosis with a specific indicator is missing (for example Admission diagnosis missing). The algorithm which determines that a diagnosis is missing must be implemented in the exit.
The standard provides the function module ISHMED_DIAG_BEW_CHECK, which determines missing hospital principal diagnoses, department principal diagnoses, etc. for the movement in the current view.
Patient Transport Service
- Patient Transport Service - Calculation of Duration of a Transport Order (Business Add-In N1_FA_CALCULATE)
Method EXIT_FA_CALCULATE: This method is used to implement an algorithm which calculates the duration of a transport order. It is called from the function module ISHMED_PTS_DURATION_CALCULATE, if the status required for the calculation of the duration of a transport order does not exist.
Cumulative Findings
- Access to Cumulative Findings (Enhancement Component N2CUM01)
Creation of customer-specific cumulative finding for laboratory values. This is called as an alternative to standard processing.
- Cumulative Findings (Enhancement Component SAPLN212)
Creation of a customer-specific report for displaying cumulative findings.
Laboratory Data
- Laboratory Data (Enhancement Component SAPLN2LA)
Post-processing of laboratory data entered or maintained in documents of type N2_LABOR or N2_LABOR1.
- Laboratory Data Transfer (Enhancement Component SAPLN2L1)
Modification of laboratory data which was transferred via the communication interface, before it is saved as laboratory data in documents of type N2_LABOR or N2_LABOR1.
- Laboratory Data Transfer (Enhancement Component SAPLN2L2)
It is possible to process customer-specifically enhanced messages in HL7 format when transferring laboratory data. You can also modify laboratory data following standard processing, before it is transferred as a finding by batch input.
- Laboratory Document (Enhancement Component N2LABPRI)
The enhancement component contains two user exits for implementing the separate print control and print formatting of a laboratory document.
Service Management
- Employee - Service Assignment (Team Conversion) (Enhancement Component SAPLN1TU)
This user exit is called after the standard service conversion with the data of this conversion. You can fine tune the service allocation. The user exit returns the new service allocation to a separate table.
Due to the example source code implemented, a new data record is created for the fee-based physician role for every converted service.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ISHMED_USEREXIT | 0 | I010004300 | Clinical System |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20030220 |
| SAP Release Created in |
