[i.s.h.med Basis 1] Service Management 6.00 Application

i.s.h.med Training

i.s.h.med Basis 1 Service Management Application - Release 6.0

====!"§==Systems=

Contents

0 Contents 0

Contents......................................................................................................................................................... 2

1

Prerequisites.................................................................................................................................................... 3

2

Overview......................................................................................................................................................... 4 2.1 Classification of Terms.................................................................................................................................... 4 2.2 Overview ..................................................................................................................................................... 4

3

Application: Service Entry.................................................................................................................................... 5 3.1 i.s.h.med Service Entry (Release 6.0).................................................................................................................. 5 3.1.1 Overview............................................................................................................................................... 5 3.1.2 Settings for i.s.h.med Service Entry.............................................................................................................. 6 3.1.3 Entry of Services ..................................................................................................................................... 8 3.2 i.s.h.med Service Entry up to Release 6.0 .......................................................................................................... 11 3.2.1 Documentation of Material Consumption.................................................................................................... 12 3.2.2 Documentation of Involved Employees....................................................................................................... 12 3.3 i.s.h.med Subsequent Service Entry ................................................................................................................. 13 3.4 Additional Service Management Functions ........................................................................................................ 14

4

Table of Figures.............................................................................................................................................. 15

====!"§==Systems=

Page 2 of 16

Prerequisites

1

Prerequisites

This document is primarily for people with knowledge of the following subject areas: •

Foundations of the operation of i.s.h.med and SAP in general

•

Organizational structure (creation, modification)

•

Clinical work station (application and customizing)

•

OU parameters / system parameters / user parameters (entry options)

====!"§==Systems=

Page 3 of 16

Overview

2

Overview

2.1 Classification of Terms A service is a diagnostic or therapeutic procedure performed on a patient within the framework of a treatment. i.s.h.med enhances the possibilities of the administrative service entry (IS-H), which serves primarily to bill the procedures performed on the patient: •

Example Germany: Entry of basic nursing record for inpatient stays

•

Example Austria: Entry of single medical services

i.s.h.med works with the term medical service, which is already required in the planning process for controlling service communication (clinical order). In addition, the medical service is a navigational point to all its associated documentation elements, materials, or involved persons (team). Due to the system’s conversion of performed medical services into administrative items, the medical staff is relieved of billing-relevant tasks.

2.2 Overview The following is a description of the possibilities of medical service entry. As of Release 6.0 a new medical service entry function is available – this is described in detail under point 3.1. You can find a description of the service entry function used up until Release 6.0 and the associated application possibilities under point 3.2. Details on the material documentation and team entry (documentation of the employees involved), both functionalities in connection with the service documentation, can be found under points 3.2.1 and 3.2.2. The subsequent service entry and quick service entry are described under 3.3 and 3.4. Finally, you will find a description of the service management functions which can be integrated into the clinical work station.

====!"§==Systems=

Page 4 of 16

Application: Service Entry

3

Application: Service Entry

3.1 i.s.h.med Service Entry (Release 6.0) As of i.s.h.med Release 6.0 a new function is available for entering medical services. This new medical service entry contains all functions necessary for processing medical services and will, in future, replace both the service entry and subsequent service entry functions (see point 3.3) in i.s.h.med. Service processing can be adapted within the framework of basic item definition (see point 3.1.2). The new i.s.h.med service entry can be called directly from the clinical work station. To do this the function ZMEDSRV_CHANGE must be integrated into the function variant.

3.1.1 Overview

Fig. 1: i.s.h.med Service Entry (Release 6.0)

The following interface components are apparent in i.s.h.med service entry: •

Integrated hit list: The integrated hit list contains a list of the services of the organizational unit (OU) from which the service entry was called. You can change the hit list displayed using the

====!"§==Systems=

function in the

Page 5 of 16

Application: Service Entry

”Performing OU“ area. Configuration is also possible using the transaction N1COMPCON (see point 3.1.2). •

Context information: The context information area lists information on the patient, on the movement, etc..

•

Service entry: In the service entry area you document the services. The function toolbar can be changed as well as the layout of the table.

•

Detailed information on the service: If you wish to display detailed information on one of the services displayed, you select the service in the service entry area and then select the function.

3.1.2 Settings for i.s.h.med Service Entry The appearance of the i.s.h.med service entry can be changed using the transaction N1COMPCON (”Edit Component Configuration“):

