SAP Patient Management 4.

72

Clinical Process Builder

1
 Content

„ Concept of framework architecture

„ Management of variants
„ Overview of subscreens
„ Reference level of variants and subscreens
„ Creation of customer-specific subscreens
„ Access from various transactions
„ Direct call of CPB
„ Call from other transactions
„ Consequences on system administration

© SAP AG 2004

2
 From EnjoySAP-Admission to the Clinical Process Builder

Before
BeforeRelease
Release4.72
4.72 From
FromRelease
Release4.72
4.72

Transaction NV2000 Transaction NV2000

EnjoySAP-Admission Clinical Process Builder

Impatient Admission
Change of terminology Framework
Outpatient Admission architecture for the
creating, editing
Surgery
and displaying of
Transfer the patient-, case-
and movement-
„Old“ Transactions (e.g. current Discharge
related Data in SAP
admission not using NV2000) Case-Related Materials Patient
will still be available under Consumption
Management
Release 4.72 (provided user Patient Master Data
parameter NV2000 is in „OFF“
mode). However, the change to Further in Planning
using NV2000 is recommended.

© SAP AG 2004

As of this release, EnjoySAP Admission has become the Clinical Process Builder.

This provides a standard framework architecture for creating, editing and displaying the patient-, case-,
and movement-related data in SAP Patient Management.

From the familiar transactions, the user is directed by the system to the initial screen of the Clinical
Process Builder, where he or she can select the appropriate variant for the processing at hand.
Preconfigured SAP variants are supplied that can be supplemented with customer-defined variants.

3
 Variants in the Clinical Process Builder

The user selects the variant preferred for the particular function.

Customer-
Customer-
specific
specificvariants
variants

Pre-defined
Pre-defined
SAP-Variants
SAP-Variants

You have the following options:

„ Use of SAP-Variants
These variants can be
„ An administrator can define customer-specific variants assigned to the user /
meeting the specific needs of the different users / user role by the administrator.
roles in the hospital.

© SAP AG 2004

4
 Administration of Variants

As already before
the 4.72 release,
the administrator
creates the
variants by
maintaining the
attributes and by
assigning
subscreens and
dialog elements.

This
Thisis
iswhere
wherethe
the The
Thepool
poolof
ofSAP
SAP You
Youcancanalso
alsocreate
create
administrator
administratorassigns
assigns subscreens
subscreens availablehas
available has customer-specific
subscreens customer-specific
subscreensand
anddialog
dialog been
beenenhanced
enhancedwith
with subscreens.
elements. release subscreens.
elements. release4.72.
4.72.

© SAP AG 2004

5
 New/ changed Subscreens

New / changed Subscreen Refer to

Movement data Page 8 (movement-related variants)
Appointment data Unit 2: Outpatient Management
Clinical data relating to visit (if IS-H*MED is used)

Diagnoses Unit 7: Medical documentation

Procedures Unit 7: Medical documentation
DRG data Unit 7: Medical documentation
Case-related materials consumption Unit 6: Integration to MM
Insurance Unit 4: Insurance relationships
Insurance proposal Unit 4: Insurance relationships
Readmissions Unit 8: DRG Billing
Readmission – total case Unit 8: DRG Billing
Sample data Page 9 (Copy Template)

© SAP AG 2004

6
 Reference Levels of Subscreens and Variants

„ Depending on the properties of the data

they contain, subscreens can be
patient-, case- or movement-related.

„ These properties of the subscreens are

passed on to the variants in which they
are incorporated.

„ Certain combinations of properties can lead to different system behaviour. An overview

of these combinations and the resulting system behaviour can be found in the 4.72
Release Information, chapter EnjoySAP Admission Becomes the Clinical Process
Builder.

InInthis Patient-
Patient-related
relatedSubscreen
thisspecial
specialconstellation
constellation Subscreen
the
the systemadds
system addsthe
therelation
relation
toto the case for thevariant.
the case for the variant. Movement-related
Movement-relatedSubscreen
Subscreen

Movement-related
Movement-relatedSubscreen
Subscreen

© SAP AG 2004

7
 Movement-related Variants

© SAP AG 2004

Due to the characteristics of the variant (In-/ out-patient admission, Transfer, Discharge) the subscreen
“Movement Data” can react differently in accordance with the type of movement being created /
processed.

The indicators Standard/ Short/ Emergency Admission can only be used for variants relating to inpatient
admission or outpatient visit.

8
 Copy Template for customer-specific Subscreens (1/2)

„ For the creation of customer-specific

subscreens the function group NTPLNV2000
can be used as a copy template.

„ How to proceed: Copy this function group into

your own one and adapt the processing logic
and dialog interface to your requirements.

