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_DIA_ENCD | BAdI: Call Combined Diagnosis-Procedure Coding |
| Transaction Code | S_KK4_96000559 | IMG Activity: ISHMED_PROC_DIA_ENCD |
| Created on | 20020415 | |
| Customizing Attributes | ISHMED_PROC_DIA_ENCD | BAdI: Call Combined Diagnosis-Procedure Coding |
| Customizing Activity | ISHMED_PROC_DIA_ENCD | BAdI: Call Combined Diagnosis-Procedure Coding |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_PROC_DIA_ENCD |
Use
You can use this Business Add-In (BAdI) to implement a customer-specific connection to combined external coding of diagnoses and procedures.
You can find further information under:
Import Interface
All required data is transferred from the SAP application to the coding system via the BAdI's import interface.
This includes application-specific data (e.g. catalogs and search strings) as well as case-related context data for further checks.
Context data is data from the current case, for example, patient name, birthdate and sex.
When using the combined diagnosis and procedure coding, import data also includes all diagnoses and procedures, which belong to the current case. These enable the system to propose possible diagnosis/procedure combinations when coding.
The import interface also controls whether the combined coding of diagnoses and procedures is called from the diagnosis or procedure view.
You can find a precise description of the import interface in the Data Dictionary for the structures RN2IDCOD (diagnosis data) and RN2IPCOD (procedure data) and the method documentation.
Export Interface
All diagnoses and procedures transferred from the coding system are returned to the SAP application via the export interface.
You can find a precise description of the export interface in the Data Dictionary for the structures RN2EDCOD (diagnosis data) and RN2EPCOD (procedure data) and the method documentation.
Requirements
Standard settings
Activities
Implementing the User Exit Combined Coding
To use the user exit for diagnosis coding, the customer must implement the BAdI. You should proceed as follows:
- By executing this activity in the implementation guide, you implement the BAdI in the customer namespace. The implementation created by you will not contain program code for the methods. You can access the program code of the delivered example methods via the menu option Goto -> Example Coding. You can copy the program code into your own implementation via the clipboard. You then make any adjustments necessary to your requirements. The method ENCODE_DIAG_PROCEDURES is contained in the interface of your implementation. By double-clicking you can access the code of the method where you copy the example coding.
Once you have executed the customer-specific enhancements, you must then activate the implementation so that the application programs can also execute them. You should note that only one implementation can be active at any time.
Example
Example of an implementation:
Method: if_ex_ishmed_proc_dia_encd~encode_diag_procedures
This method contains an example code for calling an external system for combined diagnosis and procedure coding which takes customer-specific customizing entries into account.
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_DIA_ENCD | 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 |
