Function documentationCancel Objects in i.s.h.med

 

A standardized cancellation function is available for canceling objects in i.s.h.med. This means that when canceling all objects, you will always access a standard dialog box, where you can cancel, for example, the following objects:

  • Services

    If you wish to cancel a service, which is already assigned to an appointment, the system must also cancel this appointment. It is therefore preselected and cannot be deselected.

    The movement (visit) is preselected and can be canceled as an option.

  • Documents

  • Appointments

    If you wish to cancel an appointment, the assigned movement (visit) is preselected and can be canceled as an option (regardless of the visit status).

    The assigned service is always preselected, but can no longer be deselected once the service has Released or Performed status.

  • Clinical Orders

    See Cancel Clinical Order

  • Order items of clinical orders

  • Transport Orders

  • Requests

From the object to be canceled, the dialog box displays a list of all dependent objects which can or must be taken into account during cancellation.

See Dependencies of Medical Objects when Canceling

Whether a dependent object must be canceled, or can be canceled as an option, depends on whether the dependent object can also exist without the superordinate object:

  • The system will indicate dependent objects which can be canceled as an option, by setting the checkbox for this object ready for input.

  • The system will indicate dependent objects which must be canceled, by selecting the object and no setting the checkbox for this object ready for input.

    Example Example

    You wish to cancel a service. An appointment and a case-related procedure exist for this service. The system will automatically also cancel the appointment if no other service is assigned to it. In the case of the case-related procedure, you can decide whether it should also be cancelled as an option.

    End of the example.

If you can or must cancel a dependent object, the cancellation of this dependent object may necessitate the cancellation of further objects.

Example Example

When canceling an object you wish to optionally cancel a movement, for which two subsequent movements exist. If you select the movement for cancellation (check the checkbox), you must also cancel the two subsequent movements. In this case, the checkboxes of the two subsequent movements are already selected and not ready for input.

End of the example.

If the system cannot cancel a dependent object which you wish to cancel or must also be canceled, it also cannot cancel the originally selected object.

Example Example

If the system cannot cancel an object which is dependent on a clinical order, it also cannot cancel the clinical order.

End of the example.

Caution Caution

If the last visit of an outpatient case is selected for cancellation, the case will also be canceled. If dependent objects exist for the movement or case, which cannot be cancelled, the system also will not cancel the movement and therefore the case.

End of the caution.

If you cancel objects of SAP Patient Management (IS-H) (for example, a movement or a case), the system also cancels the dependent objects from i.s.h.med (for example, associated clinical orders, requests, and services). Here, the system takes the medical objects into account in the same way as when canceling the medical objects themselves.

See Dependencies of Medical Objects when Canceling

Example Example

For instance, if you cancel the last movement for a case to which requests are assigned, the system issues a warning that informs you that requests are assigned to this case or movement and will be canceled too.

In response to this warning, you can cancel the cancellation process or go ahead and cancel the movement, the case and consequently the associated requests.

End of the example.

Integration

The following user exits and Business Add-Ins (BAdIs) are available for customer-specific enhancements to the cancel function:

  • Cancel service - initial screen (N1LF0001)

    Detaillierte Informationen entnehmen Sie dem Einführungsleitfaden unter Start of the navigation path Branchenlösung Klinisches System Next navigation step Leistungsmanagement Next navigation step Exits und BAdIs zu den Leistungen Next navigation step Exit: Stornieren von Leistungen – Einstieg End of the navigation path

  • BAdI Implementation – Cancel Function (N1_CANCEL)

    Detaillierte Informationen entnehmen Sie dem Einführungsleitfaden unter Start of the navigation path Branchenlösung Klinisches System Next navigation step Anwendungsübergreifende Einstellungen Next navigation step BAdI: Stornofunktion End of the navigation path.

Features

Presentation

In the dialog box, the system will display in tree structure.

  1. The top node always displays the patient or patients, if you wish to cancel the same objects for different patients.

  2. Below the patient, the system will display the object to be canceled (for example, service).

  3. Subordinate to this node, the system will display a folder for each dependent object class (for example, a folder for the materials of a service). Each folder also displays the number of objects contained.

  4. In these folders, the corresponding dependent objects are displayed (for example, material for service). The objects themselves display the most important information on the object in the hierarchy area. This information corresponds to the information which is also displayed in the patient organizer.

    • Case

    • Date

    • Time

    • Organizational unit (OU)

    • Employee responsible (EmR)

    • Status

      For services, this is the service status, and for movements, this is the movement status.

    • Classification (use dependent on displayed object)

      The system displays, for example, for documents, any existing special indicator.

    • Key

      The key displayed is dependent on the object which is displayed, e.g. technical name of the document category.

    • Context

      For the clinical order the system displays objects which were assigned using a context in the form of a description of the context.

    • Context icon

You can individually adapt the layout of the information for the object to suit your individual needs. Depending on the authorization (authorization object N_VM_DEF) you can define layouts for specific users or for all users.

Error Messages

The system will display any error message or warnings in the dialog box of the Cancel function in additional display area. If an error message refers to an object in the tree structure, you can double-click this message to branch directly to this object.

You can also branch to the long text of the error message.

For better clarity the system will indicate the object originally to be canceled as follows:

  • - (-) No error or warning exists; you must not make a decision concerning dependent objects. Cancellation is possible.

  • Yellow light: Warnings exist or you must make decisions concerning dependent objects. Cancellation is possible.

  • - (-) Errors occurred. Cancellation is not possible.

Activities

To cancel the selected object and the corresponding dependent objects, you must:

  • Mark the objects you want to cancel optionally

  • Enter the cancellation reason

    You define cancellation reasons in the Implementation Guide under Industry-Specific Component Clinical SystemCross-Application SettingsMaintain Cancellation Reasons.

  • Enter the employee responsible

    Note Note

    The cancellation reason and employee responsible are also valid for the dependent objects which should also be canceled. The system will not take into account whether the cancellation reason is also defined in the master data for the dependent object.

    End of the note.

Example

If, for example, you cancel a clinical order, the system will cancel the following dependent objects, or offer them for cancellation:

  • All order items

  • All services for the order items

  • Appointment templates for the order items

  • The system will deactivate the currently active status object for the order items

  • Appointments for the appointment templates and/or appointments for the order items services, if no other objects are linked to the appointment

  • The provisional patient master data, if the clinical order is the last object with which this data is connected