Ansicht
Dokumentation

ISH_HCM_NPMI_DO_CUST - SG: NPMI Customizing

PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Procedure for Implementing NPMI Data Exchange (Singapore)

1. Create the data collection points: Master data maintenance

Before a message can be sent, you have to specify the recipient. You do this by choosing Maintain Master Data of Data Collection Points.

1. Maintain the transfer system connection

To be able to transmit the data synchronously to the transferring system you have to specify the RFC destination and function module which receives the data. You maintain these settings by choosing Connect Transfer System.

For more information on RFC destinations and RFC stubs, please refer to the SAP Basis documentation and the sections on Express Dispatch in the IS-H Implementation Guide. Also refer to documentation on the Customizing step Maintain RFC Destination.

1. Activate data collection

NPMI data transfer has to activated explicitly in the system. You activate this option in the Customizing activity Activate Communication Procedure. In the corresponding Customizing table you can specify for which communication procedure you want to carry out data exchange.

You should activate data collection only if data exchange takes place electronically. On no account activate this file creation if you are still exchanging data using forms (or any other means).

1. Maintain case exclusions

In production operation, it may be agreed with the recipient concerned that data relating to complicated cases should be communicated in paper form only. To prevent messages from being created and processed in such situations, you have to add the corresponding cases to the EDI case exclusion table. You can also create a short explanatory text for these entries.

You can exclude cases from EDI processing by choosing Hospital -> -> Communication -> EDI -> Exclude -> Case.

1. Most important steps for implementing NPMI data exchange
1. Maintain the recipient data and corresponding agreements. When maintaining the agreements ensure you maintain the standard, version and first character of the special characters. This is used as the separator for segments and fields. The usual value is "*".
2. For the transfer system maintain the RFC destination and the name of the RFC module. Data is transmitted synchronously by calling the program specified here. The called program receives the data and routes it to the actual recipient. This program is the responsibility of the respective hospital and is not part of the SAP standard shipment. You need to agree on the interface with the vendor of the receiving program.
   
   If you are not familiar with how to connect external programs, with RFC modules and with generating RFC stubs, please refer to the corresponding chapters of the SAP Basis documentation.
3. Maintain the physician numbers in the physician table (NPER-ARZTN).
4. Maintain the Customizing settings for risk factors and drug allergies (table TNRSF).
5. Maintain the hospital code in the TNC301XI table.
6. Maintain the assignment of internal codes to external CCPS codes in the TNCMAPP table. The following field is concerned:

• Change reason (TNC301XI-EREASON).

1. Activate the communication procedure.
2. When a patient is admitted a request for risk factors is sent
   When all risk factors have been entered, a list of all medical alerts and changed risk factors is transmitted using the NPMI data structures.
3. To upload received data into the IS-H System, please call the function module ISH_NPMI_RECEIVE_RFDATA which handles the data receipt on the SAP side.
   
   

Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4573 Date: 20240426 Time: 083056     sap01-206 ( 72 ms )