Data Sheet SW Ishmed Ward

8/16/2019 Data Sheet SW Ishmed Ward

http://slidepdf.com/reader/full/data-sheet-sw-ishmed-ward 1/9

www.siemens.com/healthcare

i.s.h.med wardData Sheet

Answers for l ife.



Dokumenten ID: Data Sheet SW ishmed ward en.doc Page 2 / 9 Released Date: Date of last signature, Status: Released

Solution Definition

i.s.h.med® ward is the specific documentation work station

for work in the wards of the hospital. The module is based

on the idea of task-centered work in the inpatient area.

Tasks are generated from process steps and displayed as a

worklist for the respective user. These task lists can be

defined using various criteria and called quickly (e.g.

specific to occupational groups or a specific time period).

From the worklist the user can directly access the

corresponding documentation (e.g. anamnesis form) or

receive the necessary information (e.g. lab results).

Moreover, the clinical overview can be filled with various

modules containing content on different topics in a

standardized interface on a customer-specific basis.

The customer can therefore determine the content and

appearance of the clinical overview himself to a large

extent and, in this way, define the information which is

presented to the user.

Fig.1: i.s.h.med Modules in Connection with SAP

Performance Features

i.s.h.med ward (10415867)

The components in the i.s.h.med ward module facilitate the

routine work of the medical and nursing staff on the care unit

(= ward). A key component is the ’Ward Documentation Work

Station’.

Ward Documentation Work Station

The ’Ward Documentation Work Station’ can be used to mapprocesses, such as, for example, the inpatient admission, the

preparation of examinations or the discharge, with their tasks.

At the same time the work station also provides information

tailored to the situation and tasks.

￭ The ward documentation work station’ is integrated into

the Occupancy, Arrivals, Departures and Coding Analyses

view types in the clinical work station.

￭

It offers template management for creating task, profile

and situation templates. These objects form the basis for

the task list of the documentation work station as well as

for the task catalog.

￭

It offers a full screen work station in which variousinformation areas and functions can be simultaneously

displayed on the screen and comprises the following

components:

- Work station header for displaying superordinate data

of a work situation such as for example, patient data.

- Global toolbar for the integration of functions, which

are not suitable for task-related processing, for

example, display of cumulative lab results.

- Task component for defining and mapping tasks and

situations in the inpatient area. The task list displays all

tasks which belong to a situation. A situation groups

together tasks that are to be completed for one ormore patients in a work situation on the ward

documentation work station.

- Patient viewer - (display component). This shows

information from the electronic patient record which is

relevant to the work situation. As an alternative to the

patient viewer. Display in the chart in i.s.h.med is also

possible.




- Chart component – (optional additional module

i.s.h.med charting) displays selected patient record

data graphically on a joint time axis. You can only

display this component as an alternative to the

patient viewer.

- Clinical overview – enables customer-specific

composition of various modules with content

regarding different topics in a standardized

interface.

- Documentation objects – are the processing

interfaces connected with the tasks, such as forexample, the ’dialog of the inpatient progress note’

or the ’dialog for the medication order’. The ’clinical

overview’ can be displayed in the area in which the

documentation object is displayed. Alternatively, it is

possible to call documentation objects for the

‘clinical overview’.

- The use of documentation objects and their

properties is only possible in the documentation

work station. The following documentation objects

are available:

- Administrative services

- Diagnoses

- Procedures

- Medical services

- Parameterized medical documents (prerequisite

Gen. V. 2)

- Clinical order

- Medication orders (i.s.h.med medication license

required)

- Vital sign entry

- Allergy documentation

- Display information in a browser (URL)

- Call up form printing

- Freely definable documentation objects

- Inpatient progress note

- Nursing planning (i.s.h.med nursing license

required)

- Nursing service documentation (i.s.h.med nursing

license required)

- Base items create the link between the process-

supporting objects of various applications (such as, for

example, tasks in the ward documentation work

station) and the individual i.s.h.med documentation

objects (such as, for example, clinical order,

document, etc.).

- Base items are used by various modules which are

based on i.s.h.med.

Fig. 2: ’Ward Documentation Work Station’ with Integrated Chart and Clinical Overview (Example)