Fig. 2: Component Configuration i.s.h.med Service Entry

You can use the component ID SAP_MEDSRV to change existing configurations and create new ones. An example of this are the function variant or layout settings of the service entry. You can use the function to access the configuration maintenance function. On the “Properties“ tab page you will find the “Layout“ and ”Function Variant“ areas. You can edit existing layout and function variants using the function. You proceed in exactly the same way as when maintaining views in the clinical work station. It is, of course, possible to create new variants and delete and/or copy existing variants.

Note: The hit list of the performing OU can be displayed as a dialog or as an integrated hit list.

====!"§==Systems=

Page 6 of 16

Application: Service Entry

Fig. 3: Configuration Component Properties (Layout and Function Variant) You can make the following settings on the “Presettings“ tab page:

Fig. 4: Configuration Component Presettings If the performing OU is preset you can define favorites on the “Hit List“ tab page:

Fig. 5: Hit List Configuration (Favorites)

To do this you select the entry to be transferred and execute the

====!"§==Systems=

function.

Page 7 of 16

Application: Service Entry

Note: The newly created configuration must be assigned via programming (BAdI, Z table, etc.). If the i.s.h.med service entry is used within the SAP Ambulatory Care Management module, assignment is also possible without previous programming.

3.1.3 Entry of Services In order to enter services, you must first select the patient in the clinical work station:

Fig. 6: Patient Selection and Function in Clinical Work Station

You then execute the

function (ZMEDSRV_CHANGE) and access the service entry:

Fig. 7: Medical Service Processing

You use the function to create a new service for the patient (the hit list of the performing OU is called). The service(s) to be transferred is (are) selected and entered for the patient using the pushbutton (transfer to service entry).

Note: If the display is not set as standard in the configuration, the hit list can be displayed or hidden using the

function.

The transferred services can be performed, replaced, or released using the (sub) functions

====!"§==Systems=

.

Page 8 of 16

Application: Service Entry

Note: You can use the user parameter “MLS“ to determine the preset service status.

•

Perform Service action: The status of the services changes to “performed“. When the service is performed the performing OU, employee responsible, and date are queried:

Fig. 8: Perform Service Dialog •

Replace Service action: During the Replace Service action, the originally entered service is canceled and replaced by the newly entered service(s) (a connection is made between the original service and the new entries):

Original Service

Newly Entered (“Replaced”) Service(s)

Fig. 9: Replace Service Dialog

====!"§==Systems=

Page 9 of 16

Application: Service Entry

•

Release Service action: If a service is replaced, the status changes to the “end status“ (e.g. confirmed, ok etc.). If the original service is a service which does not have the “performable“ indicator set (e.g. a group service), the release represents the implicit replacement. This means that the services assigned to the group are offered for replacement during the release. The status of the transferred service(s) is then correspondingly confirmed, etc., whereby in the above described replacement of the service, the status of the transferred services does NOT change:

Fig. 10: Release Service Dialog

Fig. 11: Replace Service During Service Release

In the above example (Fig. 11) the services HNOCYDOV and M6925 are assigned to the group service G-HNOCYDOV. The group service cannot be performed, hence the two single services are “offered“ for replacement. Of course, it is also possible to enter other services during the refunction. placement. You can do this using the

The function toolbar of the i.s.h.med service entry offers the following options for displaying the services of patients:

•

All services:

•

For current case:

•

For current movement:

•

For current visit sequence:

It is also possible to copy services which have already been entered using the tion ”Services from Movements“.

function, or the subfunc-

Finally, you should also note that in Release 6.0 the i.s.h.med service entry can be and is integrated into the documentation work station. Material and employee entry is therefore not directly possible (but can be programmed).

====!"§==Systems=

Page 10 of 16

Application: Service Entry

3.2 i.s.h.med Service Entry up to Release 6.0 Note: In the future the i.s.h.med service entry will be replaced by the service entry function described under 3.1. The following is a description of the functionality of the i.s.h.med service entry relevant up to Release 6.0:

The function is called using the function code LERF, and is integrated in the views of the clinical work station (outpatient clinic, service facility, etc.). Once you have selected the patient and called the function you access the service entry screen:

Fig. 12: Dialog i.s.h.med Service Entry up to Release 6.0

You can enter further services using the functions

(New Entry) or

