SAP ABAP IMG Activity ISH_HCM_NPMI_DO_CUST (SG: NPMI Customizing)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
ID ISH_HCM_NPMI_DO_CUST SG: NPMI Customizing  
Transaction Code S_KK4_74000432   IMG Activity: ISH_HCM_NPMI_DO_CUST 
Created on 19990816    
Customizing Attributes ISH_HCM_NPMI_DO_CUST   SG: NPMI Customizing 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_HCM_NPMI_DO_CUST    

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.

  2. Maintain agreements with the data collection points

    All temporary specifications regarding the data collection points are combined under Agreements. These include agreements with the data collection points (special characters, compression, etc.) and processing parameters within your installation (path definition, code page, etc.).

    Regular automatic processing requires the specification of a separate directory for inbound and outbound data per data collection point in your filesystem. The directory name should include the key of the data collection point in order to facilitate the work not only during the test phase, but during the productive phase as well.

  3. 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.

  4. Maintain Number Range ISH_NC301

    Define the number range for EDI message administration in the number range object ISH_NC301.

    Note the following conditions:

    • Do not specify an institution. The number range is institution-independent.
    • The transaction mode must always be "N".
    • Specify an asterisk (*) in the Obj. Key field.
    • Enter the two-digit identification of an internal number range (e.g. "01") in the NI field.
    • Leave the NE field blank.
    • Do no select the A attribute.

      You maintain the number range interval by choosing Maintain Number Range and then Insert Interval. The system checks in each case whether the intervals overlap.

      Define an internal purely numeric number range here so that the system automatically determines a number in the corresponding situation.

      SAP recommends that you use a number range as great as possible (from '000...000' through '999...999') for this purely technical number. This will ensure trouble-free functionality for the long-term.

  5. Maintain Number Range ISH_NC301D

    Define the number range for EDI file administration in the number range object ISH_NC301D.

    Note the following conditions:

    • Do not specify an institution. This number range is institution-independent.
    • The transaction mode must always be "N".
    • Specify an asterisk (*) in the Obj. Key field.
    • Enter the two-digit internal identification of an internal number range (e.g. "01") in the NI field.
    • Leave the NE field blank.
    • Do not select the A attribute.

      You maintain the actual number range interval by choosing Maintain Number Interval and then Insert Interval. The system checks in each case whether the intervals overlap.

      You have to define an internal purely numeric number range here so that the system automatically determines a number in the corresponding situation.

      SAP recommends that you use a number range as great as possible (from '000...000' through '999...999') for this purely technical number. This will ensure trouble-free functionality for the long-term.

  6. Maintain Number Range ISH_NC301X

    If you connect an external transfer system which can process the files from one directory only, you also have to define a number range for this. The number range object ISH_301X is predefined for this purpose.
    If you do not use this 'all in one' directory logic, you do not need to create the number range.

    Note the following conditions:

    • Specify an institution. This number range is institution-dependent.
    • The transaction mode must always be "N".
    • Specify the respective EDI procedure (e.g. 'P301' for data exchange according to §301 SGB V in Germany) in the Obj. Key field.
    • Enter the two-digit internal identification of an internal number range (e.g. 01) in the NI field.
    • Leave the NE field blank.
    • Do not select the A attribute.

      Maintain the actual number range interval by choosing Maintain Number Range and then Insert interval. The system checks in each case whether the intervals overlap.

      Define an internal purely numeric number range here so that the system automatically determines a number in the corresponding situation.

      Please consult the manufacturer of the transfer system when defining the number interval for the number range, since both systems will work with this number.

      In particular, when several EDI procedures are active in the one institution, and in instances when several institutions exist, you have to use different intervals for different EDI procedures.

In such cases, the use of a single number range interval is not sufficient to ensure contiguous number assignment per institution and EDI procedure. Define the number range in relation to the capabilities of the transfer system.

SAP recommends that you use a number range as great as possible (from '000...000' through '999...999') for this purely technical number. This will ensure trouble-free functionality for the long-term.

SAP makes the following recommendation when several different intervals are used: distinguish these intervals using the initial two or three digits. The remaining digits should again make for as great an interval as possible.

Example:

  • Institution 1, P301: 0110000000 through 0119999999, institution 1, P302: 0120000000 through 0129999999
  • Institution 2, P301: 0210000000 through 0219999999, institution 2, P302: 0220000000 through 0229999999.

  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).

  2. 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.

  3. 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.

  1. EDI troubleshooting

  • If no EDI messages were created, you have to check through t
Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
ISH_HCM_NPMI_DO_CUST SG Singapore
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ISH_HCM_NPMI_DO_CUST 0 I010004233 Communication with Systems Outside the Hospital 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990816 
SAP Release Created in