- Base items are defined by the object which assigns

them to a specific process step (task of a situation in

the documentation work station).

- Depending on the type, base items enable extensive

semantic presetting of the relevant object in

i.s.h.med, for example the exact specification of an

entire order profile for a certain step within a clinical

pathway.

- Using the semantics of the preset content, base

items also define the actions which should happen

to the assigned object, as soon as the concerned

calling process step is triggered for the first time or a

repeated time (e.g. create a specific document as

the initial action, call document in change mode as

the repeat action).

- In i.s.h.med base items are supported for:

Administrative services, requests, medication orders,

business add-ins (BAdI), treatment pathways,

surgical documentation, diagnoses, documents,

form printing, clinical orders, complications,

material entry, medical services, surgery times,

problems, procedures, team entry, textual orders,

transactions, URLs, progress entries.

Clinical Task Management

Clinical task management

￭

represents a component of the ward documentation

work station.

￭ comprises template management with the previously

individually used applications for a predictable work

situation in which a navigable task selection can be

compiled.

￭ supports the definition of static situation templates. For

this purpose tasks are grouped that are to be completed

for one or more patients in a work situation on the ward


￭

supports the definition of dynamic task lists. During thisthe tasks from all work processes are collected and

displayed as a to-do list.

￭

The Tasks API facilitates the program-controlled creation

of tasks.

￭ Event handling in clinical task management enables the

setting of the status of a task to 'completed' for

individual applications.

’Situations’ in the Ward Documentation Work

Station

‘Situations’ in the ward documentation work station support

the documentation with specific information for each work

situation.

￭

A situation groups together tasks that are to be completedfor one or more patients in a work situation on the ward

documentation work station. Static and dynamic

situations are differentiated here.

￭ A static situation comprises the tasks which were defined

in the static situation template and assigned to a patient

as a situation.

￭ A dynamic situation contains the tasks that satisfy the

selection criteria of the dynamic situation template at

runtime with regard to the selected patients.

A situation comprises the following optional elements:

￭

Task list - supports documentation in connection with awork situation in which different applications, each with

specific information, are required.

￭ Information text – used to display and view the details of

a situation. This can include an explanation of how to

work with situations which are created from this template.

The user can see the text in the assignment dialog, in the

selection dialog, or in the documentation work station.

￭ View components – used for the integrated display and

view in the patient record, in the clinical overview or in

the chart component.

Situations are created from situation templates. As soon as astatic situation template is assigned for a patient, the

situation and the corresponding tasks are created for the

patient according to the template.

Alternatively, it is possible to create a ‘quick processing’

situation. The user selects one or more task templates. The

system then creates a situation and a number of tasks for

each patient.

The ’Display Situation’ situation type enables the display of the

’clinical overview’ as well as the info area with the chart and

the patient viewer in the clinical work station.

’Tasks’ in the Ward Documentation Work Station

The task list in the ward documentation work station groups

tasks for one or more patients and enables navigation across

different documentation objects. Tasks are placeholders for a

work step in the treatment planning of a patient. The tasks

can be processed in the documentation work station by

choosing a function for selected patients in the clinical work

station.

There are two types of task lists in the ward documentation

work station:

￭ Static task lists - are elements of static situations, whose

tasks are defined in the situation template’s structure. You

can add further tasks to the situation in thedocumentation work station.




￭

Dynamic task lists – determine the quantity of taskswhich correspond to the selection criteria for the

selected patient and the specific time.

The task list supports the following functions:

￭

Complete Task - Sets the status of the selected task to

‘completed’. Shows that this part of the treatment has

been completed.

￭ Cancel Task - Sets the status of the selected task to

‘cancelled’. Shows that this task must not be completed

in this situation.

￭ Add Task – Opens a dialog in which further tasks can be

inserted into the current situation. The system displays astructured list of all tasks and profile templates which

are active and have the ‘Available in Selection’ indicator

set. Profiles enable the insertion of a group of task

templates. It can be necessary to add tasks if particulars

arise during the treatment of a patient, which were not

taken into account in the situation template.

￭ Close Situation - Closes a situation following the

