Ansicht
Dokumentation
Case-Related Procedure Entry ( RELNISH_462_SR_NP47 )
Fill RESBD Structure from EBP Component Structure General Data in Customer MasterThis documentation is copyright by SAP AG.
Short text
Case-Related Procedure Entry
Use
In previous releases, you were only able to enter procedures in combination with a surgery. As of this release, you can enter case-related procedures for medical measures that are not related to a surgery.
You can enter and process procedures for a case, without a surgery, using the functions for processing and displaying case-related procedures (transaction codes NP47 and NP48).
You cannot assign case-related procedures to services or diagnoses. The system does not take these procedures into account in statistics, charge proposals, or billing. You can, however, assign a case-related procedure to a surgery at a later time because case-related procedures are also displayed in surgical data maintenance.
For case-related procedures, the following data is required:
- Departmental organizational unit
- Start date
- Start time
You do not have to enter an end time. If entries are not made in these fields, the system proposes data from the first movement of the case (admission or first appointment).
For more information on new fields, Customizing activities and DRG-relevant procedures, refer to the release note Surgical Data Processing.
In message control you will find two new messages. These messages let you specify whether or not:
- A departmental OU which is not used in the case can be entered for a procedure
- Departmental OU
| Field | Entry |
|---|---|
| Institution | |
| Function | NICP |
| Application area | N3 |
| Message | 296 |
| Preset type | W |
| Message type | |
| Message text | Dept. OU & is not used in |
| any movement of | |
| the case |
- A DRG procedure can be entered in a DRG surgical procedure code catalog other than the catalog specified in Customizing. A procedure is a DRG procedure if the category primary or secondary procedure is set.
- DRG Surgical procedure code catalog
| Field | Entry |
|---|---|
| Institution | |
| Function | NICP |
| Application area | N3 |
| Message | 295 |
| Preset type | W |
| Message type | |
| Message text | Catalog & is different |
| DRG catalog & |
With the system default settings, you will receive a warning message if you enter a departmental OU that is not used in the case, or a DRG surgical procedure code catalog that differs from the catalog specified in Customizing.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
To be able to enter DRG-relevant procedures, you have to have defined a DRG surgical procedure code catalog in Customizing. The DRG surgical procedure code catalog should be identical to the standard surgical procedure code catalog. For the purposes of testing, you can also use an alternative catalog to the standard one.
If you entered identical catalog keys in Customizing for the surgical procedure code catalog and the DRG surgical procedure code catalog, the system will also display DRG-relevant procedures in this transaction.
If the DRG surgical procedure code catalog differs from the surgical procedure code catalog, you are able to maintain DRG procedures in the DRG transaction only. For further information on the DRG transaction, refer to the following release notes:
- SG: DRG Data Processing (Release 4.61)
- DRG Processing: Released for All Country Versions (Release 4.62)
Further Information
BAL Application Log Documentation Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 5875 Date: 20240520 Time: 155240 sap01-206 ( 65 ms )
