SAP ABAP IMG Activity ISHMED_CDOKU_CALL (BAdI: Call Surgical Documentation)

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_CDOKU_CALL	BAdI: Call Surgical Documentation
Transaction Code	S_KK4_96000558	IMG Activity: ISHMED_CDOKU_CALL
Created on	20020412
Customizing Attributes	ISHMED_CDOKU_CALL	BAdI: Call Surgical Documentation
Customizing Activity	ISHMED_CDOKU_CALL	BAdI: Call Surgical Documentation

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	ISHMED_CDOKU_CALL

Use

You can use this Business Add-In (BAdI) to implement a customer-specific connection for transferring diagnoses and procedure data when the surgical documentation is called.

You can also deactivate certain functions in the surgical documentation and suppress the surgical documentation call.

You can see which functions are used in the surgical documentation and which functions you have deactivated in the function group 'N2OP' in GUI status 'CDOK'. You cannot deactivate functions which are required for the normal use of the surgical documentation. (e.g. save, release, etc.).

Diagnoses and procedures transferred using the BAdI (diagnoses, procedures and team) are only transferred to the surgical documentation if the surgical documentation is in change mode.

You can find further information under

• Interface Documentation
• Method Documentation

Import Interface

The import interface of the BAPI provides you with additional application-specific data such as the surgery anchor service, case data, and surgery movement data, to supplement the surgery-specific data: surgery anchor service, case data (NFAL) and surgery movement data (NBEW).

You can find a detailed description of the import interfaces to NBEW and NFAL in the data dictionary.

Using the surgery anchor service, you can determine surgery-specific data, for example, diagnoses, procedures, surgery team members or complications.

Export Interface

Using the export tables T_DIA_TAB and T_ICPM_TAB of the BAdI, you can enhance the surgery data beyond the standard process of the surgical documentation by adding additional diagnosis and procedure data.
The export table T_TEAM_TAB is not supported. Team data cannot therefore be enhanced.

In the export table T_EXCL_FUNCTION you add the functions to be hidden. These then no longer appear as pushbuttons.

You can prevent the surgical documentation from being called by setting the export parameter E_CODE_CHIRDOKU to A. However, you cannot reset an executed 'Surgery Start'.

Requirements

Standard settings

Activities

Implement User Exit for Calling the Surgical Documentation

In order to be able to use the user exit to call the surgical documentation, you must implement and activate the BAdI. You should proceed as follows:

• By executing this implementation guide activity, you create an implementation of the BAdI in the customer namespace. However, the implementation you create does not yet contain program code for the method. You can access the program code of the example method delivered via Goto -> Example Code, providing an example implementation was delivered. You can then transfer the program code to your own implementation via the clipboard. You then make your adjustments. The CHIRDOKU_CALL 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 sample code, or your own implementations.

You must then activate your implementation. Only one implementation can be active at any one time.

Further notes

You should note that you supplement surgery data using this BAdI at your own risk. This is not normally necessary, as all data which is required for the OR documentation, and therefore also for the surgical documentation, exists in the SAP system, or is manually entered.

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_CDOKU_CALL	0	I010004313	OR Documentation

Maintenance Objects

Maintenance object type

E

Business Add-In - Definition

History

Last changed by/on	SAP	20020416
SAP Release Created in	463B