completion or cancellation of at least all required tasks.

Tasks, which are not required tasks and which have not

been completed, can be automatically canceled when

the situation is closed. The system only displays opensituations in the selection list for editing situations.

￭ Create Situation Note – Opens a note window for the

entry, display or editing of a note. As this note function is

also available in the assignment dialog, admission staff

can enter organizational information here which is then

accessible during treatment.

￭ Edit Layout – Enables layout adaptation in the task list, for

example, ‘Hide Column’. The layout can be changed, if

necessary, or retained for each individual user.

￭ Show Situation List - Shows the situation list even if only

one single patient was selected in the clinical work

station.￭ Show Detail View – Shows an information area. The lists

receive an additional information column and display

information which was entered for the situations or tasks

in template management.

￭

Open Situation (for Patient) - If the patient has at least one

further open situation, you can add it to the situation list.

￭ Show / Hide Situation List - When task lists are long, you

can hide the situation list.

￭ Work Patient-/ Situation-Related - If several open situations

of a patient have been selected for processing, you can

Fig. 3: Task List (Example)




display the tasks for each situation or in a common"patient-related" list. If several patients have been

selected, you can navigate among the patients using a

dropdown list in the patient-related display.

￭ Change Responsibility - The occupational group

responsible can be changed by processing agents of this

occupational group. Select a different responsible

occupational group if the task is to be further processed.

￭ Change Priority – Determine the priority.

￭ Edit Task Again – Can be used if the ’completed’ status

was set by mistake.

Clinical Overview

The ‘clinical overview’

￭ represents a view component of the ward


￭ offers the user a quick overview of the most important

patient data.

￭

is used to enhance other view components such as, for

example, the patient viewer and chart component

(optional additional i.s.h.med charting module).

￭ supports the option of defining specific overviews for

different work situations.

￭

comprises supplied information blocks which display thespecific objects of a patient:

- Patient Data

- Patient Header

- Relatives/Persons to Contact

- Insurance Relationships

- Case List

- Movements

- Allergies

- Patient's Physicians

- Referrer and Family Physician

- Diagnoses

- Procedures

- Medication Order

- Surgeries

- Vital Signs

- Medical Documents

- Inpatient Progress Report

- Lab values with a trend display and highlighting of

critical value ranges

Fig. 4: Clinical Overview (Example)




￭

enables the individual design of the overview displaybased on predefined floor plans. The following floor

plans are supplied:

- Floor plan for one info block only

- Single-column floor plan with four areas

- Two-column floor plan with four areas each

- Floor plan with different sized areas

- Floor plan with a T split

- Two-column floor plan; the left column provides one

area, the right column three areas.

- Two-column floor plan with four areas each, as well

as header and footer area.

- Complex floor plan with areas of different sizes, as

well as header and footer area.

￭ supports the creation of customer-specific floor plan

components with a copy template.

Clinical Progress Documentation

Inpatient progress notes enable the entry of information

concerning the treatment progress of a patient. The

progress documentation

￭ provides the option of entering information in the form

of a free text note.

￭

enables the use of configurable text modules for quickentry.

￭ enables the structuring of notes by the allocation to an

occupational group or a user-defined category.

￭ supports the display of progress notes in the patient

organizer in the clinical overview.

￭ supports the display of progress notes in the charting

component using an icon.

The inpatient progress report displays the individual notes

together in chronological order. Filters enable the creation

of special views.

To include all inpatient progress notes in the overview, the

system only displays the start of each note text. A pop-in

function (web dynpro technology) enables the display of

the entire text via a mouse-click.

The new ’i.s.h.med progress documentation’ module is

available with i.s.h.med SAP 6.0 EHP 6 SP 10. The new

progress documentation can be integrated into the

’i.s.h.med ward‘, ’i.s.h.med nursing‘ and ’SAP Ambulatory

Care Management‘ modules. During the conversion from

the previously used progress documentation to the new

progress documentation (time is freely selectable) existing

data have to be migrated. The license for the new ’i.s.h.med

progress documentation‘ module (10401960) is free of

charge, providing ’i.s.h.med ward‘ is already licensed.

Physician Order

