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 | SIMG_ISH_BADI_DCOD | BAdI: User Exit for Coding Diagnoses |
| Transaction Code | S_KK4_96000365 | IMG Activity: SIMG_ISH_BADI_DCOD |
| Created on | 20000810 | |
| Customizing Attributes | SIMG_ISH_BADI_DCOD | BAdI: User Exit for Coding Diagnoses |
| Customizing Activity | ISH_PF4_DIAGNOSEN | Define Input Help for Entering Diagnoses |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISH_BADI_DCOD |
This Business Add In (BAdI) lets you implement a customer-specific connection to an external program for diagnosis coding.
For further information, refer to the following documentation:
The BAdI replaces the existing User Exit DCOD for diagnosis coding.
Import Interface
Besides application-specific data such as the diagnosis coding catalog and the diagnosis text, context data for further checks is also made available via the BAdI's import interface.
Context data comprises specifications relating to the current case, such as patient name, birthdate and sex.
The import interface also determines whether simple selection or multiple selection from the application is accommodated.
For a detailed description of the import interface, refer to the structure RN2IDCOD in the Data Dictionary.
Export Interface
The export interface has been enhanced for the respective application program such that it is now possible to pass a maximum of two diagnosis values and, depending on the user-specific settings, the catalog text as SAPscript text for the user-defined text diagnosis.
For a detailed description of the export interface, refer to the structure RN2EDCOD in the Data Dictionary.
When the external coding system is called for simple selection, the export structure E_RN2EDCOD must be filled. In the case of multiple selection, the export structure of table T_RN2EDCOD must be supplied with data.
Example
Implementation Example:
Method: if_ex_ish_diagnosis_dcod~rndia_dcod
This method contains example source code for calling an external coding program and for supplying data to the export interfaces in relation to the selection type supported in each case.
Requirements
To be able to implement the User Exit for diagnosis coding in the applications, you must have made the appropriate entry in the activity Define Input Help for Coding Diagnoses .
Standard settings
Recommendation
Activities
Implement User Exit for Coding Diagnoses
To be able to avail of the user exit for coding diagnoses, customers have to implement the BAdI. To do this, proceed as follows:
- When you perform this Customizing activity you create an implementation of the BAdI in the customer namespace. The implementation you have created does not yet have any program code for the method. You access the program code of the example method contained in the standard system by choosing Goto -> Example code. You can copy the program code via the clipboard into your own implementation, and then custom tailor this copy to satisfy your own particular requirements. The interface of your implementation contains the method RNDIA_DCOD. Double-clicking takes you into the code for the method where you can perform the copy of the sample code.
Once you have completed the customer-specific modifications you still have to activate the implementation so that these modifications can also be executed by the application programs. Note that only one implementation at the most can be active.
If you have already implemented user exit DCOD, you can transfer the relevant program modifications as implemented in this exit into the new environment.
Further notes
Since not all applications accommodate the new BAdI technology, both user exits must exist in parallel in your system.
The new user exit with the described functionality is used in the following applications:
- Diagnosis documentation IS-H/ IS-H*MED
- External data module diagnoses IS-H*MED
- OR documentation IS-H*MED
Long text processing
The user parameter DKD lets you stipulate whether the catalog text should be transferred as a SAPscript text after coding when an external coding procedure is used.
The user parameter DKD has the following meanings:
- 1st position X: catalog text transfer for internally-used catalogs; this functionality only applies for IS-H*MED
- 2nd position X: catalog text transfer for external coding procedures.
In cases where you wish the catalog text to be transferred, processing takes the following form:
- Diagnosis catalog text transferred into the user-defined text diagnosis field
- Longer diagnosis catalog texts are saved as SAPscript text
- Existing SAPscript text completely overwritten by long catalog text
- Existing SAPscript text deleted by short catalog text
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired 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_ISH_BADI_DCOD | 0 | I010004218 | Basic Medical/Nursing Documentation |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20010508 |
| SAP Release Created in | 462 |
