SAP Patient Management 4.

72

Planning Functionality

1
 Content

„ Concept of the Clinical Order

„ Integration of the preregistration in the clinical order
„ Structure of a preregistration
„ Design of the data entry interface
„ Header components
„ Item components
„ Call of planning functions from the preregistration
„ Customizing the Clinical Order
„ Migration

© SAP AG 2004

2
 Concept „Clinical Order“

Order Order
Initiator for: ….
Initiated by: …
Details of treatment
Internal business
partner

Laboratory
Internal recording

Organisational Admisson
Unit
Via Internet
Surgery
External
Physicians

© SAP AG 2004

3
 Concept of Clinical Order in 4.72

„ Consolidation of preregistration and service request

(both are elements of the Clinical Order in IS-H*Med)
„ Replacement of the service request
„ Concept of application components
„ Multiple preregistration items addressed to different (order) fillers
„ New dialog interface
„ New status concept
„ Status-dependent field properties of the preregistration items
„ Trace of changes
„ New concept of enhancement through clinical application
components
„ Object-oriented technical basis
Consequences in IS-H:
IS-H continues to use the term „preregistration“. The preregistration is a
specification of the clinical order which can be used to plan Outpatient visists
(appointments), as well as In-Patient admissions.

© SAP AG 2004

4
 Structure of a Preregistration

Patient header Preregistration data

ƒ Preliminary and existing ƒ initiator Predetermined
Predetermined
patient master data ƒ employee responsible
ƒ Import data from healthcare ƒ status of preregistration, etc.
smart card

Application components structured in tabcards Structure

Structureand
and
ƒ general medical data contents
contentscan
can
ƒ context
ƒ waiting list be
becustomised
customised
ƒ comment
ƒ insurance (IMG)
(IMG)
ƒ procedures

Items of Preregistration structured in tab cards

Pos. 1 Sonography
ƒ Admission Number
Numberandand
ƒ Referal contents
contentsof
of
items
itemscan
canbe
be
Pos. 2 Pre-OP by Anaesthetist customised
customised
(IMG)
(IMG)
Pos. 1 Inpatient admission
Pos. 1 Surgery

© SAP AG 2004

After redesign, a preregistration now comprises the following areas:

ƒ Header data
ƒ Patient data
ƒ General medical information
ƒ Waiting list data
ƒ Item data
ƒ Order type
ƒ Filler
ƒ Departmental responsibility
ƒ Appointment or appointment proposal
ƒ Case information

A preregistration can now have more than two preregistration items.

A nonhierarchical, item-related display is provided for the display in the preregistration view. The
preregistration header is thus not output in a separate row.

The data of the preregistration header is incorporated in the item rows. The system fills it for each item.

5
 Example: Preregistration with several positions

Header
Headerdata
data
compulsory
compulsory

Header
Headerdata
data
optional
optional

Items
Items

© SAP AG 2004

6
 Item data of the preregistration

Item data comprise information and functions relating to the processing of an

appointment during the treatment.

Cancel
Cancel
Appoint-
Appoint- Appoint-
Appoint- assignment
Order Elemental assignmentof of
Order Elemental Filler
Filler ment
ment ment
ment preregistration
item order preregistration
item ordertype
type template
template search
search to
tocase
case

Appointment
Appointment Admission
editor Admission
editor

© SAP AG 2004

Preregistration item Æ Overview row:

The corresponding overview row for the individual preregistration items has a static structure. It always
contains the following data:
ƒ Item number
ƒ Order type
ƒ Order filler
ƒ Departmental responsibility
ƒ Appointment or appointment proposal
ƒ Case information
The Appointment field displays an appointment template or alternatively, an appointment. An
appointment template is the template for planning an actual appointment. In the simplest case, an
appointment template is a desired date.

In the Case field or using the corresponding pushbutton, you can link the order item to a case or detach it
from the case.

Preregistration Æ Details:

The details of the preregistration item are strictly specified by the underlying order type. Details are, for
example, the two tab pages Admission and Referral Data.

7
 Cancellation of Preregistrations/Items

© SAP AG 2004

8
 Printing forms from the preregistration

© SAP AG 2004

The preregistration offers two alternative print variants. You can access these in the Edit menu:

Standard Form Print

You can choose Print Form → Standard Form to print an overview display of the preregistration using a
predefined SAP Smart Form. This variant contains the data of the preregistration header (patient data,
general preregistration data) as well as the overview rows of the individual preregistration items. You can
print this form on printers which are defined in the SAP environment.