Physician orders enable quick data entry during rounds using

a simple entry dialog. Physician orders

￭ are integrated into inpatient processes via the support of

subsequent processes in the form of tasks (situation / task

lists).

￭ are integrated into the clinical work station, patient

organizer and the charting component (optional

additional i.s.h.med charting module).

￭ offer a summary of relevant data in the physician order

log.

￭

are processed in the created situation in thedocumentation work station.

The entry dialog includes, in addition to the header data, the

hit list which supports the quick entry of a physician order.

Free text entries in the text editor enable the creation of ad

hoc tasks. In the task component changes can be made

concerning the planned date of the task, person responsible,

required task, and tasks can be added or deleted. Physician

orders can be saved before release, without this generating a

situation / task.

The processing dialog is divided into three areas:￭ Patient header of the selected patient (top)

￭

List of patients (middle)

￭ List of physician orders for the selected patient (bottom)

The following actions are possible in the processing dialog:

￭

Add Patient

￭ Show / Hide Patient List

￭ Create, Edit (only “created” status), Display (physician

order log), Release (only “created status), Print, Delete

(only “created” status) Physician Order

￭

Navigate to the situation of the physician order and togglebetween outstanding and completed physician orders.

For each released physician order a situation with the

contained tasks of the physician order is assigned to the

patient. Subsequent processing is the same as in the case of

other situations in the ward documentation work station.




Prerequisites forImplementation

Modules

￭

License and installation of SAP for Healthcare

(10178662) (Patient Management, previously IS-H)

￭ License and installation of i.s.h.med basis (07600997)

IntegrationThe following optional modules can be integrated:

￭ i.s.h.med charting (10415853)

￭ i.s.h.med nursing (10415900)

￭ i.s.h.med medication (07601078)

￭ i.s.h.med progress documentation (10401960)

System-Technical Prerequisites

￭

The i.s.h.med ward module is available from i.s.h.med

SAP 6.0 EHP 4 onwards.

￭

Generally, i.s.h.med can be technically run on thehardware which is necessary for SAP Patient

Management. We recommend the scaling of this

concerning CPU performance, RAM, possible server

clusters, etc. in accordance with the foreseeable system

load (number of users, etc.).

￭

The supported operating system platforms, database

systems, etc. are the same as those for SAP ERP Release

6.0.

Other Prerequisites

￭ Services are required for productive use.



Seite 9 / 9

Due to local restrictions to sales rights and service

availability we regret that we are unable to guarantee that

all products listed in this brochure can actually be sold bySiemens throughout the world.

The information contained within this document provides

general technical descriptions of services and configuration

options which are not prerequisites in every individual

case. Availability and configuration packages can vary

from country to country. For this reason the desired

services and configuration should be determined in

individual cases upon conclusion of contract.

Siemens reserves the right to change the construction,

configuration packages, performance characteristics and

configuration options without prior notice. For up-to-dateinformation please contact your Siemens representative.

Note: Technical descriptions in this document may deviate

within a defined range of tolerance. Images always lose a

certain degree of detail in reproduction.

All patient data displayed in this document in software

screenshots or otherwise is purely fictitious. Screenshots

are created on Siemens own systems for demonstration

purposes.

All product and company names are trademarks or

registered trademarks of the corresponding companies.

www.siemens.com/ishmed

Global Siemens Headquarters

Siemens AGWittelsbacherplatz 280333 Muenchen

Germany

Global Siemens Healthcare Headquarter

Siemens AGHealthcare SectorHenkestrasse 12791052 ErlangenTelephone: +49 9131 84-0Germany

www.siemens.com/healthcare

Legal Manufacturer

Siemens AGWittelsbacherplatz 2

80333 MuenchenGermany

Local Contact Information

Siemens AGSiemens DeutschlandHealthcare SectorKarl-Heinz-Kaske-Straße 291052 ErlangenGermanyPhone +49 800 188 1885www.siemens.de/healthcare

Global Business Unit Adress

Siemens Medical Solutions USA, Inc.Health Services51 Valley Stream ParkwayMalvern, PA 19355USAwww.usa.siemens.com/healthcare

© 2013, Siemens AG