Connect a DRG Grouper 

Use

SAP Patient Management is open and flexible to accommodate data exchange with various DRG groupers. The SAP Patient Management generic interface operates with parameters and tables, which SAP Patient Management translates upon export into external values, either in a customer-specific ABAP function module, or in an external executable file, connected to SAP Patient Management via an RFC connection.

SAP Patient Management is the leading system in terms of data integrity. This means that you can only change patient master data and the case-related data in SAP Patient Management, and not via an import from the DRG grouper. If you need to change this type of data as well, make use of the SAP BAPI constructs and build these into your system environment. The generic interface uses BAPI structures wherever existent, and SAP Patient Management table structures and parameters otherwise.

Prerequisites

Considerations for determining whether the layout of the external system satisfies SAP Patient Management requirements:

·        Does the system allow interactive DRG determination, or is determination an automated batch process?

·        Is the data exchange file-based, or via direct parameter transfer?

·        Does the system support multiple users?

·        Do these users have an SAP Patient Management license?

·        Are the diagnosis and procedure codes exported from SAP Patient Management to be used in the external DRG grouper?

·        What type of catalog do you use for DRG codes and DRG-relevant diagnoses and procedures?

·        Do you need to operate several DRG groupers, or only one?

When importing the data, SAP Patient Management only saves the value imported last. If you determine DRG values from several DRG groupers, you have to decide which is the relevant value.

Features

The following parameters and tables are provided for exporting data:

Parameter Name	Description	Structure/Fields
Generic function provides these parameters for the export process
SS_PATIENT_DATA	Structure with patient master data such as name, sex, birthdate.	BAPI1084OUT
SS_CASE_DATA	Structure with case data.	BAPI2097CASE
SS_BIRTH_DATA	Structure with newborn's birthdate.	NGEB
SS_ADMIN_DATA	Structure with following administrative data: Hospital basic case value, currency key for hospital basic case value, length of stay, same day case, involuntary treatment indicator, cause for admission, main department, external physician department.	ISH_DRG_ADMIN_DATA
SS_CONNECTION_DATA	Structure with DRG grouper agreement data from Customizing for SAP Patient Management.	TNGRP2
SS_FILE_NAME	Structure with name of the data exchange file that is to be written.	255 characters
SS_USER_NAME	Structure with SAP user name of user triggering data export.	12 characters
SS_MOVEMENT_TAB	Table with information for admission and discharge.	BAPI2097MOVE
SS_DIA_TAB	Table with DRG-relevant diagnoses and their attributes.	BAPI2098DATA
SS_ICP_TAB	Table with DRG-relevant procedures and their attributes.	NICP2
Generic function expects to receive these parameters for bilateral mode, when import and export are done with one function call
SS_RETURN_CODE	0 = Data exchange is ok.	Type Integer
SS_RETURN_TAB	Table with error messages.	BAPIRET2
SS_DRG_TAB	Table with one entry that contains the DRG value and all attributes such as MDC, SOI, ROM, grouping date, user and comment.	NDRG
SS_DIA_TAB	Table with one entry that contains the DRG-relevant diagnoses and their attributes as determined or changed by the DRG grouper.	BAPI2098DATA
SS_ICP_TAB	Table with one entry that contains the DRG-relevant procedures and their attributes as determined or changed by the DRG grouper.	NICP2

Function module ISH_OLE2_ID_GROUPER_OUT provides an example for this interface.

The following parameters and tables are provided for importing data:

Parameter Name	Description	Structure/Fields
Generic function passes these parameters for the import process
SS_INSTITUTION	SAP Patient Management institution from where the import process was started.	4 characters
SS_CASE	SAP Patient Management case number for which the import process was started.	10-digit number
SS_CONNECTION_DATA	Structure with the DRG grouper agreements that you stipulated in Customizing for SAP Patient Management.	TNGRP2
SS_FILE_NAME	Structure with name of the data exchange file that the system is to read.	255 characters
SS_FILE_ARCHIVE	Structure with the name of the archive file. After successfully importing the inbound file, the system moves it to the directory which serves as an archive. Make sure that the house-keeping of the archive occurs regularly.	255 characters
SS_USER_NAME	Structure with SAP user name of user triggering data import.	12 characters
SS_DATA_GIVEN_DIRECTLY	Flag set to ON if system has already transferred the data because export/import was done in bilateral mode.	1 character (space or X)
SS_FILECONTENT	If the SS_DATA_GIVEN_DIRECTLY flag is set, this table contains the DRG data read from the import file.	RNCMAIL
Generic function expects these inbound parameters from the concrete function module
SS_INSTITUTION_IN_FILE	Institution the system actually found in the DRG file.	4 characters
SS_CASE_IN_FILE	Case number the system actually found in the DRG file (with leading zero).	10-digit number
SS_RETURN_CODE	0 = data exchange is ok; 4 = technical system error, file could not be processed; 8 = external DRG grouper reports error.	Type Integer
SS_RETURN_TAB	Table with error messages.	BAPIRET2
SS_DRG_TAB	Table with one entry that contains the determined DRG value and all attributes such as MDC, SOI, ROM, grouping date, user and comment.	BAPI2098DATA
SS_ICP_TAB	Table with the DRG-relevant procedures and their attributes determined by the DRG grouper.	NICP2

Function module ISH_DRGCDF_FORMAT_3MTAG_IN provides an example for this interface.

Activities

You can start the export process in the following ways:

·        Single case processing: Choose  Export DRG Data in the DRG transaction.

For more information, see DRG Work Station.

·        Mass processing: Start the program IS-H: Data Exchange with DRG Grouper for Multiple Cases (RNUDRG0A). You can also schedule this program to run as a background job.

You cannot schedule the program to run as a background job if you are using a DRG grouper connected via an OLE interface.

For more information about this, see Data Exchange with DRG Grouper for Multiple Cases.

SAP Patient Management is able to inform the DRG grouper that an export has taken place. For an example API/RFC function module, refer to ISH_DRGCDF_EXPORT_PARTNER_CALL. This function module caters for various processing options that you can select in the table of DRG grouper agreements in Customizing for SAP Patient Management. You can use this function as a template to create processing steps specific to your hospital. Copy this function into a function in your own name range, and specify the new function name in the agreements Customizing table.

You can start the import process in the following ways:

·        When the DRG grouper is connected directly, the import function can be incorporated into the export function.

·        Single case processing: Choose  Import DRG Data in the DRG transaction.

For more information, see DRG Work Station.

·        Mass processing: Start the program IS-H: Data Exchange with DRG Grouper for Multiple Cases (RNUDRG0A). You can also schedule this program to run as a background job.

You cannot schedule the program to run as a background job if you are using a DRG grouper connected via an OLE interface.

For more information about this, see Data Exchange with DRG Grouper for Multiple Cases.

In such cases, the parameters SS_INSTITUTION and SS_CASE might be empty. The concrete interface function must cater for this.

·        Via an external trigger directly from the DRG grouper, on condition that the external system supports the trigger. The trigger calls the API/RFC function module ISH_DRGCDF_IMPORT_PARTNER_CALL thus prompting SAP Patient Management to start the data import process.