Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NMED (Package) R/3MED: Medical documentation GSD
IMG Activity
| ID | ISHMED_PROC_ENC_HITL | BAdI: Call Personal Hit List for Procedure Coding |
| Transaction Code | S_KK4_96000674 | (empty) |
| Created on | 20021109 | |
| Customizing Attributes | ISHMED_PROC_ENC_HITL | BAdI: Personal Hit List for Procedure Coding |
| Customizing Activity | ISHMED_PROC_ENC_HITL | BAdI: Personal Hit List for Procedure Coding |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_PROC_ENC_HITL |
Use
You can use the Business Add-In (BAdI) to implement a customer-specific connection to a procedure coding tool using a personal hit list.
You can find further information under:
Import Interface
Via the import interface, the system is supplied with context data for further checks as well as application-specific data, for example the procedure catalog and search string, for calling the hit list management program.
Context data includes entries for the current case, for example, the patient name, date of birth, and sex.
This import interface also controls whether single selection or multiple selection is supported by the application.
You can find a detailed description of the import interface in the Data Dictionary under the structure RN2IPCOD.
Export Interface
You can find a detailed description of the export interface in the Data Dictionary under the structure RN2EPCOD.
When the procedure coding tool is called for single selection, the export structure E_RN2EPCOD must be filled. For multiple selection the export structure of the table T_RN2EPCOD must be supplied with data.
Requirements
Standard settings
Activities
Implement User Exit for Calling Hit List Coding
In order to use the user exit for coding diagnoses, customers must implement the BAdI. You should proceed as follows:
- You create an implementation of the BAdI in the customer namespace by performing this implementation guide activity. However, your implementation does not yet contain program code for the method. You can access the program code of the delivered example methods via Goto -> Example Code. You can transfer the program code to your own implementation via the clipboard. You then make any adjustments to suit your requirements. The ENCODE_PROCEDURES_HITL method is contained in the interface of your implementation. By double-clicking you can access the code of the method, where you can then transfer the example code.
Once you have executed the customer-specific enhancements, you must activate your implementation, so that it can be executed by the application programs. You should note that only one implementation may be active at any time.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| 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 | ISHMED_PROC_ENC_HITL | 0 | I010004313 | OR Documentation |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20021109 |
| SAP Release Created in | 471 |
