Kontakt

Ansicht
Dokumentation

BAPI_MEDSRV_CREATEMULT_PATIENT - IS-H*MED: BAPI Medical Service Create Multiple - Create Medical Services

BAPI_MEDSRV_CREATEMULT_PATIENT - IS-H*MED: BAPI Medical Service Create Multiple - Create Medical Services

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This BAPI method is part of the Clinical System component of IS-H*MED for hospitals.

It is used to create medical services for a patient who is already known in the system. You cannot create services for provisional patient master data using this method.

Example

Notes

You must enter the client, institution and patient number for which you wish to create the service, as import parameters.

The following fields must be filled in the MEDICALSERVICE_INPUT table:

  • CLIENT (Client)
  • INSTITUTION (Institution)
  • PATIENTID (Patient Number)
  • BPARTNER (Business Partner)
  • SERVICE_STATUS (Service Status)
  • PERFORM_OU (Performing Organizational Unit)
  • SERVICEID (Service within Service Catalog)
  • REQ_NURS_OU (Nursing Organizational Unit)
  • ALTBILLCAT (Service Catalog Identification)

If you enter a case number which already exists for the patient (which is optional), the system will create a case-related service. No other optional fields have an effect on the process of this function.

If you optionally enter the sequence number (SERVICE_SEQNO) of the service, the system will not interpret this when creating the service. Following a successful update, the system will return the sequence number of the service, generated by the system, using the tables MEDICALSERVICE_OUTPUT and STATUS_OUTPUT.

During this method, the system will first check existing tables for errors and consistency. If the system finds an error in a record, it will log this internally and will not change the service in the database.

You must use the internal description when entering the service status. The BAPI method is implemented for the following service statuses:

  • Requested
  • Performed
  • Released
  • Canceled
  • Confirmed-Requested
  • Unconfirmed-Requested

The parameter TESTRUN is optional. If it contains an "X", the module will run in test mode. The test mode is used to check transferred data (for consistency and errors). The system will return to the user any errors determined during this check in the RETURN table. The system will not write to the database in test mode.

Possible return values and their meanings are listed in the parameter documentation for the RETURN table.

You will require the following authorizations to execute this method:

  1. On Patient level: N_NLEM_PATNR;
  2. On Service level: N_NLEI_ANF, N_NLEI_ANP and N_NLEI_ERB.

The system will try to process, i.e. update, every transferred MEDICALSERVICE_INPUT record. If you are creating several data records and one service (i.e. its attributes) is incorrect, the system will still process all other data records. The system will not update the incorrect service. It will produce a relevant error message.

Further information





Parameters

CLIENT
INSTITUTION
MEDICALSERVICE_INPUT
MEDICALSERVICE_OUTPUT
PATIENTID
RETURN
STATUS_OUTPUT
TESTRUN
WORST_RETURNED_MSGTY

Exceptions

Function Group

1410

CL_GUI_FRONTEND_SERVICES - Frontend Services   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5139 Date: 20240523 Time: 181839     sap01-206 ( 72 ms )