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 | SIMG_ISHCM_FCTDOC | IS-HCM Function Description |
| Transaction Code | S_KK4_74000433 | IMG Activity: SIMG_ISHCM_FCTDOC |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_ISHCM_FCTDOC | IS-HCM Function Description |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHCM_FCTDOC |
IS-HCM Function Description
Status: IS-H Release 4.71, January 2003
Contents
- Introduction
- HCM Dispatch & HCM Receipt
- SAP Communication Module
- HCM Dispatch Process
- HCM Receipt Process
- Message Formats
- HCM Express Dispatch
- IS-H BAPIs
- Introduction
IS-HCM (Hospital Communication Module) is part of the Industry Solution for Hospitals. The IS-HCM component (hereafter called HCM) comprises various services for exchanging data with other (hospital) systems.
"HCM Dispatch" enables the event-triggered asynchronous transfer of data from the IS-H system to partner systems. This means that dispatch is automatically initiated when application data is entered (admission, transfer, etc.) into the IS-H system. "HCM Receipt" enables the IS-H system to asynchronously receive data from the partner system.
"HCM Express Dispatch" enables the event-triggered synchronous transmission of admission data to partner systems.
"IS-H BAPIs" (Business Application Programming Interfaces) enable the high integration of partner systems with the IS-H system. They are based on RFC technology (Remote Function Call). Several IS-H BAPIs are supplied for different purposes. SAP has already shipped three function modules that can be used to test the basic functionality.
As of IS-H Release 4.03, the standard system has contained a number of BAPIs. For further information, refer to the Release Notes. More BAPIs will follow in coming releases. IS-H BAPIs are destined to play a role in communication from and with IS-H in the future. See the section entitled IS-H-BAPIs: Overview, Information in the IS-H Implementation Guide.
This document provides a short overview of the functionality of these HCM components. It explains the methods and techniques used. This knowledge is the prerequisite to designing and installing partner connections to IS-H. For detailed information, please refer to the appropriate sections of the IS-H Implementation Guide.
- HCM Dispatch & HCM Receipt
The HCM Dispatch and HCM Receipt asynchronous processes are described in this section. Furthermore, the message formatting used in these processes is described.
- SAP Communication Module
HCM Dispatch and HCM Receipt are based on the SAP Communication Module. This communications interface consists of two parts:
- the part resident in SAP (ABAP programs in thr SAP system) and
- the part which has to be installed in the partner system (executable programs supplied by SAP). This part is called the transceiver.
The SAP Communication Module is included in the IS-HCM delivery. SAP currently provides transceiver software for the following platforms (available under /specific/ish/HCM on sapservX):
ALPHAOSF for DEC Alpha OSF/1 3.2,
HP for HP UX 9.0x,
LINUXINTEL for Red Hat Linux 6.0 on Intel,
OS2 for OS/2 Warp 3.0,
OS400 for IBM OS/400 as of V3R7 on AS/400,
RM600 for SNI Reliant 5.41 on RM400/600,
RS6000 for IBM AIX 3.2.5,
SUN for SUN 5.4,
WNT for MS Windows NT 3.5, 4.0 on Intel,
WNT.DECALPHA for MS Windows NT 3.5, 4.0 on ALPHA.
To be able to use the transceiver software under OS/2, you need to have installed TCP/IP version 2.1 (or higher).
For information on the prerequisites to be satisfied for using the transceiver software under Linux, please see the SAP Note 171356.
If a suitable transceiver module is not available for the operating system of the host on which your subsystem is running, you need not forgo the functionality of the HCM transceiver. In such cases, you simply need to have a computer running one of the above supported systems in your network. You can install the transceiver module on this computer in such a way that the NFS (Network File System) functionality ('mounts' or 'links') retains the HCM transceiver functionality undiminished.
As can be seen from the above list of operating systems, the subsystems linked to SAP can run on various computers. Communication is always executed as CPI-C (Common Programming Interface - Communication) and is based on TCP/IP. The transceiver module link to the SAP system is established by the SAP gateway. The interfaces between the communications part and the actual partner application (such as a laboratory system) consist of several files in directories that can be defined individually.
- HCM Dispatch process
HCM Dispatch is event-triggered. When IS-H Dispatch is active, a dispatch order is created for each event (at the moment when data is saved) in the IS-H application transactions. Depending on how your system is configured, this order creates a message that is transmitted to all partner systems concerned by the occurred event.
IS-HCM receives these orders from the application. It determines which partner systems must be informed of the event and in what manner (message standard, message type, message format). It is possible to use a different message format for each partner system and each single event. HCM creates the required messages and transmits them to the partner systems (at regular intervals that can be defined by the system administrator).
Data is transferred from the SAP system to a subsystem by triggering HCM program RNCSND01. This program processes the data for one partner system after the other. If data exists for a partner system, this program first starts its partner program (PUT_TAB) in the subsystem. The required data is then read from the SAP database and routed to the communication partner via CPI-C.
Once the data has been successfully transferred, the messages are stored in their original format in a dispatch log table in the IS-H system. If the transfer fails, the data is retained in the dispatch table in the IS-H system. A renewed attempt is made to transmit it the next time the dispatch job is run.
The receiving program on the partner side (PUT_TAB) accepts the data and first stores it in a .tmp file, which is converted into the actual NTISH.dat interface file after a verification phase (check on the correct number of data records). Before this conversion is carried out, the interface status file SS_STAT.dat is locked in order to assure exclusive file access. This lock is implemented by the respective operating system mechanisms. For more information, refer to the section File locking mechanism in the chapter Explain programming of the partner programs. At this point, the system also makes an entry in the status file SS_STAT.dat, writing the table name NTISH and the timestamp.
Upon completion of the conversion, the receiver module deletes the .tmp file and releases the SS_STAT.dat. It then calls a script to inform the application running on the subsystem (such as the laboratory system) that new data has been sent by IS-H and is awaiting collection.
The next time IS-H sends data, the new data is attached to the existing data in the NTISH.dat interface file, thus assuring the chronological order of the messages.
- HCM Receipt process
HCM Receipt allows you to transfer client-specific data (messages) from partner systems into the IS-H system. The procedure assumes that the partner system assembles the data depending on the data type in special interface files. At present, HCM Receipt supports the transfer of the following data:
- Case-related diagnoses (file NT021.dat),
- Case-related services (file NT102.dat [or NT101.dat old])
- Surgical data (file NT104.dat [or NT103.dat old])
- OU-related services (file NT150.dat).
There are two ways of initiating the data flow from the partner system to the IS-H system:
- Trigger an IS-H program (RNCGET01, RNCGET02, etc., depending on the data type). This program starts its partner program GET_TAB in the partner system. GET_TAB reads all the data from the corresponding interface file and sends it to IS-H.
- Initiative for data transfer taken by the partner system by starting the transceiver program SEND_TAB in the subsystem. SEND_TAB first establishes the connection to IS-h where it starts its partner program RNCCDEXT, reads the corresponding interface file and transfers the data to IS-H.
Business Attributes
ASAP Roadmap ID 899 not to be assigned Mandatory / Optional 3 Nonrequired activity Critical / Non-Critical 2 Non-critical Country-Dependency A Valid for all countries Assigned Application ComponentsDocumentation Object Class Documentation Object Name Current line number Application Component Application Component Name SIMG SIMG_ISHCM_FCTDOC 0 I010004207 Communication Maintenance Objects
Maintenance object type 
History Last changed by/on SAP 19990816 SAP Release Created in
