Ansicht
Dokumentation

Case List: Reassign or Copy a Visit with Template (New) ( RELNISH_472_BZ_CASREV )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Short text

Case List: Reassign or Copy a Visit with Template (New)

Use

The case list in this release contains two new functions:

• Reassign a visit to an existing or a new case

• Create a visit with template for an existing or a new case.

The new features in detail:

• Reassign:

When carrying out case revision, you can reassign outpatient visits from one case to another case of the same patient. The system includes all dependent objects (services, for example) in this reassignment. Reassignment assists you in correcting cases. For example, when you have two concurrent cases and assign a visit to the wrong case, the new function provides a simple way of reassigning the visit to the correct case.

Procedure

1. In the case overview (transaction code NP10), select the visit you want to reassign. If you want to reassign this visit to an existing case, also select the target case.
2. Choose Case Overview -> Case Revision -> Reassign Visit.

The system sends a dialog box containing the movement to be reassigned with all dependent objects (source case). You can execute a test run using the "Check" icon. When you choose the "Execute" icon, the system executes the process. You can no longer cancel the process.

If an error occurs, the system outputs the corresponding message in the lower part of the dialog box and terminates the process. This prevents inconsistent data from being recorded on the database. Correct the cause of the error messages, and repeat the process.

1. Once reassignment has been successfully carried out, the system displays the reassigned movement and its dependent objects in the right-hand area of the dialog box (target case). All of the objects that the system canceled are highlighted in color in the target case. The "Back" icon returns you to the case list. When you choose "Refresh" in the case list, the changes become visible.

Caution: A reassigned visit is not entirely identical to the original visit. For this reason, if you reassign a visit to another case then assign it back to the original case, it cannot be guaranteed that the system restores the original status. You should therefore only use the "Reassign" function after a thorough check of the situation.

• Create with template:

This function enables you to create a visit using default values from an existing visit. You can also include all the dependent objects (services, for example).

Procedure:

1. In the case overview (transaction code NP10) or in the Clinical Process Builder (transaction code NV2000), select the visit you want to use as the template for a new visit.
2. From the case overview, choose Goto -> Outpatient Visit -> Create or Create Outpatient Case, or from the Clinical Process Builder choose Case List -> Create Visit -> With New Outpatient Visit or For Existing Case.

If you choose "Create" and have not selected another case as the target case, the system assigns a visit to the same case. Otherwise, it creates the copy of the selected target case.

If you choose "Create Outpatient Case" or "For New Case", the system creates a new outpatient case with the template of the selected visit.

1. The system sends a dialog box containing the template movement with all the dependent objects (source case). You can execute a test run using the "Check" icon. Choosing the "Create without Template" icon takes you directly into the Clinical Process Builder without applying the template data. When you choose the "Execute" icon, the system executes the process. You can no longer cancel the process.

If an error occurs, the system outputs the corresponding message in the lower part of the dialog box. This message tells you which objects the system was unable to create. You have to manually postprocess these objects.

Once the process has been successfully carried out, the system displays the new movement and its dependent objects in the right-hand area of the dialog box (target case). The "Back" icon returns you to the admission in order to check the data you have created.

Note that after the function has been executed, the data is saved on the database. It is no longer possible to cancel the process.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

The system behavior is determined by whether a user has the authorization for case revision (authorization object N_CASE_REV):

• If a user has the authorization for case revision, the system does not perform an authorization check in the individual objects and runs the entire process.

• If the user does not have this authorization, the system checks the authorization for each single object. If an error is encountered, the system terminates the process.

The authorization object N_CASE_REV has two activities:

• Copy

• Move

Effects on Customizing

In Customizing for SAP Patient Management (IS-H), you make the following settings by choosing SAP Healthcare - Industry-Specific Components for Hospitals -> Patient Management -> Cases -> Define Case Revision Settings:

• Cancellation reason:

The cancellation reason specified here must be defined in the IMG activity Maintain Cancellation Reasons. The Movement and General Cancellation Reason indicators must be set for this cancellation reason. We recommend that you create a separate cancellation reason for the case revision process, thereby making it easier to identify the objects canceled by the process. The system enters the cancellation reason you specify for the case revision in all of the objects that are reassigned and that accommodate a cancellation reason.

For further information, see the IS-H Implementation Guide under SAP Healthcare - Industry-Specific Components for Hospitals -> Patient Management -> Movements > Cancellation Reasons.

• Medical Status:

The status specified here must be defined in Customizing for the Medical Case Status (IMG activity Define Status Profile). We recommend that you create a separate status that enables a check on the reassigned movements and their cases. In particular, it should still be possible to change diagnoses and procedures. Both the source case and the target case are assigned this medical status before the process is executed. The system does not however change the status of a case whose medical status is initial.

If you do not specify a status, the system checks the statuses that are assigned to the source or target case.

For further information, see the IS-H Implementation Guide under SAP Healthcare - Industry-Specific Components for Hospitals -> Medical/Nursing Documentation -> Basic Medical Documentation Status Management -> Maintain Status Profiles.

Further Information

For detailed information about the reassignment procedure and creating movements with a template, see the SAP Library under IS-H/IS-H*MED -> IS-H Hospital -> Patient Management.

CPI1466 during Backup   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 8777 Date: 20240602 Time: 054329     sap01-206 ( 155 ms )