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_ENCODING | BAdI: Call Procedure Coding |
| Transaction Code | S_KK4_96000547 | IMG Activity: ISHMED_PROC_ENCODING |
| Created on | 20020308 | |
| Customizing Attributes | ISHMED_PROC_ENCODING | BAdI: Procedure Coding |
| Customizing Activity | ISHMED_PROC_ENCODING | BAdI: Procedure Coding |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_PROC_ENCODING |
Use
You can use the existing Business Add-In (BAdI) to implement a customer-specific connection to an external coding program for procedure coding.
You can find further information under:
The BAdI replaces the user exit used until now for procedure coding.
Import Interface
The import interface of the BAdI provides context data, used for further checks as well as application-specific data like, for example, the procedure catalog and search text for the procedure process with an external system.
Context data are entries in the current case, for example, patient name, birthdate and sex.
The import interface also controls whether the application will support single or multiple selection.
You can find a more detailed description of the import interface in the Data Dictionary under the structure RN2IPCOD.
Export Interface
You can find a more detailed description of the export interface in the Data Dictionary under the structure RN2EPCOD.
When you call the external coding system for single selection, the export structure E_RN2EPCOD must be filled in. For multiple selection the export structure, you must provide the T_RN2EPCOD with data.
Activities
Implement User Exit for Procedure Encoding
If you wish to use the user exit to code diagnoses, you must implement the BAdI. You should proceed as follows:
- When you execute this Implementation Guide activity, you create a BAdI implementation in the customer namespace. However, the implementation which you create will not yet contain a program code for the methods. Using Goto -> Example Coding you will branch to the program code of the delivered example method. Using the clipboard, you can transfer the program code to your own implementation. You then make the necessary adjustments. The interface of your implementation contains the ENCODE_PROCEDURES method. By double-clicking, you can access the program code of the delivered example method, where you can then transfer the example code.
When you have completed the customer-specific supplements, you must activate the implementation, so that the application can execute them. You should note that only one implementation can be active at any time.
If you already use customer exit NPRV0001, you can transfer the corresponding program enhancements, as they are implemented there, into the new environment.
Further notes
As not all applications have been converted to the new BAdI technology, you must leave both user exits in your system.
In the following applications the new user exit is used with the described functionality:
- Surgical Documentation IS-H*MED
Example
Requirements
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_ENCODING | 0 | I010004313 | OR Documentation |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020530 |
| SAP Release Created in | 463B |