Subscreen
Subscreentemplate
templateininthe
theClinical
ClinicalProcess
ProcessBuilder
Builder

© SAP AG 2004

The function group contains the function modules that are entered in the corresponding fields when a dialog
element for the Clinical Process Builder is created or changed:

ƒ Initialization - ISH_NV2000_TEMPLATE_SUBSCREEN: Call at each PBO (= process before

output) prior to CALL SUBSCREEN

ƒ Transfer OK-Code - ISH_NV2000_TEMPLATE_SUB_INPUT: Call at each PAI (= process after

input) Prior to CALL SUBSCREEN

ƒ Set Cursor - ISH_NV2000_TEMPLATE_SUB_OUTPUT: Call at each PAI after CALL

SUBSCREEN

ƒ Check Changes - ISH_NV2000_TEMPLATE_SUB_CHNGES:Call when transaction exited (e.g. exit)

ƒ Save - ISH_NV2000_TEMPLATE_SUB_SAVE: Call when data saved

ƒ This function module also contains the update module for the database table NTPLNV2000.

9
 Copy Template for customer-specific Subscreens (2/2)

„ For the creation of customer-specific

subscreens the function group NTPLNV2000
can be used as a copy template.

„ How to proceed: Copy this function group into

your own one and adapt the processing logic
and dialog interface to your requirements.

Subscreen
Subscreentemplate
templateininthe
theClinical
ClinicalProcess
ProcessBuilder
Builder

© SAP AG 2004

ƒ Other participating objects are the database table NTPLNV2000 and the structure RNDNTPLNV2000
that contains the dialog fields. You must replace these by your own tables and structures.

ƒ Since the dialog screen contains the user-defined fields of the patient master, you can very easily active
them for maintenance within the variant by copying the function group and simply removing the
processing for the database table NTPLNV2000. You're then left with the maintenance of the user-
defined fields of the patient master.

You can get an idea of the functionality by entering the function modules in a customer-specific dialog element
of the Clinical Process Builder and assigning this element to a variant. Please keep in mind that some of the
fields on the dialog screen are stored in the user-defined fields of the patient master (NPAT-USER1 to NPAT-
USER6) and, consequently, productive IS-H data may be affected.

10
 Call of Transactions

Prerequisites regarding user parameter:

The
Thesystems
systemstakes
takesthe
theuser
userinto
into
The
Theuser
userchooses
choosesaafamiliar
familiar the
the initial screen of the CPBwith
initial screen of the CPB with
transaction.
transaction. the
therespective
respectivestandard
standardvariant.
variant.

© SAP AG 2004

11
 Overview of Admission Types changed

Process Transaction Implementation in 4.72

Standard NV01-NV03, Call of transactions leads to

Admission NV41-NV43 “SAP Standard variant”

NV04-NV06, Call of transactions leads to

Quick Admission
NV44-NV46 “SAP Quick Admission”

Emergency NV07-NV09 Call of transactions leads to

Admission NV47-NV49 “SAP Emergency Admission”

Call of transactions leads to “SAP

Maintain NP11-NP13
Standard variant”, now it is also
Admission/ Visit NP41-NP43
possible to create new patients

Call of transactions leads to “SAP

Create Surgery NP37-NP39
Surgery” (also see Chapter 8)

© SAP AG 2004

12
 Overview of remaining transactions modified

Process Transaction Implementation in 4.72

Patient Master Call of transactions leads to

NP01-NP03
Data “SAP Patient Master Data”

Call of transactions leads to

Transfer NV11-NV13
“SAP Transfer”

Call of transactions leads to

Discharge NP97-NP99
“SAP Discharge”

NAPX1- Call of transactions leads to

Readmission
NAPX2 “SAP Readmission”

Case-Related Call of transactions leads to “SAP

NMMC1-
Material Case-Related Material
NMMC2
Consumption Consumption”(also see chapter 11)

© SAP AG 2004

13
 Call of the Clinical Process Builders

p aa Can lead to
standard variants
o Manual selection of
variant

X Call CPB (without

pre-selecting
Process)

p b Can lead to customer-

specific variants

© SAP AG 2004

14
 Call from other Transactions

Via call of the

respective
transaction code…

… and via the IMG

assignment table
the variant is
determined …

… which is
displayed to the
user.

© SAP AG 2004

15
 Summary

„ The EnjoySAP – admission is enhanced into the Clinical Process

Builder .
„ The CPB is the new framework architecture for the editing and
updating patient data.
„ The CPB is also using variants and subscreens.
„ Variants and subscreens have reference levels (movement, case,
patient) that communicate with one another.
„ It is also possible to create customer-specific subscreens.
„ The call of the „old“ transactions is still possible.
„ Some consequences on the system administration need to be
considered.

© SAP AG 2004

16