(Service Hit List):

Fig. 13: Enter Further i.s.h.med Services (“New Entry” Function)

====!"§==Systems=

Page 11 of 16

Application: Service Entry

Fig. 14: Service Performance Hit List

The service is performed or released as described under point 3.1.3 using the relevant buttons (select the service first!). The material consumption and involved employees can then be documented:

3.2.1 Documentation of Material Consumption You document the material consumption using the service):

function (you must first select the

Fig. 15: Documentation Material Consumption

The presetting of the material consumption for a service is maintained using transaction NT45. You can enter additional materials using the pushbutton. If you wish to delete material from the documentation you can use the pushbutton. You can cancel assignments which have already been saved using the menu option Edit – Cancel. OU parameters can be used to make further material entry settings (see Customizing document).

3.2.2 Documentation of Involved Employees You can enter the involved employees (“team“) for each entered service. You call the team entry function, after selecting the service, using the

====!"§==Systems=

: function

Page 12 of 16

Application: Service Entry

Drag and Drop Task Proposal

Available Employees

Available Tasks

Fig. 16: Team Entry (“Involved Employees”)

In the “task proposal“ area the tasks to be completed are listed. If you wish to add further entries you can use pushbuttons. It is also possible to delete existing entries using . You can use the pushbutthe ton (either in the “Task Proposal“ or “Available Tasks“ area) to list the employees available for each task. You then assign by dragging and dropping from the “Available Employees“ area (see Fig. 16). If the employee is not listed, you can use the menu option task, to enter an external employee.

in the “Task Proposal“ area, having first selected the

You can delete an existing employee assignment using the

function.

3.3 i.s.h.med Subsequent Service Entry Another way of entering services is to use the function LPFL. In the subsequent service entry you can, in addition to the functionality described under 3.2, enter the departmental and nursing requesting OU, as well as the service date and time. The employee responsible is also ready for input. As in the i.s.h.med service entry you can enter further services either using the input help (F4) in the “Service“ field or using the hit list of the organizational unit . Other functions correspond to the procedure described under point 3.2:

====!"§==Systems=

Page 13 of 16

Application: Service Entry

Fig. 17: i.s.h.med Subsequent Service Entry

3.4 Additional Service Management Functions Some of the functions available under the service entry dialogs described under points 3.1 to 3.4, can be integrated into the Outpatient Clinic/Service Facility view type: •

ERBR: Perform service

•

AUFL: Replace service

•

AURU: Undo service replacement

•

QUIT: Release service

====!"§==Systems=

Page 14 of 16

Table of Figures

4

Table of Figures

Fig. 1: i.s.h.med Service Entry (Release 6.0) ................................................................................................................... 5 Fig. 2: Component Configuration i.s.h.med Service Entry .................................................................................................. 6 Fig. 3: Configuration Component Properties (Layout and Function Variant) ........................................................................... 7 Fig. 4: Configuration Component Presettings ................................................................................................................. 7 Fig. 5: Hit List Configuration (Favorites)......................................................................................................................... 7 Fig. 6: Patient Selection and Function in Clinical Work Station............................................................................................ 8 Fig. 7: Medical Service Processing .............................................................................................................................. 8 Fig. 8: Perform Service Dialog .................................................................................................................................... 9 Fig. 9: Replace Service Dialog .................................................................................................................................... 9 Fig. 10: Release Service Dialog................................................................................................................................. 10 Fig. 11: Replace Service During Service Release .......................................................................................................... 10 Fig. 12: Dialog i.s.h.med Service Entry up to Release 6.0................................................................................................. 11 Fig. 13: Enter Further i.s.h.med Services (“New Entry” Function) ....................................................................................... 11 Fig. 14: Service Performance Hit List.......................................................................................................................... 12 Fig. 15: Documentation Material Consumption ............................................................................................................. 12 Fig. 16: Team Entry (“Involved Employees”) ................................................................................................................. 13 Fig. 17: i.s.h.med Subsequent Service Entry................................................................................................................. 14

====!"§==Systems=

Page 15 of 16

Table of Figures

Copyright 2006 T-Systems Austria All rights reserved. ƒ

No part of this document may be reproduced or transmitted without the express written permission of T-Systems Austria.

ƒ

The information contained herein is subject to change at any time without prior notice.

====!"§==Systems=

Page 16 of 16