Choose Form Print

You can choose Print Form → Choose Form... to print an overview display of the preregistration using,
for example, a self-defined SAP Smart Form. As before, this variant contains the data of the
preregistration header (patient data, general preregistration data) as well as the overview rows of the
individual preregistration items.

9
 Order Types

Order Type: Elemental

Vormerkung: MRI Header Data

9 nuclear magnetic resonance imaging
Item data
(NMRI)

Order Type: Profile

Preregistration:
Preregistration: planned Caesarian Header Data
9 Sonography

9 Pre-OP by Anaesthetist
Item data
9 Impatient Admission

9 Surgery

© SAP AG 2004

As a result of the preregistration redesign as a specification of the clinical order, the previous
preregistration types are depicted as order types in the preregistration master data. When you create a
new order type, you have to choose between an elemental order type and a profile type.

The elemental order type is created using components and design elements (tab pages). When a
preregistration is entered, specifying an elemental order type results in exactly one preregistration item.

The profile type is created using existing elemental order types. When a preregistration is entered,
specifying a profile type results in as many preregistration items as the number of order types contained in
profile type.

10
 Customizing the Elemental Preregistration

„ Short Name / Name

„ Filler
„ Pre-assignment of values
„ Initiator

© SAP AG 2004

11
 Call of Planning tools for outpatients/inpatients

IfIf the
thepreregistration
preregistration is
isdefined
defined for
for IfIf the
thepreregistration
preregistration isisdefined
defined
the
the movement
movement type
type “Inpatient
Inpatient
“Inpatient for
for the
the movement
movement typetype
Admission”,
Admission”, the
Admission the system
systemcalls
callsup
upthe
the “Outpatient
Outpatient Visit”,
“Outpatient Visit”,the
Visit the system
system
planning for exact days.
planning for exact days. calls up the Visit Scheduling.
calls up the Visit Scheduling.

© SAP AG 2004

12
 Preregistration Header Components

„Compulsory“components
„ Patient header
„ Preregistration data

Optional components

„ general medical data

„ waitinglist
„ insurance
„ comment
„ context
„ procedures

Design elements
„ Customer-defined tab cards
„ Display in one or two columns

© SAP AG 2004

Preregistration header

Here you can define (provisional or actual) patient information, and also general information on the
preregistration and the order placer (initiator).

Tab page header

The composition of these tab pages and their content is dynamic and dependent on the selection of the
order type at item level.

If, for example, you select a very simple order type, this defines only one component as relevant for the
entire order (for example, general medical information).

If you create a second item based on a different order type definition, this can add further tab
pages/components to the tab page header. Similar components, which originate from different items, are
only displayed once. If you cancel an item from an order with several items, and the order type upon
which this item is based is the last in the preregistration which defines a specific tab page, the system will
remove this tab page.

13
 Preregistration Item Components

Item components Design elements

„ Admission Data „ Customer definded tab cards
„ Display in one or two columns
„ Referral

© SAP AG 2004

14
 Structure (elemental)

Customizing

Application

© SAP AG 2004

15
 Structure (Profile type)

© SAP AG 2004

16
 Process Preregistrations from Clinical Workplace

Each item of a preregistration is displayed as a separate line in the clinical

workstation. The number of the preregistration forms a reference unit around
the various items of the preregistration.

Preregistration
Preregistration
with
with22items
items

Desired
Desireddate
date
marked
markedwith
withblue
blue

© SAP AG 2004

17
 Migration

Basic Data Movement Data

„ Each preregistration type is „ Existing preregistrations will be

turned respectively into: transferred into a clinical order
‹ One admission type (in- with one or two items:
patients) ‹ Admission item (admission
‹ One treatment type (out- date)
patients) ‹ Treatment item (outpatient
„ Existing preregistrations types appointment)
from releases <4.72 will be kept „ Interdependent relationships will
in the system for reference
be retained
purposes, however they cannot
be used anymore. „ Automatically with realease
upgrade through XPRA
„ Name of design elements =
name / description of tab cards
„ Names / descriptions will be
ported from the preregistration
types into the clinical order
types
„ Automatically with realease
upgrade through XPRA

© SAP AG 2004

18
 Summary

„ With 4.72 the Clinical Order is being introduced as a merger of the

preregistration and the service request.
„ There is a new user interface.
„ The display can be determined via components that can be arranged
customer-specifically on tab cards.
„ Preregistrations can now contain several positions.
„ The system supports the data migration.

© SAP AG 2004

19