01.saphelp Erp60 SP en 1b Cb0d50aa85d047e10000000a44176f Content-Ish-BasicData

BASIC DATA
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/1b/cb0d50aa85d047e10000000a44176f/content.htm
Created on March 16, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure.
Subtopics from other structures are not included.
The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You
can manually download the missing subtopics.
2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior
notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Page 1 of 75
TABLE OF CONTENT
1 Basic Data
1.1 Hospital Structure
1.1.1 Input Help for Organizational Hierarchy
1.1.2 Maintaining Personal Value Help
1.1.3 Organizational Structure
1.1.3.1 Creation of Organizational Structure
1.1.3.2 Organizational Unit
1.1.3.2.1 Organizational Unit: Name and Address Data
1.1.3.2.2 Organizational Unit: Blocking Indicator
1.1.3.2.3 Organizational Unit: Validity Dates
1.1.3.2.4 Organizational Unit: Specialty Keys
1.1.3.2.5 Organizational Unit: Departmental Per Diem
1.1.3.2.6 Example: Departmental Per Diem of Departmental and Nursing OU
1.1.3.2.7 Organizational Unit: Indicators Relevant to Processing
1.1.3.2.8 Organizational Unit: Division (CH)
1.1.3.2.9 Organizational Unit: Assign Physician (AT)
1.1.3.2.10 Identification Key for Organizational Units
1.1.3.2.11 Creating Organizational Units
1.1.3.2.12 Maintain Organizational Units: Initial Screen
1.1.3.2.13 Changing Organizational Units
1.1.3.2.14 Flagging Organizational Units for Deletion
1.1.3.2.15 Canceling the Deletion Flag for Organizational Units
1.1.3.2.16 Blocking/Unblocking Organizational Units
1.1.3.3 Organizational Hierarchy
1.1.3.3.1 Example: Organizational Hierarchy
1.1.3.3.2 Maintain the Organizational Hierarchy
1.1.3.3.3 Displaying the Hierarchy Overview Graphic
1.1.3.3.4 Interdepartmental Relationships
1.1.3.3.5 Maintain Interdepartmental Relationships
1.1.3.4 Maintaining Organizational Unit-to-Building Unit Assignments
1.1.3.5 Maintaining Statistical Bed Figures
1.1.3.6 Release Organizational Structure
1.1.3.7 Transport Organizational Units
1.1.3.7.1 Transporting Organizational Units
1.1.4 Building Structure
1.1.4.1 Creation of Building Structure
1.1.4.2 Building Units
1.1.4.2.1 Building Unit: Name Data
1.1.4.2.2 Building Unit: Validity Dates
1.1.4.2.3 Building Unit: Coordinate Data
1.1.4.2.4 Assignment of Identification Keys for Building Units
1.1.4.2.5 Create Building Units
1.1.4.2.6 Creating Building Units: Single Entry
1.1.4.2.7 Maintain Building Units: Initial Screen
1.1.4.2.8 Changing Building Units: Collective Entry
1.1.4.2.9 Create Building Units: Collective Entry Screen
1.1.4.2.10 Change Building Units
1.1.4.2.11 Changing Building Units: Single Entry
1.1.4.2.13 Flagging Building Units for Deletion
1.1.4.2.14 Canceling the Deletion Flag for Building Units
1.1.4.2.15 Blocking/Unblocking Building Units
1.1.4.3 Building Hierarchy
1.1.4.3.1 Maintaining the Building Hierarchy
1.1.4.3.2 Displaying the Building Hierarchy Overview
1.1.4.3.3 Planning Characteristics of Building Units
1.1.4.3.3.1 Maintain Planning Characteristics
1.1.4.3.4 Facilities of Building Units
1.1.4.3.4.1 Maintaining Facilities of a Building Unit
1.1.4.3.5 Release of Building Structure
1.1.4.3.5.1 Releasing the Building Structure
1.1.4.3.6 Transport Building Units
1.1.4.3.6.1 Transporting Building Units
1.1.4.4 Maintain Building Units for Care Unit Graphic
1.1.4.4.1 Planning the Graphical Representation of the Care Unit Structure
1.1.4.4.2 Example of Care Unit Aligned with SAP Coordinate System
1.1.4.4.3 Rooms in the Care Unit Overview Graphic
1.1.4.4.4 Corridors in the Care Unit Overview Graphic
1.1.4.4.5 Bed Locations in the Care Unit Overview Graphic
1.1.4.4.6 Doors in the Care Unit Overview Graphic
1.1.4.4.6.1 Define the Location of Room and Corridor Doors
1.1.4.4.6.2 Examples of Vertical and Horizontal Doors
1.1.4.4.6.3 Maintaining Doors
1.2 Business Partner
1.2.1 BAPIs for Business Partners
1.2.2 Business Partner Concept
1.2.3 Business Partner Identification Key
1.2.4 Business Partner Search
1.2.5 Business Partner List
1.2.6 Creation of Business Partners: Strategies
PUBLIC
Page 2 of 75
1.2.6.1 General Business Partner Data

1.2.6.2 Creating General Business Partners
1.2.6.3 General Business Partner: Initial Screen
1.2.6.4 General Business Partner: Entry Screen
1.2.7 Blocking Business Partners
1.2.8 Unblocking Business Partners
1.2.9 Displaying the Blocking Interval of the Business Partner
1.2.10 Deletion of Insurance Providers
1.2.10.1 Flagging Business Partners for Deletion
1.2.10.2 Displaying Business Partners Flagged for Deletion
1.2.10.3 Cancelling the Deletion Flag for Business Partners
1.2.10.4 Deleting Insurance Providers Flagged for Deletion
1.2.10.5 Deletion of Insurance Providers: Selection Criteria
1.2.11 Display of Business Partner Administrative Data
1.2.11.1 Displaying the Administrative Data of General Business Partners
1.2.12 Business Partner Functions
1.2.12.1 Displaying the Administrative Data of Business Partner Functions
1.2.12.2 Creating Business Partner Functions
1.2.12.3 Employer (Business Partner Function)
1.2.12.4 Insurance Provider (Business Partner Function)
1.2.12.4.1 Insurance Provider-Specific Master Data
1.2.12.4.2 Insurance Provider: Insurance Provider Type
1.2.12.4.3 Ins. Prov.: Relevant Fields for Importing Healthcare Smart Card
1.2.12.4.4 Example: Head Office and Branch Determination at Healthcare Smar
1.2.12.4.5 Insurance Provider: Head Office
1.2.12.4.6 Insurance Provider: Health Insurer Search Name
1.2.12.4.7 Insurance Provider: Control Parameters
1.2.12.4.8 Find Insurance Providers Without Customers
1.2.12.4.9 Determine Insurance Providers Without Customers
1.2.12.5 IS-H Customer (Business Partner Function)
1.2.12.5.1 Customer-Specific Master Data
1.2.12.5.2 Creating IS-H Customers
1.2.12.5.3 Creating Customers in IS-H and FI
1.2.12.5.4 Sensitive Fields
1.2.12.5.5 Creating IS-H Customers and Assigning FI Customers
1.2.12.5.6 Assigning FI Customers to IS-H Customers
1.2.12.5.7 Changing Customers
1.2.12.5.8 Create Bank Details
1.2.12.5.9 Edit Bank Details List
1.2.12.5.10 Determination of IS-H Customers Without FI Customers
1.2.12.6 Hospital (Business Partner Function)
1.2.12.6.1 Hospital in Insurance Provider Role
1.2.12.7 Employee/Physician (Business Partner Function)
1.2.12.8 External Ordering Party (Business Partner Function) [CH]
1.2.12.9 Fee Recipient (Business Partner Function) [CH]
1.2.12.10 Assign Contract Partner Number (AT)
1.3 Service Master Data
1.3.1 Service Master
1.3.1.1 Creating the Service Master
1.3.1.2 Service Master: Initial Screen
1.3.1.3 Service Master: Service Texts
1.3.1.4 Service Master: Columns
1.3.1.5 Service Master: Classification
1.3.1.6 Service Master: Other
1.3.1.7 Service Master: Medical Indicators
1.3.1.8 Service Master: Communication
1.3.1.9 Service Master: FR/PS (Germany)
1.3.1.9.1 Important Master Data for FR/PS (Germany)
1.3.1.9.2 Maintaining Add. Data for FR/PS (Germany)
1.3.1.9.3 Add. Data: Displaying and Delimiting Validity Intervals (Germany
1.3.1.10 Service Master: Additional Data (Switzerland)
1.3.1.10.1 Maintaining Add. Data for Service Catalogs and Fees (Switzerland
1.3.1.10.2 Maintaining Additional Data for TARMED (Switzerland)
1.3.1.10.2.1 Maintain Swiss Service Master (TARMED) Using Tables
1.3.1.10.2.2 Import TARMED Service Master Data (Switzerland)
1.3.1.10.3 Import Tariff Types (Switzerland)
1.3.1.10.4 Alternative Service Code (Switzerland)
1.3.1.11 Service Master: Additional Data (Austria)
1.3.1.12 Maintaining Planned Values for Services
1.3.1.13 Changing the Service Master
PUBLIC
Page 3 of 75
1 Basic Data
Important master data on which Patient Management and Patient Accounting are based.
Features
Master data includes:
Organizational units
Building units
Business partner data
Service master data
Catalogs
Clinical work station
1.1 Hospital Structure

Modeling of the organizational structure and building structure of a hospital in hierarchical form.
Integration
You must create the organizational structure of the hospital. You only have to create the building structure of the hospital if you schedule
building units (rooms and beds) in Care Unit Management or Outpatient Clinic Management and want to assign patients to rooms and
beds. You also must have created the building structure to be able to use the care unit graphic.
Features
You model the structure of your hospital in the IS-H system using organizational and building structures.
For Information On
See
Organizational structure
Organizational Structure
Creation of Organizational Structure: Procedure in Overview
Organizational Units
Organizational Hierarchy
Inter-Departmental Relationships
Statistical Bed Figures
Release of Organizational Structure
Transport Organizational Units
Building structure
Introduction to the Building Structure

Creation of Building Structure: Procedure in Overview
Building Units
Building Hierarchy
Maintain Organizational Unit-to-Building Unit Assignments
Planning Characteristics of Building Units
Facilities of Building Units
Maintenance of Building Units for Care Unit Overview Graphic
Release of Building Structure
Transport Building Units
1.1.1 Input Help for Organizational Hierarchy

The input help for the organizational hierarchy (building and organizational units) lets you take advantage of the personal value list.
Note
To enable personalization to be configured centrally, you can copy the personal settings for the organizational hierarchy input help
from one user to another using program RNUHLP00. For more information about this, see the program documentation.
PUBLIC
Page 4 of 75
Features
Personal Value List
You can custom tailor the display of the organizational hierarchy to satisfy your needs. This involves maintaining a personal value list
that is then displayed by default when you call the input help. Additional fields are available to you for outputting information (for
example, category, name and telephone number of the organizational/building unit).
Note
You should use additional fields sparingly, otherwise entries can run into the next line.
Activities
Maintain Personal Value List
You can maintain the personal value list either using (-) or using the personalization settings (Ctrl + F4). When you insert an
organizational unit in the personal value list, the system always includes the complete path of the hierarchy as of the first or second
level beneath the institution.
If you have maintained personal values, the personal list is always displayed directly when you call the input help. If need be, you can
switch to the complete hierarchy by choosing the globe symbol.
Note
If you have maintained personal values for the input help, the cursor is only positioned on an organizational unit already entered in
the list if the corresponding path is found in the personal values.
You can expand all nodes of the hierarchy in one go.
Note
You can accelerate the generation of the hierarchy using the new institution-specific, time-independent system parameter
OE_LOAD. Read the documentation relating to this system parameter in the IS-H Implementation Guide by choosing Basic
Settings System Parameters Maintain Institution-Specific, Time-Independent Parameters .
If system parameter OE_LOAD is set to 'L' (load hierarchy only up to displayed level), the Display All Lines pushbutton is not
available.
1.1.2 Maintaining Personal Value Help

Procedure
To maintain a personal value help, proceed as follows:
1. Position your cursor on the input field for an organizational or building unit (when creating an admission, for example), and then
choose the value help.
The Input Help:<> dialog box appears.
2. To insert a path from the organizational hierarchy in your personal value help, position the cursor on the desired organizational unit of
the hierarchy path, and choose
(Add to Favorites).
The hierarchy path is inserted in your personal value list.
Alternative Procedure
You can also proceed as follows from the Input Help:<> dialog box:
1. Press STRG + F4, or choose Personalize in the context menu (displayed by clicking the right mouse button).
2. The Personalize F4 Help for User <USER-ID> dialog box appears. Your cursor is positioned on the Value selection tab page.
Any personal paths you have already chosen are displayed in the left section of this tab page. All remaining non-chosen
organizational hierarchy paths are displayed in the right section.
3. You can insert selected paths in your personal value selection, or remove them using the
(-) and
(-) pushbuttons.
Note
You can exclude particular organizational categories from the display. Specify the organizational categories that are not to be
displayed under Do not display organizational categories on the Settings tab page.
Note
You can stipulate that outpatient clinics should no longer be included in your personal value list for OUs.
PUBLIC
Page 5 of 75
You can stipulate that care units should no longer be included in your personal value list for OUs.
1.1.3 Organizational Structure

You model the organizational structure of your hospital using organizational units (OUs) that you bring into relation with one another.
Whenever you create an organizational unit, you assign an organizational category to it. The organizational category determines
which organizational units can be brought into relation with one another.
You can define organizational categories of your choosing in Customizing for IS-H. For more information about this, see the section
entitled Define Organizational Unit Categories of the IS-H Implementation Guide.
Example
Examples of such categories are:
Clinic
Department
Care Unit
Admitting Department
Outpatient clinic
You create an organizational unit with the appropriate organizational category for each organizational unit in your institution. The
organizational category determines which attributes you can store for an organizational unit.
Example
Examples of such attributes are:
Outpatient treatment
Departmental assignment
Nursing assignment
Supports interdepartmental bed assignment
The organizational structure you define in the IS-H System is used in the following areas:
Area
Use
Patient assignment
The attributes of an OU determine whether it can be used as a
departmental, nursing and/or treatment OU in the patient
assignment.
Service entry/billing
In the master data of an OU, you can specify the service that
should be automatically entered and billed for a patients stay in
this OU. The organizational structure determines whether you can
store different services on different levels of the organizational
hierarchy.
Statistics
Statistics evaluate specific data in relation to organizational units,

for example the patient census, and total the determined values
according to the organizational hierarchy.
Service transfer into Controlling
To be able to transfer services into Controlling, you must first

have assigned organizational units to cost centers. You should,
therefore, also include service facilities such as laboratories and
X-ray departments in the organizational hierarchy, so as to be
able to post to the corresponding cost centers when carrying out
internal activity allocation.
Prior to creating an organizational structure, you should analyze which results you require in the respective areas and create the
organizational structure accordingly.
1.1.3.1 Creation of Organizational Structure

To model the organizational structures of your institution in the system, you create an organizational structure. To do this, work through
the following activities in the order specified.
Process
1.
Creating Organizational Units
PUBLIC
Page 6 of 75
Maintain the Organizational Hierarchy

Maintain Interdepartmental Relationships
4. Maintain Organizational Unit-to-Building Unit Assignments
5. Release Organizational Structure
2.
3.
1.1.3.2 Organizational Unit

Any organizational unit within a hospital. For example, you can characterize a care unit as a nursing organizational unit or a department
as a departmental organizational unit.
On Tab Page
Label
/Description
You Store the Following Data...

Name Data
Blocking indicator
Validity dates
Specialty, Indic.
Specialty Key
Departmental per Diem
Indicators Relevant for Assignment/Occupancy
Other Data
Other Data
Address
Address
Gen. Switzerland
Division (country version Switzerland only)
More Information
Identification Key for Organizational Units
Creating Organizational Units
Changing Organizational Units
Blocking/Unblocking Organizational Units
Flagging Organizational Units for Deletion
1.1.3.2.1 Organizational Unit: Name and Address Data

You can store the following name data for an organizational unit (OU). You should maintain this data fully, since it is output at different
places in the system.
OU Name
You specify the long name of the OU here.
OU Short Text
You enter the short text of the organizational unit in this field. The short text is output on many screens, for example in the case list,
care unit overview and the organizational unit hierarchy.
Note
To ensure the short text is maintained for each OU, you should define the corresponding field as a required-entry field in
Customizing. For more information about this, see the Section Maintain Screen Modification of the IS-H Implementation Guide.
OU Identifier
The input of an identifier is mandatory. Use mnemonic identifiers. The identifier of an OU must be unique in relation to the OUs above it
in the organizational hierarchy.
To list the identifiers already used, choose Extras Existing Identifier List .
Note
The identifiers are not supported in the Clinical Process Builder.
Activities
Enter the name data on the Description tab page.
Enter the address of the OU on the Address tab page.
PUBLIC
Page 7 of 75
1.1.3.2.2 Organizational Unit: Blocking Indicator

If you want to prevent an organizational unit (OU) from being used (in the patient assignment, for example), you can block this OU. You
do this by setting the blocking indicator in the OU master data..
If the blocking indicator is set, the OU is blocked for the duration of the validity period.
If an OU is only temporarily unavailable, due to construction work, for instance, you have to set the blocking indicator and deselect it as
soon as the OU can be used again.
Activities
You can select or deselect the blocking indicator on the Description tab page. For the exact procedure, see Blocking/Unblocking
Organizational Units.
1.1.3.2.3 Organizational Unit: Validity Dates

You create organizational units (OU) with a specific validity. . You cannot use an OU outside of this validity period. In other words, you
cannot assign movements or other OUs within the organizational structure to OUs outside of their specified validity periods.
Note
If you want to transfer legacy data from a previous system, you have to set the validity start date of the OUs in such a way that the
OUs are valid when the movements of the transferred cases take place.
If you want to shut down an OU, you should delimit the validity of the OU accordingly and set the blocking indicator.
Activities
You enter the validity dates on the Description tab page.
1.1.3.2.4 Organizational Unit: Specialty Keys

You can classify organizational units (OUs) in relation to specialty. This assignment is the basis for displaying the figures of governmentmandated statistics by specialty. Consequently, you should assign departments and clinics to a specialty.
If you cannot assign a clinic to exactly one specialty, do not make any assignment. In this case, the system displays the figures
calculated for the clinic under No Specialty Assigned in the statistics.
Prerequisites
In Customizing for IS-H, you specify according to which statutory regulations you assign OUs to specialties. For more information about
this, see the sections entitled Define Specialty Categories, Code Specialties and Maintain Specialty Hierarchy in the IS-H
Implementation Guide.
The following possibilities exist:
Statutory regulations Germany
Specialties pursuant to the Federal Regulation for Hospitals 1995
Specialties pursuant to the Federal Regulation for Hospitals 1985
Specialties pursuant to Statistical Regulatory Requirements
Specialties pursuant to the Nursing Staff Regulation
Statutory regulations Austria
Specialties pursuant to KRAZAF
Regulations Netherlands
Specialties pursuant to POLIS
Additionally, you can classify OUs according to specialties of your choosing.
Activities
You assign specialties to OUs on the Specialty, indic. tab page.
PUBLIC
Page 8 of 75
1.1.3.2.5 Organizational Unit: Departmental Per Diem

In the organizational unit (OU) master data, you can store a service (departmental per diem) which the system is to automatically
generate for a case if the patient is assigned to this OU.
Features
The system proceeds as follows:
1. It first generates the service that is stored in the master data of the OU to which a case is assigned on a nursing basis.
2. If a service is not stored here, the system generates the service of the OU to which a case is assigned on a departmental basis.
3. If a service is not stored here, the system does not generate a service.
Service by Departmental OU
In Germany, you normally bill for departmental per diem charges that are valid for all of the OUs of a department. In such cases, it is
useful to store the departmental per diem in the master data of the departmental OU. You do not enter a service in the master data of
the nursing OUs.
Service by Nursing OU
Should certain departmental per diem charges only be billed for for stays on particular nursing organizational units of a department, you
can specify this in the master data of the nursing OU. The system then enters the departmental per diem of the nursing OU rather than
that of the departmental OU.
Caution
If you have stored a separate departmental per diem in the master data of a nursing OU and other departments are allowed to
assign patients to beds on this OU (inter-departmental bed assignment authority), the system always enters, in relation to a case, the
departmental per diem of the nursing OU, irrespective of the OU to which the case is assigned on a departmental basis. This can
result in unwelcome results as regards inter-departmental bed assignment.
An example illustrates the procedure described.
Different Services Within a Departmental OU
In certain cases, you do not bill for the same departmental per diem for all patients on a nursing OU. This can be true, for example, if
external physician services are performed for a number of patients within the nursing OU or a number of patients are assigned to
mobile intensive care units.
To be able to model and automatically generate alternative departmental per diem charges for these patients in the system, it is
recommended to proceed as follows (the abbreviations in brackets refer to example 1 below):
You have defined a nursing OU (N11) below the departmental OU (D11) in the organizational hierarchy and assigned departmental per
diem 11 to this nursing OU. Create another nursing OU (N1A) that is also below the departmental OU in the organizational hierarchy and
assign the alternative departmental per diem (A) to this nursing OU. You then assign patients for whom you want to charge this
alternative departmental per diem to this additional OU (N1A).
Example 1
Different Services Within a Nursing OU

If you want to be able to model and automatically generate alternative departmental per diem charges for patients in the system, you
can also proceed as follows (the abbreviations in brackets refer to example 2 below):
You create an additional auxiliary organizational unit (D1A). You store the alternative departmental per diem in the master data of this
OU. You then assign patients for whom you want to charge this service to this OU on a departmental basis.
To ensure that statistics (for example midnight census statistics) are not distorted, you have to subordinate the auxiliary organizational
unitto the actual departmental OU in the organizational hierarchy. You subordinate the nursing OU to the auxiliary organizational unit.
PUBLIC
Page 9 of 75
Example 2
Activities
You can store the departmental per diem for an OU on the Specialty, Indic. tab page.
1.1.3.2.6 Example: Departmental Per Diem of Departmental

and Nursing OU
The example below illustrates two departmental organizational units (OUs), each of which is assigned a specific departmental per diem.
An alternative departmental per diem is assigned only to the surgery intensive care unit on the subordinate nursing organizational unit
level.
The urology department may assign patients to beds on care unit 2 and on the surgery intensive care unit.
The following table shows patient assignments and the service entered automatically on the basis of the assignment:
Departmental OU
Nursing OU
Service Entered
Surgery
Surgery unit 1
SRGFR
Surgery
Surgery unit 2
SRGU2FR
Surgery
Surgery intensive care
INTFR
Urology
Urology unit 1
UROFR
Urology
Urology unit 2
UROFR
Urology
Surgery intensive care
INTFR
Urology
Surgery unit 2
SRGU2FR
1.1.3.2.7 Organizational Unit: Indicators Relevant to

Processing
You can set specific indicators in the organizational unit (OU) master data to specify the attributes of the OU. The attributes of the OU
specify, on the one hand, how you can use the OU in different functions. These specifications are also used by the system to control
specific processes in relation to the attributes of the OU.
Features
The indicators listed below are available to you. You can obtain comprehensive information about each indicator via the F1 help. The
following documentation considers only specific aspects of using the indicators in the system.
Indicators Relevant for Assignment/Occupancy
PUBLIC
Page 10 of 75
Departmental Assignment
Nursing assignment
Outpatient visit
Inter-departmental assignment authority
Inter-departmental OU
Intensive care treatment
OUs for which this checkbox is flagged are intensive care units. These can be nursing OUs and departmental OUs.
The system uses this indicator in the following functions (Germany):
In evaluations of hospital statistical regulatory requirements
In the charge check on cases with flat rates per case which have both a maximum length of stay of the flat rate per case and a
maximum length of stay of the intensive care stay.
In the maintenance of nursing acuities pursuant to the Nursing Staff Regulation.
Note
The intensive care treatment indicator is not taken into account in statistics (with the exception of statistics pursuant to hospital
statistical regulatory requirements). OUs are considered as intensive care units only if they are assigned to a specialty for which
the intensive care indicator is set in Customizing for IS-H. For more information about this, see the Section Code Specialties of the
IS-H Implementation Guide and the FI help for the intensive care treatment indicator (I field) in the corresponding Customizing
table.
Other Data
Admitting Department
Within admission data you can specify the facility that admits the patient. You can only specify OUs for which this indicator is set.
Medical record archive
In Medical Record Management, you can assign a medical record to the archive in which the medical record is kept. A medical record
archive can only be an organizational unit for which you have set this indicator.
Pediatric indicator
You set this indicator for departmental and nursing OUs of pediatrics.
When maintaining nursing acuities pursuant to the Nursing Staff Regulation (Germany), you classify cases that are assigned to an OU
with the pediatric indicator using the nursing acuities of infant and children care.
Exclusion from nursing acuity classification
You set this indicator for OUs that are excluded from the regulatory nursing acuity classification (Germany). These include dialysis
units and psychiatric units.
Data protection
If the data protection indicator is set for an OU, the system displays movements on this OU in the case list only if you have the
corresponding display authorization.
Care Unit Storage Location
If you use the case-related goods issue from care unit storage location function, you must specify a plant and a storage location that
are assigned to the care unit storage facility.
Calendar
In this field, you can specify the calendar that is valid for the OU for defining the workdays of the OU. For more information, see the F1
help.
In Customizing for IS-H, you stipulate, in relation to the organizational category, which of these indicators should be maintainable for OUs
of a certain category. For more information about this, see the section entitled Define Organizational Unit Categories in the IS-H
Activities
You set the indicators relative to assignment/occupancy on the Specialty, Indic. tab page.
You can make further entries on the Other Data tab page.
1.1.3.2.8 Organizational Unit: Division (CH)

This documentation is only relevant for the country version Switzerland and is not available in English.
1.1.3.2.9 Organizational Unit: Assign Physician (AT)

This documentation is only relevant for the country version Austria and is not available in English.
PUBLIC
Page 11 of 75
1.1.3.2.10 Identification Key for Organizational Units

An organizational unit (OU) is defined by means of a unique identification key.
The identification key of an OU can be assigned by the system (internal number assignment), or you can assign it yourself (external
number assignment). In Customizing for IS-H, you can specify whether one of these two number assignment methods should be
excluded. In Customizing, you can also define the number ranges authorized for internal and external number assignment.
Note
If you assign external identification keys, it is possible to use mnemonic keys (e.g. unit07 for care unit 7). Note, however, that once
assigned, the identification key of an OU cannot be changed. For instance, should your hospital be restructured, the mnemonic keys
of the OUs may no longer match the new structure. You should therefore avoid using mnemonic keys.
The OU identification keys must be unique within a client. The system ensures that unique identification keys are always assigned. With
internal number assignment, the system always selects the next number from the internal number range. With external number
assignment, the system prevents a number, which is already assigned, from being assigned again.
Note
If you have defined several institutions in one client and are using external number assignment, you can specify a prefix for each
institution which the system places at the start of the identification key of the institutions. This enables you to designate the
organizational units which belong to the organizational structure of an institution.
1.1.3.2.11 Creating Organizational Units

You create a master record for each organizational unit (clinics, departments, care units, etc.). You can create organizational units
(OUs) with or without a template. On the initial screen of the transaction, you specify an existing organizational unit of the required
category as the template OU. If you create an organizational unit with a reference, the system transfers almost all the data of the
template OU as default values into the new master record. The following data is not transferred:
Higher-level OU
OU Identifier
Release Indicator
The system automatically sets the release indicator when you release the organizational structure.
Procedure
Choose Hospital Basic Data Administration Hospital Structure Organizational Structure Organizational Unit Create on the
SAP Easy Access screen.
The Create Organizational Unit: Initial Screen appears.
2. Enter the data as required on the initial screen, and then choose
Create (Create Organizational Unit).
The Create Organizational Unit: Administrative Data screen appears.
3. Maintain the data on the appropriate tab pages. These are named in the respective section:
Organizational Unit: Name and Address Data
Organizational Unit: Departmental Per Diem
Organizational Unit: Specialty Keys
Organizational Unit: Indicators Relevant to Processing
Organizational Unit: Validity Dates
Organizational Unit: Blocking Indicator
You can maintain the organizational hierarchy when creating an organizational unit by specifying the identification key of the OU that is
one level higher than the OU you are creating in the organizational hierarchy in the Higher OU field.
To display the master data of the higher-level OU, choose the OU by double clicking the Higher OU field.
4. Save the data.
1.
1.1.3.2.12 Maintain Organizational Units: Initial Screen

To create an organizational unit (OU), specify the following data on the initial screen:
Institution
Specify the institution for which you want to create the OU.
Identification key of the OU
If you are working with internal number assignment, leave the Organizational Unit field blank. The system automatically assigns an
identification key when you save the data.
PUBLIC
Page 12 of 75
If you are working with external number assignment, enter the required identification key in the Organizational Unit field.
Type of OU
Specify the category of the organizational unit to be created in the OU Category field. The organizational unit categories available
depend on the specified institution.
Template
If you want to use an existing organizational unit as a template when creating your OU, specify the identification key of the existing
organizational unit in the Organizational Unit field in the Template group box. This organizational unit must be of the specified
category.
If you want to change or display organizational units, you simply have to specify the identification key of the OU concerned. If you do
not know the identification key, you select it from the value help.
1.1.3.2.13 Changing Organizational Units

You can change the master data of organizational units (OUs) as you like. Note that the following changes result in the system resetting
the status of released OUs to not released:
Change to the validity dates
Change to the organizational hierarchy
You change the organizational hierarchy whenever you change the higher-level OU in the master data of the OU.
Caution
Note that making changes to organizational units in production operation can lead to inconsistencies within existing data.
Procedure
Choose Hospital Basic Data Administration Hospital Structure Organizational Structure Organizational Unit Change
The Change Organizational Unit: Initial Screen appears.
2. Specify the institution and the identification key of the organizational unit.
3. Choose
(Change).
The Change Organizational Unit: Administrative Data screen appears.
4. Maintain the data as required on the appropriate tab pages. For more information about this, see:
Organizational Unit: Name and Address Data
Organizational Unit: Departmental Per Diem
Organizational Unit: Specialty Keys
Organizational Unit: Indicators Relevant to Processing
Organizational Unit: Validity Dates
Organizational Unit: Blocking Indicator
1.
on the
Note
If you change the validity of the OU, a dialog box appears. This enables you to check whether the OU is used after the change in a
movement that is situated outside the validity period of the OU. To do this, choose Check Consistency. Note that this consistency
check can take a long time and may terminate if the runtime exceeds the maximum dialog time.
5.
Save the data.

You return to the initial screen.
1.1.3.2.14 Flagging Organizational Units for Deletion

Prerequisites
You cannot delete organizational units (OUs) directly. Deleting OUs without first checking whether dependent objects exist would
constitute a serious threat to data consistency within the IS-H system. For instance, you might delete an OU to which a case is still
assigned for nursing care.
For this reason, you should block OUs you no longer want to use. You can no longer use blocked OUs. Existing assignments between
the OU and objects are retained. For more information about this see Blocking/Unblocking Organizational Units.
If you want to physically delete OUs, first set a deletion flag for the OUs to be deleted. You can then run a deletion program to delete all
of the OUs flagged for deletion. At present, SAP does not support a program for deleting OUs flagged for deletion. Note that there are
no restrictions on using OUs flagged for deletion.
Note
PUBLIC
Page 13 of 75
OUs flagged for deletion are not listed in the input help.
Procedure
1.
2.
3.
4.
5.
Specify the institution and the identification key of the organizational unit.
Choose
(Change).
The organizational unit entry screen appears.
Choose Set Deletion Flag.
A dialog box appears. Confirm that you want to flag the building unit for deletion by choosing (Continue).
Save the data.
on the
More Information
Canceling the Deletion Flag for Organizational Units
1.1.3.2.15 Canceling the Deletion Flag for Organizational Units

Procedure
1.
2.
3.
4.
5.
Choose
(Change).
The entry screen of the OU appears.
Choose Organizational unit Deletion flag Cancel .
A message box informs you that that the deletion flag was canceled. Confirm this message by choosing (Continue).
Save the data.
on the
More Information
Flagging Organizational Units for Deletion
1.1.3.2.16 Blocking/Unblocking Organizational Units

You can block organizational units (OUs) by setting the blocking indicator in the master record of the OU. You can no longer use blocked
OUs in subsequent functions. Existing relationships between these OUs and other objects are retained.
If you want to release a blocked OU for further use, you can unblock the OU.
Procedure
1.
2.
3.
4.
5.
6.
Choose Hospital Basic Data Administration Hospital Structure Organizational Structure Organizational Unit Change on the
Choose
(Change).
The Change Organizational Unit: Administrative Data screen appears. Your cursor is positioned on the Description tab page.
To block the OU, select Blocking indicator.
To unblock the OU, deselect Blocking indicator.
Save the data.
PUBLIC
Page 14 of 75
1.1.3.3 Organizational Hierarchy

The organizational hierarchy depicts the relationships between the various organizational units (OUs).
You create these relationships by assigning one organizational unit to another, where one OU is subordinate to the other.
You can maintain the organizational hierarchy explicitly. Alternatively, you can maintain the organizational hierarchy when maintaining the
organizational units. To do this, in each case specify the higher-level OU in the master data of the OU you are maintaining. The system
uses this specification to create the corresponding assignment records in the organizational hierarchy.
Structure
The resulting hierarchy can portray any number of levels.
The category of the organizational units determines whether you can assign one organizational unit to another. In Customizing for ISH, you specify which building categories may be assigned to each other. For more information about this, see Maintain Hierarchy of
Organizational Unit Categories in the IS-H Implementation Guide.
More Information
Maintain the Organizational Hierarchy
Displaying the Hierarchy Overview Graphic
1.1.3.3.1 Example: Organizational Hierarchy

You depict a multiple-level organizational hierarchy by representing the relationships between the organizational units using single-level
assignments in the system.
Caution
Do not assign departmental OUs below nursing or treatment OUs (i.e. care units or outpatient clinics) in the hierarchy.
Caution
Do not make recursive assignments.
1.1.3.3.2 Maintain the Organizational Hierarchy

PUBLIC
Page 15 of 75
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Organizational Structure
Organizational Hierarchy Maintain .
The system lists the existing organizational unit assignments.
If you entered the higher-level organizational unit when maintaining the organizational units, these assignments are included in this list.
2. The following editing options are available from this list:
Create New Assignments
Display and Change Existing Assignments
Delete Existing Assignments
Now proceed with the following steps in relation to the processing option you wish to use:
Display and Change Existing Assignments Delete Existing Assignments
1. Choose
(Create).
1. Select an entry, and then choose
1. Select the entry you want to delete, and
The Maintain Organizational Hierarchy
(Details).
then choose
(Details).
screen appears.
The assignment detail screen appears.
2. Specify the identification keys of the
The institution for which this assignment 2. Choose
(Delete).
OUs you want to assign to one another.
is valid is displayed in the Hierarchy
A confirmation prompt is issued.
You need to have created these
group box.
3. Confirm the delete operation.
organizational units beforehand. You
2. Change the data as required, and then
The system deletes the entry and
can only assign OUs to each other if
save.
returns to the list of existing
both OUs are created in the same
A dialog box appears containing the
assignments.
institution.
changed data.
The system uses the validity period
3. Confirm the changes by saving the
common to both organizational units as
data.
the default validity period for the
You return to the list of existing
assignment. You can further restrict the
assignments.
validity period of the assignment.
The detail screen provides a navigation
3. Save the data.
function to enable you to edit individual
assignment records quickly and directly. To
assignments.
go directly from the detail screen to the
detail screen of the next entry, choose
(-). To go to the detail screen of a specific
entry, specify the data of the required entry
in at least one field in the Table Entry
Selection group box. Then choose
(-).
To display the master data of the assigned
OUs, you can double-click (choose) the
required OU on the assignment detail
screen.
1.
1.1.3.3.3 Displaying the Hierarchy Overview Graphic

By means of the hierarchy overview you can display in graphical form the relationship between the organizational units (OUs) as
defined in the system. Here you can specify for which OU you want to display all the lower-level (dependent) OUs.
Procedure
Organizational Hierarchy Display or Maintain.
The list of existing assignments appears.
2. Choose
(Overview).
A dialog box appears for you to specify the institution, key date and OU for which you want to display the dependent OUs in graphical
form.
1.
Note
If you have positioned the cursor on an OU in the list of existing assignments, the system proposes this OU as the highest-level
node for the display.
If you have positioned the cursor outside of the list, the system proposes the institution as the highest-level node for the display.
3.
Choose
(Continue).
The system displays, in graphical form, the organizational structure that is subordinate to the specified OU.
PUBLIC
Page 16 of 75
1.1.3.3.4 Interdepartmental Relationships

In addition to the organizational relationships between organizational units (OUs) you define within the organizational hierarchy,
interdepartmental relationships can also exist between OUs. An interdepartmental relationship exists if one OU is authorized to assign
patients to beds on another OU even though no organizational relationship exists between these OUs.
You can only maintain this interdepartmental relationship between two OUs if this is allowed in the master data of the OUs. In other
words, the Interdept.Asgmt Auth. indicator (can assign patients to beds on OU of other department) must be set in the master data of
the assigning (departmental) OU and the Interdept. OU indicator (beds on OU can be assigned patients from other department) must
be set in the master data of the (nursing) OU to which the assignment is to be made.
The following illustration is an example of an organizational hierarchy with interdepartmental relationships.
In the above illustration, the Urology department is authorized to make interdepartmental assignments to the beds of care unit 2 and to
the intensive care unit of the surgery department.
Caution
Do not assign departmental OUs below nursing or treatment OUs (i.e. care units or outpatient clinics) in the hierarchy.
Do not make recursive assignments, as illustrated below:
Note that the examples illustrated as incorrect above are only possible or can occur if the OU Surgery Unit 1 or the OUs Surgery Unit
1and Urology Unit 1 are also flagged as departmental OUs and as authorized to assign patients to beds on OU of other department
(Interdept. Asgmt Auth. indicator set).
More Information
Maintain Interdepartmental Relationships
1.1.3.3.5 Maintain Interdepartmental Relationships

Procedure
Interdept. Bed Asgmt Maintain .
The list of existing assignments appears.
Now proceed with the following steps depending on the editing option you are using:
1.
PUBLIC
Page 17 of 75

1. Choose
(Create).
1. Select the entry to be deleted, and
The assignment detail screen
(Details).
then choose
(Details).
appears.
2. In the Org. Unit field, enter the
appears.
appears.
identification key of the OU to whose
2. Change the data as required, and then 2. Choose
(Delete).
beds patients can be assigned by
save.
OUs of other departments. In the
3. If you have changed the validity dates, 3. Confirm the delete operation.
Asgmt By field, specify the
a dialog box containing the changed
The system deletes the entry and returns
identification key of the OU with intertime intervals appears. Confirm the
to the list of existing assignments.
departmental assignment authority.
changes by choosing (Save).
4. If you have changed the OU
organizational units beforehand.
assignment, the system deletes the
In the Max. Number of Beds field, you
changed entry and creates a new
can specify the maximum number of
entry. It issues a warning message
beds on the care unit to which the
accordingly. Confirm this operation by
department may assign patients from
choosing (Continue).
other departments. You can display
this specification in the bed scheduling assignments.
function of care unit management.
The detail screen provides a navigation
When you assign patients, at present function to enable you to edit individual
the system does not check whether
assignment records quickly and directly.
the maximum number of interTo go directly from the detail screen to the
departmental beds has been reached. detail screen of the next entry, choose
(-). To go to the detail screen of a specific
common to both organizational units
entry, specify the data of the required
as the default validity period for the
entry in at least one field in the Table Entry
assignment. You can further restrict the Selection group box. Then choose
(-).
To display the master data of the
You can specify sort numbers in the
assigned OUs, you can double-click
Sort Order field. These are taken into
(choose) the required OU on the
account when the list of free bed
assignment detail screen.
locations is output.
3. Save the data.
assignments.
1.1.3.4 Maintaining Organizational Unit-to-Building Unit

Assignments
You create the link between the organizational hierarchy and the building hierarchy by assigning building units to organizational units
(OUs). You can define the building unit-to-OU assignments in the transactions for maintaining the organizational structure or the building
structure.
This means you creating an assignment involving OUs located on the lowest level of the organizational hierarchy (for example, care
units, outpatient clinics) and building units located at the uppermost level of the building hierarchy (for example, rooms, corridors).
Multiple Assignment of Building Units
You can assign building units to multiple OUs:
As a primary assignment, if the building unit is assigned to the organizational unit in accordance with the hospital organizational
structure
As a secondary assignment, if the building unit already has a primary assignment to an OU and is also assigned to a different
organizational unit, since it is also used by this unit. You can also use the secondary assignment independently of an existing primary
assignment.
You can use this multiple assignment of a building unit in visit scheduling, if you allocate patient appointments for a treatment room that is
used by different outpatient clinics/service facilities For more information, see Multiple Assignment of Building Units in Visit Scheduling.
Prerequisites
The organizational units and building units for which you want to create an assignment must already exist.
Note
The category of the OU and of the building unit determines whether they can be assigned to one another. In Customizing for IS-H, you
specify which organizational unit categories may be assigned to which building unit categories.
PUBLIC
Page 18 of 75
Procedure
Choose Hospital Basic Data Administration Hospital Structure Organizational Structure Building Unit Assignment Maintain
on the SAP Easy Access screen.
The Change Building Unit-Organizational Unit Assignments screen appears with the list of existing assignments.
The following editing options are available from this list:
2. Now proceed with the following steps depending on the editing option you are using.
1.

Choose
(Create).
2. Specify the identification key of the OU and of the building unit you wish to assign to one another.
The system uses the validity period common to the organizational unit and the building unit as the default validity period for the
assignment. You can further restrict the validity period of the assignment.
3. Save the data.
You return to the list of existing assignments.
1.

1.
2.
3.
4.
5.
Select an entry, and then choose

(Details).
Change the data as required, and then save.
If you have changed the validity dates, a dialog box containing the changed time intervals appears. Confirm the changes by choosing
(Save).
If you have changed the assignment, the system deletes the changed entry and creates a new entry. It issues a warning message
accordingly. Confirm this operation by choosing (Continue). You return to the list of existing assignments.
The detail screen provides a navigation function to enable you to edit individual assignment records quickly and directly. To go
directly from the detail screen to the detail screen of the next entry, choose
(-). To go to the detail screen of a specific entry,
specify the data of the required entry in at least one field in the Table Entry Selection group box. Then choose
(-).
To display the master data of the OU or of the building unit, you can double-click (choose) the required OU or building unit on the
assignment detail screen.

Select the entry to be deleted, and then choose
(Details).
2. Choose
(Delete).
The system deletes the entry and returns to the list of existing assignments.
1.
1.1.3.5 Maintaining Statistical Bed Figures

You can store statistical bed figures for departmental and nursing organizational units (OUs) or a combination of departmental and
nursing OUs. Specifying statistical bed figures for a combination of departmental and nursing OUs enables you to also enter statistical
bed figures for OUs whose beds are assigned patients from other departments (inter-departmental bed assignment supported.
You can enter statistical bed figures as planned values (planned beds) and as actual values (setup beds). You further specify planned
and actual values according to a number of criteria.
Country Version Germany
In Germany, the following government-mandated statistics evaluate the statistical bed figures:
L3 statistics pursuant to BPflV 1995 (patient census statistics of departments)
L1 statistics pursuant to BPflV 1995 (patient census statistics of hospital)
S1 statistics pursuant to BPflV 1985 (care unit patient list)
S4 statistics pursuant to BPflV 1985 (statistical key figures of departments)
For information on how the statistical bed figures are evaluated in the various statistics, see the documentation on each statistics
program.
Procedure
Statistical Beds Maintain .
The Maintain Statistical Bed Assignments screen appears with the existing entries.
Create New Entries
Display and Change Existing Entries
1.
PUBLIC
Page 19 of 75
Delete Existing Entries

Create New Entries
1. Choose
(Create).
1. Select the entry you want to delete,
The detail screen appears.
(Details).
and then choose
(Details).
2. Specify the identification key of the OU
for which you want to store statistical
2. Make any necessary changes.
2. Choose
(Delete).
bed figures. This can be the
To display the master data of the OUs
departmental OU or the nursing OU or
specified, double-click (choose) the
a combination of both.
required OU on the detail screen.
3. Save the data.
returns to the list of existing entries.
organizational units beforehand.
You return to the list of existing entries.
Note the validity period of the
The detail screen provides a
statistical bed figures. The system
navigation function to enable you to
uses the validity period of the OU per
edit individual assignment records
default. If you specified a departmental
quickly and directly. To go directly from
OU and nursing OU combination, the
the detail screen to the detail screen
system uses the validity period
of the next entry, choose
(-). To go
common to both organizational units
to the detail screen of a specific entry,
as the default validity period for the
specify the data of the required entry
assignment.
in at least one field in the Table Entry
You can specify the validity of the
Selection group box. Then choose
statistical bed figures in the Valid From
(-).
and Valid To input fields. The system
displays the validity periods of the
OUs in the display fields with the same
name.
3. Specify the statistical bed figures. For
information about the various input
fields, see the F1 help.
4. Save the data.
1.1.3.6 Release Organizational Structure

Once you have maintained organizational units (OUs) and hierarchy relationships, you have to release these structures. This involves
the system checking that the hierarchy structure is consistent. The system sets the release indicator in the master data of each correct
OU.
You can only use released OUs in subsequent functions.
In response to the release operation, the system outputs a release log. If errors occurred, this log records the reason for the various
errors and the identification key of the OUs which could not be released. You cannot use OUs which have not been released nor the
OUs subordinate to these OUs in the hierarchy.
Note
When releasing the organizational hierarchy the system checks the assignment of building units to OUs for consistency. However, it
does not release the building units. To release building units, you have to release the building hierarchy.
The system cancels the release indicator if you make the following changes to OUs that have already been released:
Change to the validity
Change to the organizational hierarchy
Change to the assignment of OUs to building units
Change to the inter-departmental relationship
Here the system cancels the release indicator only for OUs that are directly concerned by the change. However, you can no longer use
OUs that are below this OU in the organizational hierarchy. To release these OUs again, you have to release the entire organizational
structure once more.
Procedure
Release Structure .
The IS-H Release Organizational Units for Institution screen appears.
2. Specify the institution for which you want to release the organizational structure.
You can release the organizational structure in live or test mode.
If you select test mode, the system performs the consistency checks without actually releasing the OUs. You can stipulate the scope
of the checks in test mode. For instance, if you only wish to check the consistency of the organizational hierarchy, select Org.
Hierarchy and deselect the other options.
If you release the organizational units in live mode, the system checks all of the elements of the organizational structure and releases
1.
PUBLIC
Page 20 of 75
3.
the OUs. To enable this mode, deselect Test and select all of the check options.
Choose
(Execute).
If you ran the program in test mode, the system displays the results of the checks in the log.
If you ran the program in live mode, the system releases the organizational structure and then displays the log. The log shows which
OUs have been released and which have not been released.
1.1.3.7 Transport Organizational Units

You can transport organizational units (OUs) with their dependent tables using program RNUTROE0. For this purpose, you can select an
existing transport request or create a new one.
Caution
Do not run this program until you are familiar with the basic conditions governing its use, how it functions and its possible
consequences.
Contact your consultant or SAP Consulting if necessary.
SAP does not accept liability for any damage resulting from the use of this program.
Prerequisites
Ensure that no inconsistencies arise when transporting OUs to another client or another system.
Caution
The system does not perform consistency checks during the transport operation.
Inconsistencies can arise for the following reasons:
Since master data is based on customizing data, you should always transport the customizing data first. Always use automatic
recording of customizing changes.
In the target system, you may have already maintained OUs which have the following characteristics:
The OUs do not exist in this form in the source system
The OUs have a different identification key in the source system
The OUs were created in a different order in the source system
The order in which the OUs are created can lead to inconsistencies since address management essentially works with internal
assignment and as a result two OUs with identical attributes can have different address numbers in the database.
If you transport OUs without transporting the building units, the assignment of OUs to building units can differ.
The OUs are transported to the target system with the respective release status they have in the source system. In other words, if an
OU is not released in the source system and is transported, it is also not released in the target system. Consequently, you should
release the building units in the source system prior to executing the transport. You could then run the release program in test mode in
the target system to check the result of the transport.
Features
You can further restrict the OUs data to be transported by using the following selection criteria on the program selection screen:
Institution
OU
Creation date
Changed on
Include the assignments of OU to cost centers
If you wish to include the OU-to-cost center assignments in the transport operation, select With OU-to-Cost Center Asgt.
Note
The selection criteria are linked by an AND operator. Thus if you enter an interval for building unit creation and change, the
transport will include the OUs that were created and changed within the specified time frame.
If, however you want to select all OUs that were created or changed within a given period, you must run the program twice: once
specifying the creation interval and a second time specifying the change interval. For this reason there may be duplicate entries in
the request. These do not represent a problem.
The following data is included in the transport request:
OUs flagged for deletion, to ensure that the flag is passed on to the target system
Long texts for the OUs selected
Entries for the organizational hierarchy
Inter-departmental assignments
Assignment to building units
Statistical beds
Generic entries (*, for instance for the statistical beds) are included in the transport request if the identification key of an OU appears
directly in one of the dependent tables.
PUBLIC
Page 21 of 75
Example Entries for Statistical Beds

Entries
* -*
* - SURG1
Transport request
These entries for the statistical beds are never included.
These entries would be included, if the OU SURG1 were selected.
Note
This program does not take doors into account. They are, however, taken into account by the program for transporting building units.
Moreover, it is not possible to transport change documents.
Specifications for Program Execution

You can execute the program for transporting OUs in test mode or live mode.
If you run the program in test mode, the system selects the OUs to be transported and checks whether it would be successfully
included in the transport request in live mode. However, the objects to be transported are not actually included in the transport
request. To execute the program in test mode, select Test Mode. Even if you have selected Test Mode, you must select or create a
transport request. There is no test mode for creating a request.
If you run the program in update mode, the system selects the OUs to be transported. To execute the program in update mode,
deselect Test Mode.
More Information
Transporting Organizational Units
1.1.3.7.1 Transporting Organizational Units

Procedure
From the SAP Easy Access screen, choose Hospital Statistics/Information Report Tree Basic Data Hospital Structure ISH: Transport Organizational Units .
The IS-H: Transport Organizational Units screen appears.
2. Specify the institution and further selection criteria. Also specify whether you want to run the program in test or live mode.
3. Choose
(Execute).
The Prompt for Workbench Request dialog box appears Enter a request number, and then choose
(Continue).
The program outputs the following data:
Number of the transport request
Number of the task
Number of records included per table
1.
1.1.4 Building Structure

The building structure represents the spatial reality of the organizational units You can define hospital rooms, corridors, bed locations
and so on as building units.
You define the relationships between the building units using the building hierarchy. You establish the link between the building structure
and the organizational structure by assigning building units to organizational units.
The building structure is only used by certain areas. You have to store the building structure in the system only if you want to use the
functions of these areas. These areas in question are:
Organizational structure
Information functions, for instance public list with room specifications
Outpatient clinic management
Care unit overview graphic
Patient assignment to rooms and beds
1.1.4.1 Creation of Building Structure

PUBLIC
Page 22 of 75
To create the building structure, work through the following activities in the order specified.
Process
1.
2.
3.
4.
5.
6.
7.
Maintain building structure:

For more information about this, see Building Structure and the related sections.
Maintaining building hierarchy:
For more information about this, see Building Hierarchy and the related sections.
Maintain relationships to organizational structure:
For more information about this, see Maintaining Organizational Unit-to-Building Unit Assignments.
Maintain planning characteristics:
For more information about this, see Maintaining Planning Characteristics.
Maintain facility characteristics:
For more information about this, see Maintaining Facilities of a Building Unit.
Maintain doors:
For more information about this, see Maintaining Doors.
Release building structure:
For more information about this, see Releasing the Building Structure.
1.1.4.2 Building Units

You define the physical components of organizational units such as hospital rooms, bed locations, care unit corridors, treatment rooms,
etc. as building units. Using facility characteristics and planning characteristics you can store the attributes and facilities of the building
units.
Whenever you create a building unit, you assign a particular category to it. The category of a building unit specifies whether this building
unit is a hospital room, treatment room, corridor, etc. You can define building unit categories of your choosing in Customizing for IS-H. For
more information about this, see Define Building Unit Categories in the IS-H Implementation Guide.
Structure
You can store the following data within the master data of a building unit:
Building Unit: Name Data
Building Unit: Validity Dates
Building Unit: Coordinate Data
Integration
Only categories of building units which you have characterized as rooms or bed locations in Customizing for IS-H are of functional
significance. The following functions are supported for rooms and bed locations:
Assignment of patients to rooms and bed locations
Graphical representation in the care unit overview graphic
More Information
Assignment of Identification Keys for Building Units
Create Building Units
Change Building Units
Blocking/Unblocking Building Units
Flagging Building Units for Deletion
Canceling the Deletion Flag for Building Units
1.1.4.2.1 Building Unit: Name Data

You can store the following name data for a building unit. You should maintain this data fully, since it is output at different places within
the system.
Name of the building unit (Bld. unit name field)
You specify the long text for the building unit here.
Building unit short text
You enter the short text of the organizational unit in this field. The system outputs the short text for rooms in the care unit overview
graphic if a door is not defined for the room.
Building unit identifier
The identifier of the building unit is output on many screens, for example in the case list, the care unit overview graphic, the room and
PUBLIC
Page 23 of 75
bed listing and so on. For this reason, you should use mnemonic keys in as far as possible. Identifiers of building units must only be
unique in relation to organizational unit or building unit located above them in the hierarchy.
You can use the identifier when entering the patient assignment.
Note
To ensure the short text is maintained for each building unit, you should define the corresponding field as a required-entry field in
Customizing.
Note
In the enhanced occupancy list of the care unit overview, the system displays the bed locations of a care unit without indicating the
room in which the bed location is situated. If you work with the enhanced occupancy list, you should define the bed location identifiers
such that they also contain the room identification.
1.1.4.2.2 Building Unit: Validity Dates

You create building units with a particular validity. The system defaults the validity start date to the current date and the validity end date
to 12/31/9999 (unlimited). You can change this data.
You cannot use the building unit outside of the specified validity period. This means that you cannot assign building units to other building
units or to organizational units outside of their specified validity period. It is also impossible to assign patients to them.
Note
If you wish to transfer legacy data from a previous system and wish to assign the oldcases to building units, you have to set the
validity start date such that the building units are valid when the movements of the transferred cases take place.
If you want to shut down a building unit, you should delimit the validity of the building unit accordingly and set the blocking indicator.
1.1.4.2.3 Building Unit: Coordinate Data

The coordinate data specifies the horizontal and vertical position of a building unit within the coordinate system, which is the basis for
the care unit overview graphic. In this way, you specify the physical location of the building units within an organizational unit.
If you wish to display the care unit overview (graphic) in graphical form within Care Unit Management, you have to specify the
coordinates of the building units.
If you do not wish to use the care unit overview graphic, you do not need to maintain the coordinate data.
More Information
Maintain Building Units for Care Unit Graphic
Rooms in the Care Unit Overview Graphic
Corridors in the Care Unit Overview Graphic
Bed Locations in the Care Unit Overview Graphic
1.1.4.2.4 Assignment of Identification Keys for Building Units

A building unit is defined by means of a unique identification key.
The identification key of the building unit can be assigned by the system (internal number assignment), or you can assign it yourself
(external number assignment). In Customizing for IS-H, you can specify whether one of these two number assignment methods
should be excluded. In Customizing, you can also define the number ranges authorized for internal and external number assignment.
The building unit identification keys must be unique within a client. The system ensures that unique identification keys are always
assigned. With internal number assignment, the system always selects the next number from the internal number range. With external
number assignment, the system prevents a number, which is already assigned, from being assigned again.
Note
If you work with external number assignment, choose the identification keys such that you can quickly create building units of several
PUBLIC
Page 24 of 75
organizational units by copying the identification key and making slight changes to the resulting copy. For instance, if the building
structure of different floors is similar, you can include the floor number in the identification key. After creating the building units of one
floor, you can use these building units as a reference for further building units and only have to change the floor number in the
identification key.
Note
If you have defined several institutions in one client and are using external number assignment, you can specify a prefix for each
institution which the system places at the start of the identification key of the institutions. This enables you to characterize the building
units which belong to the building structure of an institution.
1.1.4.2.5 Create Building Units

You can use the following editing methods to create building units:
Creating Building Units: Single Entry
You call the function for each building unit you want to create. Single entry enables you to maintain the complete master data of the
building unit.
Changing Building Units: Collective Entry
In collective entry, you can create several building units on a collective entry screen and in doing so subordinate them to building units
or organizational units. You cannot maintain the complete master data of the building unit on the collective entry screen. You can,
however, go directly from collective entry to the master data of the building unit.
1.1.4.2.6 Creating Building Units: Single Entry

You can create building units using or not using a copying template. On the initial screen of the transaction, you specify an existing
building unit of the required category as the building unit you wish to copy. If you create a building unit using a copying template, the
system transfers almost all the data of the template building unit as default values into the new master record. The following data is not
transferred:
Release Indicator
The system automatically sets the release indicator when you release the building structure.
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Building
Unit Create .
The Change Building Unit: Initial Screen appears.
2. Enter the data as required on the initial screen, and then choose
( Create).
The Create Building Unit: Data Screen appears.
3. Make the following entries:
Building Unit: Name Data
Building Unit: Validity Dates
Building Unit: Coordinate Data
4. Save the data.
1.
1.1.4.2.7 Maintain Building Units: Initial Screen

To create a building unit, specify the following data on the initial screen:
Institution
Specify the institution for which you want to create the building unit.
Identification key of the building unit
If you are working with internal number assignment, leave the Building unit field blank. The system automatically assigns an
identification key when you save the data.
If you are working with external number assignment, enter the required identification key in the Building unit field.
Building unit category
Specify the category of the building unit to be created in the Build. unit category field.
PUBLIC
Page 25 of 75
Template
If you want to use an existing organizational unit as a copying template when creating your OU, specify the identification key of the
existing organizational unit in the Building unit field in the Template group box. This building unit must be of the specified category.
If you want to change or display building units, you simply have to specify the identification key of the building unit concerned. If you do
not know the identification key, you select it from the value help.

Procedure
Unit Collective Entry .
The Collective Entry Building Units: Overview screen appears.
2. The overview screen displays all of the existing building units. To create further building units, choose New entries.
The system displays additional input lines.
3. Specify the data of the building unit to be created.
For more information about maintaining this data, see Create Building Units: Collective Entry Screen.
1.
Note
You can go directly from the collective entry overview screen to the detail screen of a building unit. To do this, select the desired
building unit, and then choose
(Details). The master data of the building unit appears. To return to the overview screen, choose
(Back). When you save the master data on the detail screen, you not only save the master data of the building unit but also all
of the changes you made on the collective entry overview screen.
4.
You can confirm your entries by choosing (Check) or (Enter). The system checks the consistency of the data, and changes the
Bld. unit input field into a display field. This means that you can no longer change the identification key of the building unit. However,
your specifications are not yet saved.
Note
Provided you have not yet saved the entries, you can delete certain entries. To do this, select the entry to be deleted, and then
choose Goto Delete line . Entries that have already been saved cannot be deleted.
5.
Then save the data.

You return to the SAP Easy Access screen.
1.1.4.2.9 Create Building Units: Collective Entry Screen

If you create building units using the collective entry function, you can maintain the following master data of the building unit on the
overview screen:
Identification Key
If you are working with external number assignment, enter the required identification key in the Bld. unit field.
If you are working with internal number assignment, leave the Bld. unit field blank. The system automatically assigns an identification
key when you save the data..
Building unit category
Specify the category of the building unit in the Ca field. You can list the permitted values for input by choosing the value help. This is a
required-entry field.
Building unit short text
You enter the short text of the organizational unit in this field.
The identifier of the building unit is output on many screens, for example in the case list, the care unit overview graphic, the occupancy
overview and so on. For this reason you should use mnemonic identifiers in as far as possible. Identifiers of building units must only be
unique in relation to organizational unit or building unit located above them in the hierarchy.
Validity dates
You create building units with a particular validity. The system defaults the validity start date to the current date and the validity end
date to 12/31/9999 (unlimited). You can change this data.
When creating building units on the collective entry overview screen, you can also subordinate the building units to a building unit or
organizational unit. In this way you simultaneously maintain the building hierarchy or the link between the organizational hierarchy and the
building hierarchy. You can do this only if the building unit or organizational unit to which you subordinate the building unit already exist.
Assignment to a building hierarchy
To subordinate the building unit (e.g. bed location) to another building unit in the building hierarchy (e.g. hospital room), specify the
identification key of the higher level building unit in the Higher BU field.
PUBLIC
Page 26 of 75
Assignment to an organizational hierarchy

To subordinate the building unit (e.g. sick room) to an organizational unit (e.g. care unit), specify the identification key of the higher level
building unit in the Higher OU field.
1.1.4.2.10 Change Building Units

You can use the following editing methods to change the master data of building units:
Changing Building Units: Single Entry
You call the function for each building unit you want to change. Single entry enables you to maintain the complete master data of the
building unit.
In collective entry, you can change several building units on a collective entry screen and in doing so change their assignment to other
building units or organizational units. You cannot maintain the complete master data of the building unit on the collective entry screen.
You can, however, go directly from collective entry to the master data of the building unit.
Note that the following changes result in the system resetting the status of released building units to not released:
Change to the validity dates
Change to the assignment to building units or organizational units
1.1.4.2.11 Changing Building Units: Single Entry

Procedure
On the SAP Easy Access screen, choose Hospital Basic Date Administration Hospital Structure Building Structure Building
Unit Change . The Change Building Unit: Initial Screen appears.
2. Specify the identification key of the building unit to be changed, or determine it from the value help.
3. Choose
(Change).
The Change Building Unit: Data Screen appears.
4. Maintain the data.
Name and identifier
Validity dates
Coordinates
1.
Note
If you change the validity of the building unit, a dialog box appears. This enables you to check whether the building unit is used
after the change in a movement that is situated outside the validity period of the building unit. To do this, choose
(Consistency).
Note that this consistency check can take a long time and may terminate if the runtime exceeds the maximum dialog time.
5.
Save the data.


Procedure
Unit Collective Entry .
The Collective Entry Building Units: Overview screen appears. The overview displays all the existing building units and their
assignment to other building units or organizational units.
2. You can change the master data of the building units and their assignment to other building units or organizational units on the
overview screen.
1.
Note
You can go directly from the collective entry overview screen to the master data of a building unit. To do this, select the desired
building unit, and then choose
(Details). To return to the overview screen, choose
(Back). When you save the master data
on the detail screen, you not only save the master data of the building unit but also all of the changes you made on the collective
entry overview screen.
PUBLIC
Page 27 of 75
3.
Then save the data.

You return to the SAP Easy Access screen.
1.1.4.2.13 Flagging Building Units for Deletion

Prerequisites
You cannot delete building units directly. Deleting building units without first checking whether dependent objects exist would constitute a
serious threat to data consistency within the IS-H System. For instance, you might delete a building unit to which a case is still assigned.
For this reason, you should block building units you no longer want to use. You can no longer use blocked building units. Existing
assignments between the building unit and objects are retained. For more information about this, see Blocking/Unblocking Building Units.
If you want to physically delete building units, first set a deletion flag for the building units to be deleted. You can then run a delete
program to delete all of the building units flagged for deletion. Note that there are no restrictions on using building units flagged for
deletion.
Procedure
1.
2.
3.
4.
5.
Unit Change .
Specify the identification key of the building unit, or determine it from the value help.
Choose
(Change).
The master data of the building unit appears.
Choose Set Deletion Flag.
A dialog box appears. Confirm that you want to flag the building unit for deletion by choosing (Continue).
Save the data.
More Information
Canceling the Deletion Flag for Building Units
1.1.4.2.14 Canceling the Deletion Flag for Building Units

You can cancel the deletion flag you set for a building unit.
Procedure
1.
2.
3.
4.
5.
Unit Change .
Specify the identification key of the building unit, or determine it from the value help.
Choose
(Change).
The master data of the building unit appears.
Choose Building Unit Deletion Flag Cancel .
A message box informs you that that the deletion flag was canceled. Confirm this message by choosing (Continue).
Save the data.
More Information
Flagging Building Units for Deletion
1.1.4.2.15 Blocking/Unblocking Building Units

You can block building units by setting the blocking indicator for the building unit in the units planning characteristics. If you set the
blocking indicator for a building unit, you must also specify the reason for this block.
PUBLIC
Page 28 of 75
You can no longer use blocked building units in subsequent functions. Existing relationships between these building units and other
objects are retained.
If you want to release a blocked building unit for further use, you can unblock the building unit.
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Planning
Characteristics Maintain .
The Maintain Plan. Characteristics of Building Units screen appears with the list of building unit for which you defined planning
characteristics.
2. Depending on whether you have already stored planning characteristics for the building unit to be blocked, proceed as follows:
If planning characteristics are already defined, select the relevant entry, and then choose
(Details). The planning characteristics
of the selected building unit are displayed.
If there are no planning characteristics defined for the building unit, choose
(Create). Specify the identification key of the building
unit to be blocked in the Bld. Unit field.
3. To block the building unit, flag the Blocking Indicator checkbox, and specify a blocking reason.
To unblock the building unit, deselect the Blocking Indicator checkbox, and delete the blocking reason.
1.
Note
You can define blocking reasons of your choosing in Customizing for IS-H. For more information about this, see Define Blocking
Reasons in the Healthcare Implementation Guide.
The system proposes the validity period of the building unit for the validity of the planning characteristics. You can change this
data. However, the validity period of the planning characteristics has to lie within the validity period of the building unit.
4.
Save the data.

More Information
Maintain Planning Characteristics
1.1.4.3 Building Hierarchy

The building hierarchy depicts the relationships between the various building units.
You create these relationships by subordinating a building unit to another building unit.
Example
In this way, you assign bed locations to sickrooms, for example.
Structure
The category of the building units determines whether you can assign one building unit to another. In Customizing for IS-H, you
specify which building categories may be assigned to each other.
In Customizing for IS-H, you assign the type of building unit to each category. Types of building units are predefined in the system. The
type determines how a building unit can be used in subsequent functions. For more information about this, see Define Building Unit
Categories, Maintain Hierarchy of Building Unit Categories and Assign Building Unit Categories to Org. Unit Categories in the IS-H
Example
For instance, you can use the type of building unit to distinguish sickrooms from care unit rooms. In the hierarchy, you can assign bed
locations to sickrooms but not to care unit rooms.
You can maintain the building hierarchy explicitly. Additionally, you can maintain the building hierarchy when creating or changing building
units using the collective entry function.
More Information
Maintaining the Building Hierarchy
Create Building Units: Collective Entry Screen
Displaying the Building Hierarchy Overview
PUBLIC
Page 29 of 75
1.1.4.3.1 Maintaining the Building Hierarchy

Procedure
1.
Hierarchy Maintain .
The Maintain Building Unit Hierarchy screen appears with the list of existing building unit assignments.
Note
If you edited building units using the collective entry function and, in doing so, already specified the higher-level building unit in each
case, these assignments are contained in this list.
The following editing options are available from this list:
1. Choose
(Create).
1. Select the entry you want to delete, and
(Details).
then choose
(Details).
2. Specify the identification keys of the
building units you want to assign to one 2. Change the data as required, and then
2. Choose
(Delete).
another.
save.
building units beforehand.
assignments.
3. The detail screen provides a navigation
returns to the list of existing
common to both building units as the
function to enable you to edit individual
assignments.
default validity period for the
assignment records quickly and
assignment. You can further restrict the
directly. To go directly from the detail
screen to the detail screen of the next
3. Save the data.
entry, choose
(-). To go to the detail
screen of a specific entry, specify the
assignments.
data of the required entry in at least
one field in the Table Entry Selection
group box. Then choose
(-).
To display the master data of the
assigned building units, you can doubleclick (choose) the required building unit
on the assignment detail screen.
2.
More Information
Building Hierarchy
Displaying the Building Hierarchy Overview
1.1.4.3.2 Displaying the Building Hierarchy Overview

You can display the relationship between building units as defined in the system in a hierarchy overview. Here you can either display the
complete building hierarchy or simply the building units subordinate to a particular building unit.
Procedure
Hierarchy Maintain or Display .
The existing building unit assignments appear.
2. To display the complete building hierarchy, choose
(Overview). The building hierarchy is displayed in the form of an overview.
To display the building hierarchy with reference to a particular building unit, call the detail screen of the required entry. To do this,
select the relevant entry, and then choose
(Details).
On the assignment detail screen, choose
(Overview).
In the hierarchy overview, the system displays the building units that are located below the higher-level building unit of the selected
entry.
To return to the detail screen, choose
(Back).
3. To return to the list, choose
(Back).
4. Exit the function.
1.
PUBLIC
Page 30 of 75
1.1.4.3.3 Planning Characteristics of Building Units

For each building unit, you can store characteristics which specify whether the building unit supports bed assignments and, if this is the
case, for which type of patient.
You can store planning characteristics of this type only for building units to which you can assign patients. These are the building units
bed location, sick room, treatment room and corridor with bed location.
You can store the following planning characteristics:
Room/corridor with bed location
Smoker room
Infection indicator
Maximum occupancy
Sex-specific occupancy
Blocking indicator and blocking reason
Bed location
Blocking indicator
Blocking reason
You can define blocking reasons of your choosing in customizing for IS-H. Examples of such blocking reasons are disinfection,
renovation, reservation.
Integration
Effects of Planning Characteristics
Whenever you assign patients to building units, the system checks whether the building unit is blocked at the date the movement
takes place. You cannot assign patients to blocked building units.
Whenever you assign patients to building units which may only accommodate patients of a certain sex, the system checks whether
the patient is of this sex. If the patient is of a different sex, the system issues a warning message in the patient assignment.
The remaining planning characteristics do not affect subsequent functions. You store these characteristics simply for information
purposes and can display them in the care unit overview and in the care unit overview graphic.
More Information
Maintain Planning Characteristics
Blocking/Unblocking Building Units
1.1.4.3.3.1 Maintain Planning Characteristics

Procedure
To maintain planning characteristics, proceed as follows:
1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Planning
Characteristics Maintain . The Maintain Plan. Characteristics of Building Units screen appears with the list of building unit for which
you defined planning characteristics.
Create New Entries
Create New Entries
Choose
(Create).
2. In the Bld. unit field, enter the identification key of the building unit for which you want to maintain the planning characteristics. Maintain
the planning characteristics.
1.
Note
The system proposes the validity period of the building unit as the validity period of the planning characteristics. You can further
restrict the validity period of the planning characteristics.
3.
Save the data.

PUBLIC
Page 31 of 75

(Details).
3. Save the data.
1.
Note
The detail screen provides a navigation function to enable you to edit individual assignment records quickly and directly. To go
directly from the detail screen to the detail screen of the next entry, choose
(-). To go to the detail screen of a specific entry,
specify the data of the required entry in at least one field in the Table Entry Selection group box. Then choose
(-).

Select the entry to be deleted, and then choose
(Details).
2. Choose
(Delete).
The system deletes the entry and returns to the list of existing assignments.
1.
1.1.4.3.4 Facilities of Building Units

You can store information on building unit facilities in the system. By facilities we mean characteristics which describe the possible uses
of a building unit. You can define facilities of your choosing in Customizing for IS-H.
Example
Examples of such facility characteristics are:
Bathtub
Oxygen supply
Compressed air supply
Telephone jack
More Information
Maintaining Facilities of a Building Unit
1.1.4.3.4.1 Maintaining Facilities of a Building Unit

Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Facilities
Maintain .
2. The building units for which you have stored facilities are listed.
You can assign exactly one facility to a building unit per entry. If you want to assign several facilities to a unit, you have to create an
entry for each facility.
Create new facility characteristics
Display and change existing facility characteristics
Delete existing facility characteristics
1.
Create new facility characteristics

Choose
(Create).
2. Specify the identification key of the building unit for which you want to maintain the facilities. Specify the required facility. You can list
the possible facility characteristics by calling the value help..
1.
Note
PUBLIC
Page 32 of 75
The system proposes the validity period of the building unit as the validity period of the facility. You can further restrict the validity
period of the facility.
3.
Save the data.

Display and change existing facility characteristics

(Details).
3. Save the data.
1.
Note
The detail screen provides a navigation function to enable you to edit individual entries quickly and directly. To go directly from the
detail screen to the detail screen of the next entry, choose
(-). To go to the detail screen of a specific entry, specify the data of the
required entry in at least one field in the Table Entry Selection group box. Then choose
(-).
Delete existing facility characteristics

(Details).
2. Choose
(Delete).
The system deletes the entry and returns to the list of existing entries.
1.
More Information
Facilities of Building Units
1.1.4.3.5 Release of Building Structure

Once you have maintained building units, the hierarchy relationship between the building units, their facilities and planning characteristics
and the relationships to the organizational units (OUs), you have to release the building structure. This involves the system checking that
the hierarchy structure is consistent. For each correct building structure, the system sets the release indicator in the master data of the
building unit.
You can only use released building units in subsequent functions.
Note
When you release the building hierarchy, although the system checks that the assignment of building units to organizational units is
consistent, it does not release the organizational units. To release OUs, you have to release the organizational hierarchy.
In response to the release operation, the system outputs a release log. If errors occurred, this log records the reason for the various
errors and the identification key of the building units which could not be released. Building units which have not been released and
building units subordinate to these building units in the hierarchy cannot be used in subsequent functions.
Integration
The system cancels the release indicator if you make the following changes to building units which have already been released:
Change to the validity
Change to the building hierarchy
Change to the assignment of building units to OUs
Change to the facilities
More Information
Releasing the Building Structure
1.1.4.3.5.1 Releasing the Building Structure

PUBLIC
Page 33 of 75
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Release
Structure .
The IS-H: Release Building Structure screen appears.
2. You can release the building structure in live or test mode.
If you run the release program in test mode, the system performs the consistency checks without actually releasing the building units.
You can stipulate the scope of the checks in test mode. For instance, if you only wish to check the consistency of the building
hierarchy, select Building hierarchy and deselect the other options.
If you run the release program in live mode, the system checks all of the elements of the building structure and releases the building
units. To enable this mode, deselect Test and select all of the check options.
3. Choose
(Execute).
If you ran the program in test mode, the system displays the results of the checks in the log.
If you ran the program in live mode, the system releases the building units and then displays the log. The log shows the building units
that were released and those that were not released.
1.
More Information
Release of Building Structure
1.1.4.3.6 Transport Building Units

You can transport building units with their dependent tables using program RNUTRBE0. For this purpose, you can select an existing
transport request or create a new one.
Caution
Do not run this program until you are familiar with the basic conditions governing its use, how it functions and its possible
consequences.
Contact your consultant or SAP Consulting if necessary.
SAP does not accept liability for any damage resulting from the use of this program.
Prerequisites
Ensure that no inconsistencies arise when transporting building units to another client or another system.
Caution
The system does not perform consistency checks during the transport operation.
Inconsistencies can arise for the following reasons:
Since master data is based on customizing data, you should always transport the customizing data first. Always use automatic
recording of customizing changes.
In the target system, you may have already maintained building units that have the following characteristics:
The building units do not exist in this form in the source system
The building units have a different identification key in the source system
The building units were created in a different order in the source system
The order in which the building units are created can lead to inconsistencies since building units management essentially works
with internal assignment and as a result two building units with identical attributes can have different address numbers in the
database.
If you transport organizational units (OUs) without transporting the building units, the assignment of OUs to building units can differ.
The building units are transported to the target system with their release status from the source system. This means that if a building unit
is not released in the source system when it is transported, it is also not released in the target system. Consequently, you should
release the building units in the source system prior to executing the transport. You could then run the release program in test mode in
the target system to check the result of the transport.
Features
Selection Screen
You can further restrict the building unit data to be transported by using the following selection criteria on the program selection screen:
Building unit identification key
Creation date
Date of last change
Note
PUBLIC
Page 34 of 75
The selection criteria are linked by an AND operator. Thus if you enter an interval for building unit creation and change, the
transport will include those building units that were created and changed within the specified time frame.
If, however, you want to select all of the building units that were created or changed within a given period, you must run the
program twice: once specifying the creation interval and a second time specifying the change interval. For this reason there may
be duplicate entries in the request. These do not represent a problem.
The following data is included in the transport request:
Long text for the comment field
Building units flagged for deletion
This ensures that the flag is passed on to the target system.
Moreover, the following entries are included in the transport request if the key of a building unit appears directly in one of the dependent
tables:
The entries for the following that belong to the building units selected
Building hierarchy
Planning characteristics
Facility characteristics
Assignment to organizational units
Doors
Specifications for Program Execution
You can execute the program for transporting building units in test mode or live mode.
If you run the program in test mode, the system selects the building units to be transported and checks whether they would be
successfully included in the transport request in live mode. However, the objects to be transported are not actually included in the
transport request.
To run the program in test mode, select Test Mode.
Even if you have selected Test Mode, you must select or create a transport request. There is no test mode for creating a request.
If you run the program in update mode, the system selects the building units to be transported.
To run the program in update mode, deselect Test Mode.
Activities
See Transporting Building Units
1.1.4.3.6.1 Transporting Building Units

Procedure
From the SAP Easy Access screen, choose Hospital Statistics/Information Report Tree Basic Data Hospital Structure ISH: Transport Building Units .
The IS-H: Transport Building Units screen appears.
2. Specify the institution and further selection criteria. Also specify whether you want to run the program in test or live mode.
3. Choose
(Execute).
The Prompt for Workbench Request dialog box appears Enter a request number, and then choose
(Continue).
The program outputs the following data:
Number of the transport request
Number of the task
Number of records included per table
1.
More Information
Transport Building Units
1.1.4.4 Maintain Building Units for Care Unit Graphic

If you want to use the care unit overview graphic in Care Unit Management, you have to specify the dimensions and the location of the
building units within the care unit in the building unit master data.
The graphical representation of a care unit and of the building units assigned to it is based on a right-angled, integer coordinate system
where one unit corresponds to one meter. The origin of the coordinate system is at the lower left. The x-axis extends to the right of and
the y-axis extends upwards from the origin. The position of a point in the coordinate system is specified by its x and y coordinates (x,y).
More Information
Planning the Graphical Representation of the Care Unit Structure
PUBLIC
Page 35 of 75
Example of Care Unit Aligned with SAP Coordinate System

Rooms in the Care Unit Overview Graphic
Corridors in the Care Unit Overview Graphic
Doors in the Care Unit Overview Graphic
1.1.4.4.1 Planning the Graphical Representation of the Care

Unit Structure
You can define that the care unit structure is to be displayed as a graphic in the system.
Process
If you want to specify the care unit structure to be represented in graphical form in the system, you should work through the following
preliminary steps:
1. Make the floor plan of the care unit as abstract as possible.
Do not try to reproduce the exact floor plan of a care unit in the system. Instead, make a sketch of the care unit, which should reflect
the proportions of the rooms in relation to each other. Rooms to which no bed locations are assigned can, however, be scaled down.
In this way, more space is available for displaying rooms with bed locations and the patients assigned to them.
2. Set the angle of view on the care unit.
Since the width of the screen display is usually greater than its height, you should adjust the care unit to this format.
The care unit overview graphic should reflect the care unit as seen by the staff who work there. This is generally the view from the
nurse station.
3. Map the care unit in the SAP coordinate system.
Map the care unit in the SAP coordinate system. You do not have to align the lower left corner of the care unit with the origin of the
coordinate system. You can specify the lower left corner of the unit at any point greater than (0.0). Coordinates of the unit may not
exceed 999.
Note
If you do not define the lower left corner of the care unit as the origin, you will be able to extend the station along the x or y axis at
a later date, without having to change coordinates which have already been defined.
Define the appropriate room dimensions.
You should keep the room dimensions as small as possible. Rooms with bed locations must be large enough to accommodate the
required number of bed locations.
For more information about this, see Rooms in the Care Unit Overview Graphic.
5. Define corridors.
Orientation in the care unit overview graphic is facilitated if you represent corridors in the system. You should also make a point of
including corridors with many corners.
For more information about this, see Corridors in the Care Unit Overview Graphic.
6. Define room and corridor doors.
You should include room and corridor doors when planning the care unit overview graphic, since they support orientation in the
graphic.
For more information on room and corridor doors, see Doors in the Care Unit Overview Graphic.
4.
More Information
Example of Care Unit Aligned with SAP Coordinate System
1.1.4.4.2 Example of Care Unit Aligned with SAP Coordinate

System
The following illustration is an example of a care unit aligned with the SAP coordinate system.
PUBLIC
Page 36 of 75
To represent rooms and corridors in a care unit, you have to specify the x and y coordinates and the length (y-direction) and width (xdirection) for a building unit.
The rooms and corridors outlined in the above representation are defined with the following coordinates:
Building Unit
(x,y)
Width (x-axis)
Length (y-axis)
R11
(2,2)
4
3
R12
(6,2)
R13
(13,2)
R14
(13,6)
R15
(10,9)
R16
(6,8)
R17
(2,8)
C01
(2,5)
C02
(10,2)
The dimensions of bed locations are predefined in the system (2x2 m). Consequently, you specify the position of bed locations only as
a point in the coordinate system whose origin is in the lower left corner of the room or corridor to which the bed location is assigned.
The bed locations outlined in the above representation are defined with the following coordinates:
Bed Location
(x,y)
Bed 111
(0,0)
Bed 112
(2,0)
Bed 131
(2,2)
Bed 132
(0,0)
Bed 133
(2,0)
Bed 141
(0,3)
Bed 142
(2,3)
Bed 143
(0,0)
Bed 144
(2,0)
Bed 161
(0,1)
Bed 162
(2,1)
Bed 171
(0,1)
Bed 172
(2,1)
The room door dimensions are predefined in the system (1 meter). Consequently, you specify the location of room doors only as a
point in the coordinate system whose origin is the lower left corner of the corridor on which the door is located.
The room doors outlined in the above representation are defined with the following coordinates:
PUBLIC
Page 37 of 75
Room Doors
R11/C01
(x,y)
(2,0)
R12/C01
(6,0)
R16/C01
(6,3)
R17/C01
(2,3)
R13/C02
(3,2)
R14/C02
(3,6)
R15/C02
(1,7)
1.1.4.4.3 Rooms in the Care Unit Overview Graphic

You specify the location of rooms as a point (x,y) and its extension along the x-axis (room width) and y-axis (room length) in the
coordinate system of the care unit. Rooms are always rectangular.
Up to 70 rooms can be displayed in the care unit overview graphic. Rooms comprise all rooms and corridors of a care unit. If a care unit
contains more than 70 rooms, you can no longer display the care unit overview graphic. The system issues an error message to this
effect when you call the care unit overview graphic.
Room Type
Tips on Creating Care Unit Graphic
Rooms with Bed Locations
Always keep rooms as small as the required number of bed
locations will allow. Larger rooms result in unused spaces within
the graphic. A bed always measures 2x2 m. If a private room
actually measures 6x5 m, it is recommended to make the
minimum dimensions in the care unit graphic 2x2 m or 3x2 m. The
same applies to corridors with bed locations.
Rooms Without Bed Locations
To free up as much space as possible for displaying patient data

in the care unit overview graphic, you should downscale rooms
without bed locations (e.g. utensil rooms, WCs) in comparison with
sick rooms.
1.1.4.4.4 Corridors in the Care Unit Overview Graphic

You specify the location of corridors as a point (x,y) and its extension along the x-axis (corridor width) and y-axis (corridor length) in the
coordinate system of the care unit. A corridor can only be a rectangle or a quadrilateral. To represent corridors with many corners in the
system, you have to split the corridor into rectangular or quadrilateral components and create each component as a separate corridor
in such a way that that when joined together these components make up the complete corridor.
Corridor Dimensions
You should keep the dimensions of corridors to the strict minimum. If the corridor provides for bed locations (e.g. for overflow beds), you
have to dimension the corridor so that it can accommodate the bed locations. A bed location always measures 2x2 m.
If you want to define 2 overflow bed locations in a corridor, the corridor must measure at least 2x4 m or 4x2 m.
Two Care Units in One Corridor
You cannot assign several care units to one corridor. If two care units share the same corridor, you have to define the corridor twice in
the system (under two different identification keys). You then assign the corridor and the care unit rooms to each care unit.
Note
Up to 70 rooms can be displayed in the care unit overview graphic. Rooms comprise all rooms and corridors of a care unit. If a care
unit contains more than 70 rooms, you can no longer display the care unit overview graphic. The system issues an error message to
this effect when you call the care unit overview graphic.
1.1.4.4.5 Bed Locations in the Care Unit Overview Graphic

The dimensions of bed locations are predefined in the system (2x2 m). You situate a bed location by defining its point in the coordinate
PUBLIC
Page 38 of 75
system. Here it is assumed that you are using the coordinate system of the room to which the bed location is assigned. The origin of the
coordinate system is the lower left corner of the room.
Note that the greater the number of bed locations, the less suitable they become for the graphical display. If you reduce the display
window below a specific minimum size, the system simply displays the patients name in the place of the bed location to which one
patient is assigned. Bed locations to which several patients are assigned are displayed normally.
Note
Up to 70 bed locations can be displayed in the care unit overview graphic. If a care unit contains more than 70 bed locations, you
can no longer display the care unit overview graphic. The system issues an error message to this effect when you call the care unit
overview graphic.
1.1.4.4.6 Doors in the Care Unit Overview Graphic

Note
You only have to maintain room and corridor doors if you want to use the care unit overview graphic of Care Unit Management.
Doors facilitate orientation in the care unit overview graphic. You can store the following doors:
Doors between rooms and corridors (room doors)
The system displays a room identification plate only if you have created room doors. The room identification plate displays the
identifier of the room.
Doors in the corridors (corridor doors)
You can create corridor doors in a corridor or between two corridors. There are no room identification plates for corridor doors in the
care unit overview graphic. It is, however, useful also to represent existing corridor doors in the care unit overview graphic, since
these space dividers help you to find your way around the graphic.
Features
You define room doors in relation to the room, corridor and care unit. You define corridor doors in relation to the corridor and the care
unit.
You specify the location of the door as coordination in relation to the corridor. This has the advantage that the position of the doors is
changed automatically if you alter the position of corridor within a care unit. You may need to adjust the position of the doors only if you
change the dimensions of a corridor. For more information on this, see Define the Location of Room and Corridor Doors.
Note
Up to 140 doors can be displayed in the care unit overview graphic. If a care unit contains more than 140 doors, you can no longer
display the care unit overview graphic. The system issues an error message to this effect when you call the care unit overview
graphic.
Activities
See Maintaining Doors
1.1.4.4.6.1 Define the Location of Room and Corridor Doors

You always use coordinates to specify the location of a door in relation to the corridor and not the complete care unit. All coordinates
must be positive integers.
Prerequisites
The width of a door is predefined in the system as one meter. You specify the location of a door as a point in relation to the lower left
corner of the corridor.
The maintenance of the coordinates differs depending on whether you want to specify the location of room doors or corridor doors.
Features
Location of Room Doors
To define a door between a room and a corridor, you specify the point in the corridor where the door is located in relation to the
PUBLIC
Page 39 of 75
coordinate system defined by the corridor. The system displays a one meter wide door at this point in the care unit overview graphic.
Example: Location of Room Doors
The illustration shows a corridor of width 10 (x-axis) and length 3 (y-axis) with adjoining rooms. The room doors have the following
coordinates:
Room Door Coordinates
Door Between Corridor and
Point (x,y)
Room R1
(3,3)
Room R2
(7,3)
Room R3
(10,0)
Room R4
(8,0)
Room R5
(4,0)
Room R6
(0,0)
Note
The room door specified by point (0,0) could also be the door of a room at the end wall of the corridor. Since you always define
room doors in relation to the corridor and the room, it depends on the location of the room whether a door defined by the point (0,0)
results in an opening along the x-axis or the y-axis.
Location of Corridor Doors

Corridor doors always extend across the complete width or length of a corridor. In the case of rectangular corridors, it depends on the
alignment of the corridor in the coordinate system whether it is expedient to define vertical or horizontal doors.
The following illustrations show examples of aligning rectangular corridors.
PUBLIC
Page 40 of 75
For corridor 1, it is expedient to define vertical doors.

For corridor 2, it is expedient to define horizontal doors.
To define vertical doors for a corridor, specify a point on the x-axis, for example (1,0), (2,0), (3,0).
To define horizontal doors for a corridor, specify a point on the y-axis, for example (0,0), (0,1), (0,2), (0,3).
Caution
Note that the point (0,0) defines a horizontal door. A special rule applies for vertical doors at the origin. To define a vertical door at
the origin, you must specify the coordinates that determine the dimensions of the corridor. You specified these in the master data of
the corridor. In the coordinate system, this is the point in the upper right corner of the corridor.
An example illustrates how to define horizontal and vertical doors.
1.1.4.4.6.2 Examples of Vertical and Horizontal Doors

The illustration shows the alignment of two corridors within a care unit.
The doors of the corridors are defined with the following coordinates:
Corridor
Door
Corridor 1
Door 1
Coordinates
(0,9)
Corridor 1
Door 4
(0,0)
Corridor 2
Door 2
(7,3) => vertical door at origin
Corridor 2
Door 3
(7,0)
1.1.4.4.6.3 Maintaining Doors

Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Doors
Maintain ..
The rooms and corridors for which you have already defined doors are listed. All care units including the corridors and the adjoining
building unit with x- and y-coordinates are displayed.
Create New Entries
1.
PUBLIC
Page 41 of 75
Create New Entries

1. Choose New Entries.
The New Entries: Details of Added
Entries screen appears.

(Details).

Select the entry you want to delete.
1. To create a room door, specify the

Make any necessary changes to the
identification key of the corridor and of coordinates.
the room that are to be joined by a
door. Also specify the identification key
of the care unit to which the room is
assigned.
2. Maintain the coordinates of the room
door.
3. To create a corridor door, specify the
identification key of the corridor both in
the Corridor field and the Room field.
Also specify the identification key of
the care unit to which the corridor is
assigned.
4. Maintain the coordinates of the
corridor door.
For more information about room doors
and corridor doors, see Define the
Location of Room and Corridor Doors.
Choose
(-).
The system deletes the entry.
Save the data.

Save the data.
Save the data.

1.2 Business Partner

The Business Partner component includes persons or entities with which your institution maintains business relations.
A business partner can assume the following functions:
Other hospital
Insurance provider
Patient's employer
Physician
Employee of the hospital
Customer (self-payer, for example)
External ordering party (country version Switzerland)
Fee recipient (country version Switzerland)
Integration
Select this component if you wish to
Map insurance relationships (and for components that make use of these, such as copayment or invoicing)
Store transfers from or to other hospitals
Document attending, referring or postdischarge physicians.
To map business transactions with customers in Financial Accounting (FI), you must also select the Accounts Receivable Accounting
component under Financial Accounting.
Features
PUBLIC
Page 42 of 75
For Information On
Introduction
See
Business Partner Concept
Business Partner Identification Key
Business Partner Search
Creation of Business Partners: Strategies
General business partner and business partner functions
General Business Partner Data

Creating General Business Partners
Business Partner Functions
Creating Business Partner Functions
Business Partner Administrative Data
Blocking Business Partners
Displaying the Blocking Interval of the Business Partner
Unblocking Business Partners
Flagging Business Partners for Deletion
Cancelling the Deletion Flag for Business Partners
Evaluations
Determine Insurance Providers Without Customers

Determination of IS-H Customers Without FI Customers
1.2.1 BAPIs for Business Partners

Interfaces for maintaining business partner data in the IS-H system
The following BAPIs (Business Application Programming Interface) and APIs are available to you for maintaining business partner data:
BAPI
Use
BAPI_BUSPARTNER_GETLIST
This method lets you determine business partners that assume
the General Business Partner function.
BAPI_BUSPARTNER_GETLISTCUST

the IS-H Customer function.
BAPI_BUSPARTNER_GETLISTTEMPL

the Employer function.
BAPI_BUSPARTNER_GETLISTHOSP

the Hospital function.
BAPI_BUSPARTNER_GETLISTINSPROV

the Insurance Provider function.
BAPI_BUSPARTNER_GETLISTPERSON

the Person (Physician/Employer) function.
BAPI_BUSPARTNER_GETDETAIL
You use this method to determine all existing data for a business
partner including all available role data.
BAPI_BUSPARTNER_CREATE
This method lets you create a business partner that assumes the
General Business Partner, IS-H Customer, Employer, Hospital,
Insurance Provider or Person function.
BAPI_BUSPARTNER_CHANGE
This method lets you change a business partner that assumes the
General Business Partner, IS-H Customer, Employer, Hospital,
Insurance Provider or Person function.
More Information
You'll find more information about the BAPIs in the documentation for the individual BAPIs in the BAPI Explorer (transaction BAPI). For
general information and descriptions of the BAPIs see the Interface Repository at http://ifr.sap.com.
1.2.2 Business Partner Concept

You can store persons or entities with which your institution maintains business relationships in the IS-H System. You can maintain the
relationship of a patient or a case to a person or an entity by creating a reference to the corresponding business partner master record.
Since the relationships business partners can have to your institution can be of several types, you create a business partner function for
PUBLIC
Page 43 of 75
each type of relationship. For instance, a health insurance company exists in the functions Insurance Provider and Customer.
The following business partner functions are available in the IS-H System:
Employer
Insurance provider
Customer
Hospital
Employee/external physician
External ordering party (country version Switzerland)
Fee recipient (country version Switzerland)
You store data that is specific to a function (e.g. bank details for the Customer function) in the corresponding business partner functions.
You store data that is valid for the business partner, irrespective of the specific function this partner performs, as general business
partner data.
You can also store a person or an entity without a specific function as a business partner in the system. In this case, you only maintain
the name and address data in the general business partner data.
1.2.3 Business Partner Identification Key

A business partner is defined by means of a unique identification key.
The identification key of a business partner can be assigned by the system (internal number assignment), or you can assign it yourself
(external number assignment). In Customizing for IS-H, you can specify which of these two assignment methods is to be used. You can
either use only internal number assignment, only external number assignment, or both types of number assignment. In Customizing, you
can also define the number range authorized for internal and external number assignment.
The system ensures that unique identification keys are always assigned. With internal number assignment, the system always selects
the next number from the internal number range. With external number assignment, the system prevents a number, which is already
assigned, from being assigned again.
Number Ranges for Each Function
A business partner along with its roles is managed within the system by means of a unique identification key. However, you define a
number range for the general business partner and for each function in Customizing for IS-H. These number ranges can, but need not be
identical.
For instance, to manage insurance providers with identification keys from a particular number range and hospitals with identification
keys from a different number range, you define a separate number range for each role. You then have to create the business partners
using their roles and not as a general business partner in order for you (or the system) to assign an identification key from the required
number range.
Integration
Particularities with Insurance Providers and Customers
You should define a common number range for insurance providers and customers. Since insurance providers usually also exist as
customers, it is not recommended to divide the identification keys into two separate number ranges.
When you create an IS-H customer, you can have the system automatically create the corresponding IS-H customer in Financial
Accounting in the background. For this to be possible, you need to have set up external number assignment for the creation of
customers in Customizing for Financial Accounting.
If you want to ensure that the identification key of the FI customer is identical to that of the business partner, the number interval of the
external number range in Financial Accounting must comprise the business partner number range.
The type of number assignment and the valid number range for a customer master record in Financial Accounting are determined using
the account group.
For more information about number ranges, see the Financial Accounting Implementation Guide and the IS-H Implementation Guide.
1.2.4 Business Partner Search

The business partner search allows you to determine existing business partners for processing or displaying. Before creating a
business partner, you should check whether the business partner in question already exists in the system. This minimizes the risk of
entering the same business partner more than once.
Example
The duplicate entry of an insurance provider, for example, would result in two customer master records being created for this
insurance provider and, consequently, two accounts in Financial Accounting. This would make for incorrect results in sales
evaluations.
PUBLIC
Page 44 of 75
Features
Search terms are available on the initial screen of the function for editing the general business partner or the business partner functions.
The business partner search returns a list of the business partners that match the search terms specified. If you call the business
partner search from the initial screen of a business partner function in change or display mode, the system only lists the business
partners that exist in this function. If you call the business partner search from the initial screen of a business partner function in create
mode, the system lists all of the business partners that satisfy the search criteria. In this way you can determine whether the business
partner to be created already exists in a different business partner function.
For more information about the result of the search, see Business Partner List.
1.2.5 Business Partner List

The business partner list is the result of the business partner search (list of business partners found in the system).
The list displays the following data:
Name 1 and name 2 or last name and first name
Address
Company Code
If the business partner performs the Customer function, the system displays the company code in which the customer is managed.
Specification of business partner functions
The system displays the business partner functions which the business partner performs. The abbreviations denote the following
functions:
G: General business partner
P: Person
IP: Insurance provider
D: Customer
A: Employer
Ho: Hospital
The system selects (X) the field(s) corresponding to the function(s) performed by a business partner.
If a business partner function or the general business partner is flagged for deletion, the system displays a hyphen (-) in the
corresponding field.
Business partner identification key
Blocking interval
If a business partner is blocked, the system displays the blocking interval in a second line.
1.2.6 Creation of Business Partners: Strategies

You can use different strategies for creating business partners:
Create business partners in a specific function
Business partners which have a specific relationship to your institution are best created directly in this function. In this case, maintain
both the function-independent and the function-specific data of this business partner. When you save the data, the system creates the
business partner function and the general business partner.
Create a general business partner, and create business partner functions at a later date
You can first create a business partner simply as a general business partner. You store the name and address data within the
general business partner data.
To represent the relationships the business partner maintains with your institution, you subsequently create one or more functions for
this business partner.
If you create a further business partner function for an existing business partner, the system proposes the existing functionindependent data of the business partner as default values.
Create general business partners only
You create business partners which have no particular function with regard to your institution exclusively as general business partners.
More Information
PUBLIC
Page 45 of 75
1.2.6.1 General Business Partner Data

The system stores data that is valid for a business partner irrespective of its function within the general business partner data.
You maintain the general business partner data when maintaining:
The general business partner
A business partner function
The general business partner data comprises the following data:
Names
Address and communication data
Blocking date
External partner number
The 15-figure external partner number lets you store an alphanumeric key that uniquely identifies the business partner in an external
system. You can implement checks on the external partner number in the Business Add-In (BAdI) IS-H: Check General Business
Partner Data (ISH_BP_CHECK) without having to modify the standard program code.
More Information
1.2.6.2 Creating General Business Partners

You can create a business partner without assigning a function to it.
Procedure
1.
2.
3.
4.
5.
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners General Create .
The Create Business Partner: Initial Screen appears. Business Partner is selected by default in the Function group box.
First use the business partner search to check that the business partner does not exist in the system. Under the Search Criteria
group header, enter the name, and then choose
(Display).
If you are working with external number assignment, specify the identification key of the business partner, and then choose
(Create).
If you are working with internal number assignment, choose
(Create). The system assigns an identification key to the business
partner when you save the business partner data.
The Create Business Partner: Address Data screen appears. The system transfers the data you specified as search criteria on the
initial screen into the entry screen.
Maintain the name and address data of the general business partner.
Then save the data.
1.2.6.3 General Business Partner: Initial Screen

Business Partner Search
To find a business partner in the system, specify the search criteria in the corresponding fields, and then choose ENTER.
Note
The business partner search corresponds largely to the general patient index search. For more information about this, see Business
Partner Search.
The system outputs a list of business partners as a result of the search. Choose (double-click) the required business partner if it
appears in this hit list.
If the business partner does not yet exist in the IS-H database, you can create the business partner.
Business Partner Identification Key Assignment
The identification key of a business partner can be assigned by the system (internal number assignment), or you can assign it
yourself (external number assignment).
If you are working with internal number assignment, leave the Business partner field blank and choose ENTER. The system
automatically assigns a unique identification key when you save the data.
If you are working with external number assignment, enter the required identification key in the Business partner field and choose
PUBLIC
Page 46 of 75
ENTER.
Creating with Template
You can specify the identification key of an existing business partner in the Business Partner field under the Copy From group header.
The system proposes the data of this reference business partner on the entry screen of the new business partner. Note that if a
comment was entered for this reference business partner, it will also be copied into the new business partner.
Function of the Business Partner
On the entry screen for maintaining the general business partner, you can specify which business partner functions you would like to
maintain. This general business partner is flagged by default. This, however, is only a default value. You can change this setting.
Display or Change Business Partner
If you want to display or change existing business partners, you simply have to specify the identification key of the required business
partner. If you do not know the identification key, you can determine it by means of the business partner search.
1.2.6.4 General Business Partner: Entry Screen

You store the names, address, phone, telex and fax number of the business partner on the entry screen. The following documentation
explains the features of the various fields.
Features
Business Partner Names
If the business partner is a natural person, enter the patients name in the Name and First name fields.
If the business partner is a legal entity, enter the name in the Name, 2nd name and 3rd name fields.
You characterize a general business partner as a natural person by selecting Pers.ind. If this indicator is not set, the business partner is
considered to be a legal entity.
The system proposes the name of the business partner as the business partner short name. You may change this specification. The
short name is one of the search criteria you can specify for the business partner search when maintaining business partner data on the
initial screen of the transaction.
Business Partner Address
You also store the country and language of the business partner within the address data. You can store default values for this data by
setting system parameters in customizing for IS-H.
Comment
You can store detailed comments on a business partner in the Comment field. If the length of this field in the entry screen is not
sufficient, you can branch to the text editor and store a long text. To do this, choose Create Long Text.
Note
By means of the SAP enhancement NG200002 customer exit EXIT_SAPMNG10_002 you can implement customer-specific
checks after the general program checks have run when processing the person data of the general business partners.
By means of the SAP enhancement NGPACONC EXIT_SAPLN003_001, you can modify how the name string is created from the
business partner data. This enhancement is provided in function module ISH_NGPA_CONCATENATE.
For information about this, read the documentation on the enhancements and on the function module exits. For more information,
see Enhancements to the SAP Standard.
1.2.7 Blocking Business Partners

You can block business partners you no longer want to use at given times or as of a specific date. Blocking a business partner blocks
both the general business partner and its business partner functions. You cannot assign blocked business partners to patients or cases
within the blocking interval. Existing assignments are not affected by blocking the business partner.
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partner General Change .
The Change Business Partner: Initial Screen appears. Business Partner is selected by default in the Function group box.
2. Specify the identification key of the business partner, and then choose
(Display). Alternatively, determine the business partner
1.
PUBLIC
Page 47 of 75
3.
4.
5.
6.
7.
using the business partner search, and then choose the required record from the resulting hit list.
The Change Business Partner: Address Data screen appears.
Choose
(Record Information).
The Change Business Partner: Record Info Screen of the general business partner appears.
Specify the blocking start and end dates. If you want to block a business partner for an indefinite period as of a specific date, enter
12/31/9999 in the Blocked to field.
In the Block. reason field, you can enter a text of any length which explains why the business partner is blocked. If the input field is not
long enough, go into the SAPscript text editor by choosing (-).
To return to the general business partner data, choose
(Back).
Save the data.
You return to the initial screen of the function.
More Information
Displaying the Blocking Interval of the Business Partner
1.2.8 Unblocking Business Partners

You can unblock business partners you have blocked as of a specific date or for a given interval.
Procedure
1.
2.
3.
4.
5.
6.
Specify the identification key of the business partner, and then choose
Choose
The record information screen of the general business partner appears.
Delete the blocking start and end dates. You do not need to delete an existing comment. The system deletes it automatically when
you save the changed data.
To return to the general business partner data, choose
(Back).
Save the data.
1.2.9 Displaying the Blocking Interval of the Business Partner

You can display the duration for which the business partner is blocked.
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners General Display .
The Display Business Partner: Initial Screen appears. Business Partner is selected by default in the Function group box.
The Display Business Partner: Address Data screen appears.
3. Choose
The record information screen of the general business partner appears.
4. The system displays the blocking start and end dates and the blocking reason. If the Blocked from and Blocked to fields are blank,
the business partner is not blocked.
1.
1.2.10 Deletion of Insurance Providers

The system does not support the direct deletion of business partners, since this could result in data inconsistencies. For instance, you
might delete an insurance provider that is still assigned to a current case by means of an insurance relationship.
At present, it is only possible to delete business partners which perform the insurance provider function. Consequently, you can also
delete insurance providers if they also perform the Customer function and have a corresponding customer in Financial Accounting.
PUBLIC
Page 48 of 75
Process
You can delete either the Insurance provider function alone, or also the general business partner together with the Customer function of
the business partner, if this exists. The customer in Financial Accounting is not deleted in the process.
To do this, carry out the following two activities:
1. Flagging Business Partners for Deletion
If you want to delete an insurance provider, set the deletion flag for this business partner (i.e. for the general business partner and its
functions). Flagging a business partner for deletion does not restrict its use in subsequent functions.
Note
Business partners that are flagged for deletion are no longer displayed as possible values for input in subsequent functions. If,
during the patient admission procedure, you want to assign a physician to a case as the family physician, physicians who are
flagged for deletion are no longer displayed when you choose POSSIBLE ENTRIES on the Family physician field.
If you want to prevent the business partner from being used at all, you also have to block the business partner.
2.
Deleting Insurance Providers Flagged for Deletion

You can use a deletion program to delete the insurance providers that are flagged for deletion, provided the insurance provider has
no dependent data.
More Information
Displaying Business Partners Flagged for Deletion
1.2.10.1 Flagging Business Partners for Deletion

You can flag business partners for deletion. Note that there are no restrictions on the use of business partners that are flagged for
deletion. If you want to prevent a business partner from being used, you have to block the business partner in question. For information
about this, see Blocking Business Partners.
Note
Although you can set a deletion flag for all business partners, only business partners that perform the Insurance provider and
Customer functions can at present be physically deleted.
Procedure
1.
2.
3.
4.
5.
6.
Specify the identification key of the business partner, and then choose
(Change). Alternatively, determine the business partner
Choose Bus. partner-general Delete Set deletion flag .
A dialog box appears.
Choose
(Continue) to confirm that you want to set the deletion flag.
Another dialog box appears.
Confirm that the deletion indicator should be set for all functions of the business partner by choosing (Continue).
The system sets the deletion indicator and issues a corresponding message in the status line.
Save the data.
More Information
Deleting Insurance Providers Flagged for Deletion
1.2.10.2 Displaying Business Partners Flagged for Deletion

To determine whether a business partner has been flagged for deletion, proceed as follows:
PUBLIC
Page 49 of 75
Procedure
3. Choose
The Display Business Partner: Record Info Screen appears.
4. If the business partner is flagged for deletion, Deletion flag is selected.
1.
More Information
1.2.10.3 Cancelling the Deletion Flag for Business Partners

You can cancel the deletion flag you have set for a business partner.
Procedure
(Change). Alternatively, determine the business partner
3. Choose Bus. partner-general Delete Cancel deletion flag .
The system cancels the deletion flag and issues a corresponding message in the status line.
4. Save the data.
1.
1.2.10.4 Deleting Insurance Providers Flagged for Deletion

Prerequisites
You can delete business partners which perform the Insurance provider or Customer functions. You can delete these business
partners only if the following conditions are satisfied:
You have flagged the insurance provider for deletion.
The business partner has no dependent data.
Note that canceled data that has a reference to the business partner is also dependent data.
Note
You want to delete an insurance provider that was used in insurance relationships. Even if you have canceled these insurance
relationships, the reference from the insurance provider to these canceled data records remains, thus preventing you from deleting
this insurance provider.
Procedure
From any screen, choose System Services Reporting .
The ABAP: Program Execution screen is displayed.
2. Enter RNUKTR01 as the program name and choose
(Execute).
The IS-H: Delete Insurance Providers screen appears.
3. Specify the selection criteria.
To delete the selected insurance providers immediately, deselect Test mode.
If you simply want to check whether the selected insurance providers can be deleted and output a corresponding log, select Test
mode.
4. Choose
(Execute).
If you executed the program in test mode, the system issues a check log.
If you executed the program in update mode, the system deletes the business partners or the selected business partner functions
immediately.
1.
PUBLIC
Page 50 of 75
Note
Please refer to the documentation for program RNUKTR01.
1.2.10.5 Deletion of Insurance Providers: Selection Criteria

You can select insurance providers for deletion as follows:
By specifying the insurance provider type
By specifying the identification key of the insurance provider
All specified insurance providers that are flagged for deletion are selected.
Note
Insurance providers, for which the general business partner but not the insurance provider function is flagged for deletion, are not
selected.
Features
You can influence the processing mode of the program as follows:
Delete Business Partner
You can delete either only the Insurance provider business partner function, or the complete business partner. To delete the entire
business partner, set the Delete Business Partner? indicator.
Provided the business partner does not perform any functions other than that of insurance provider, the system deletes the complete
business partner.
If the business partner performs both the Insurance provider and the Customer functions, you have to delete the customer as well (see
below).
Delete Customer
If the Customer function exists for the insurance provider as well, you can also delete the customer. To do this, set the Delete
Customer? indicator. If, in addition to the customer in the IS-H System, the corresponding customer exists in Financial Accounting (FI),
the system deletes the Customer business partner function only if you have also flagged the customer in Financial Accounting for
deletion.
Display Details
Prior to deleting an insurance provider, the system checks whether data exists in the system that is referenced to this insurance
provider. If you want to display the details of these checks, select Display details?
Test Mode
You can execute the deletion program in test mode. The system does not delete business partners in test mode. It simply displays
which of the selected business partners can and cannot be deleted. To do this, set the Test Mode indicator.
If this indicator is not selected, the system executes the program in update mode. The business partners are then deleted immediately.
Activities
For more information, see Deleting Insurance Providers Flagged for Deletion.
1.2.11 Display of Business Partner Administrative Data

Administrative data provides details on when and by whom a business partner was created, changed or flagged for deletion. The
system stores this data separately for the general business partner and the business partner functions.
The administrative data also contains the deletion flag and the blocking dates for the business partner.
Activities
Displaying the Administrative Data of General Business Partners
Displaying the Administrative Data of Business Partner Functions
PUBLIC
Page 51 of 75
1.2.11.1 Displaying the Administrative Data of General

Business Partners
Procedure
3. Choose
The Display Business Partner: Record Info Screen appears.
4. Here the system displays the administrative data for the general business partner in the User Data group box.
1.
1.2.12 Business Partner Functions

Role or function of a business partner which the latter performs in the IS-H System.
In addition to general business partner data, you can store function-specific information.
Whenever you call a business partner via its business partner functions, the system displays both the function-specific data and the
function-independent data of the general business partner. The following topics explain the particularities of function-specific data. For
more information about function-independent data, see General Business Partner: Entry Screen.
You can maintain the following functions of a business partner:
Employer (Business Partner Function)
Insurance Provider (Business Partner Function)
IS-H Customer (Business Partner Function)
Hospital (Business Partner Function)
Employee/Physician (Business Partner Function)
External Ordering Party (Business Partner Function) [CH]
Fee Recipient (Business Partner Function) [CH]
All business partner functions with the exception of the IS-H customer are valid for all institutions of a given client. IS-H customers are
only valid for one institution.
More Information
1.2.12.1 Displaying the Administrative Data of Business

Partner Functions
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners <Business Partner Function>
Display .
The initial screen of the selected business partner function appears.
The entry screen appears.
3. Choose
The record information screen of the selected business partner function appears.
4. Here the system displays the administrative data for the business partner function in the User Data group box. The administrative
data of the general business partner is displayed in the General Business Partner Data group box.
1.
Note
If the deletion flag is set here, this means that the business partner function is flagged for deletion. The deletion flag does not
necessarily also apply to the general business partner or other functions of the business partner.
PUBLIC
Page 52 of 75
Note
You can also call business partner functions by means of the display or maintenance transactions of the general business partner.
To do this, on the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners General
Change or Display, and then select the business partner function you want to call on the initial screen.
1.2.12.2 Creating Business Partner Functions

If you want to create a business partner in a specific function, you have to distinguish between the following two situations:
Creating a business partner function in cases where the business partner does not yet exist in the system
Creating a business partner function in cases where the business partner already exists as a general business partner
The appropriate procedure to use in each of these situations is described below.
Procedure
General Business Partner of the Business Partner Function Does Not Yet Exist
1.
2.
3.
4.
5.
Create .
The Create <Business Partner Function>: Initial Screen appears.
Check that the business partner is not already defined in the system by means of the business partner search.
(Create).
(Create).
The address data screen of the business partner appears.
Maintain the address data and the function-specific data.
A second entry screen exists for the business partner functions Insurance Provider, Customer and Employee/Physician. To reach
the second entry screen, choose Other indicators.
Save the data.
Business Partner Exists as General Business Partner

Create .
The Create <Business Partner Function>: Initial Screen appears.
2. Specify the identification key of the business partner for which you want to create the business partner function, and then choose
(Create).
If you do not know the identification key, determine the business partner using the business partner search, and then choose the
required record from the resulting hit list.
3. Maintain the address data and the function-specific data.
A second entry screen exists for the business partner functions Insurance Provider, Customer and Employee/Physician. To reach
the second entry screen, choose Other indicators.
4. Save the data.
1.
Note
Alternatively, you can create a specific business partner function on the SAP Easy Access screen by choosing Hospital Basic
Data Administration Business Partners General Create . The initial screen of the function appears on which you select the
required business partner function under the Function group header. Then proceed as of step 2 above.
More Information
Creating IS-H Customers
1.2.12.3 Employer (Business Partner Function)

You can store patients employers as business partners in the IS-H System.
You store the employer of a patient within the patient master data. It is, therefore, practical to store employers which you expect to enter
PUBLIC
Page 53 of 75
frequently as business partners.

You can store the following function-specific data for the employer:
Identification Key of the Responsible Accident Insurance (WorkersCompensation Association)
In the Accident Ins.field, you can specify the identification key of the insurance provider with which the employer has accident insurance.
In Germany, this is the responsible workerscompensation association. The accident insurance must exist as a business partner which
performs the Insurance provider function. If you do not know the identification key, you can determine the insurance provider by
choosing the value help for this field.
The system displays the name and address of the accident insurance below the input field.
More Information
1.2.12.4 Insurance Provider (Business Partner Function)

Health insurance funds or companies with which patients are insured.
Example
Statutory health insurance funds or private health insurance companies
Workers' compensation associations
You have to create insurance providers used for patient- and case-related insurance relationships, treatment certificates and the
insurance verification procedure as business partners which perform the Insurance provider function.
For more information about insurance provider master data, see Insurance Provider-Specific Master Data.
For more information about creating business partners, see
1.2.12.4.1 Insurance Provider-Specific Master Data

You can store the following function-specific data for an insurance provider:
Insurance Provider Type
See Insurance Provider: Insurance Provider Type.
Tax Classification
If value added tax is to be calculated during the billing process, you need to have entered the tax classification value in the Tax Class.
field in the insurance provider master record.
In addtion, you need to specify the tax classification of the service in the service master. The system calculates the value added tax
using the combination of the insurance provider's tax classification and the service's tax classification.
Note
Value added tax can only be calculated if you have made the necessary system settings both in the standard SAP System and in
the IS-H System.
Currency
You can specify the currency of the insurance provider in the insurance provider master record. If you specify a currency other than
the local currency, the system does not at present convert to the foreign currency for invoicing. The amount invoiced is always output
in local currency.
Contact Person for Outpatient and Inpatient Cases
If you know the names of the clerks responsible for processing outpatient and inpatient cases on the insurance provider side, you can
store the corresponding contact persons in the insurance provider master record.
Specify the name of the agent handling inpatient cases in the Inpt.CPers. field.
Specify the name of the agent handling outpatient cases in the Outp.CPers. field.
Institute Indicator
To identify the insurance provider, you can store the insurance providers institute indicator in the Inst. Ind. field of the insurance
provider master. In Germany, the institute indicator is assigned by the Federal Office for Statistics.
Depending on how your system is configured, the system uses the institute indicator to identify the insurance provider when you
import the healthcare smart card and to compare the insurance provider master file of the Federal Association of Panel Physicians
with the insurance provider data in IS-H. The field that is used to identify the insurance provider is identified by the symbol (-).
PUBLIC
Page 54 of 75
See also Ins. Prov.: Relevant Fields for Importing Healthcare Smart Card
Health insurer number
To identify the insurance provider, you can store the health insurer number of the insurance provider in the HI Number field of the
insurance provider master. In Germany, this is, for example, the five-digit health insurer number assigned by the Deutscher
rzteverlag.
Depending on how your system is configured, the system uses the health insurance company number to identify the insurance
provider when you import the healthcare smart card and to compare the insurance provider master file of the Federal Association of
Panel Physicians with the insurance provider data in IS-H. The field that is used to identify the insurance provider is identified by the
symbol (-).
See also: Ins. Prov.: Relevant Fields for Importing Healthcare Smart Card
Health insurer number on the healthcare smart card
To identify the insurance provider, you can store the health insurer number as it appears on the insured person's healthcare smart
card in the HI No. HCSC field of the insurance provider master.
Depending on how your system is configured, the system uses the health insurance company number from the health insurance card
to identify the insurance provider when you import the healthcare smart card and to compare the insurance provider master file of the
Federal Association of Panel Physicians with the insurance provider data in IS-H. The field that is used to identify the insurance
provider is identified by the symbol (-).
See also: Ins. Prov.: Relevant Fields for Importing Healthcare Smart Card
Head Office
See Head Office.
Health Insurer Search Name
See Health Insurer Search Name.
Responsible panel physician association (Germany)
In the insurance provider master, you can store the responsible panel physician association for the insurance provider in the Resp.
PPA field. You must have created the panel physician association as an insurance provider in the system beforehand.
This entry is exclusively for informational purposes.
Additional Settings
See Control Parameters.
Group indicator
At present, the processing of insurance provider groups is not supported.
You can enter detailed comments on a business partner in the Comment field. If the length of this field in the entry screen is not
sufficient, you can branch to the text editor and store a long text. To do this, choose Create Long Text.
1.2.12.4.2 Insurance Provider: Insurance Provider Type

The insurance provider type is a criterion for grouping together insurance providers. You can use the insurance provider group as
follows:
Using the control parameters of the insurance provider type, you can specify the same function flows for all the insurance providers of
an insurance provider type. Examples of such function flows are copayment processing or insurance verification processing.
In Customizing for IS-H, you can make system settings in relation to the insurance provider type which affect insurance verification and
invoicing.
Note
You create insurance provider types in Customizing for IS-H. For each insurance provider type you set the parameters by means of
which you want to control the function flow. These parameters are institution-independent. If you manage several institutions in one
client, you cannot therefore maintain the insurance provider type parameters separately for each institution. For more information
about insurance provider types, see Define Insurance Provider Types, CH: Define Insurance Provider Types and SG, CA: Define
Insurance Provider Types in the IS-H Implementation Guide.
Procedure and Consequences

To assign an insurance provider to an insurance provider type, specify the insurance provider type in the IPType field in the insurance
provider master. As a result of this assignment, the system settings for the insurance provider type now apply to this insurance
provider.
This assignment also causes the system to propose the control indicators set for the insurance provider type for this insurance
provider. You can change these settings in the insurance provider master record.
Caution
If you assigned the insurance provider to an insurance provider type, the control parameters set for the insurance provider type do
not automatically apply to the insurance provider.
To make the control parameters set for the insurance provider type valid for the insurance provider, you have to set the IPT Ctrl
indicator (insurance provider type control) in the insurance provider master record.
If this indicator is not set, the system uses the control parameters of the insurance provider. For more information, see Insurance
Provider: Control Parameters.
PUBLIC
Page 55 of 75
1.2.12.4.3 Ins. Prov.: Relevant Fields for Importing Healthcare

Smart Card
Identification of the Insurance Provider
When you import a healthcare smart card, the system checks whether the insurance provider issuing the healthcare smart card exists in
the IS-H database. To do this, it compares the health insurance company number on the healthcare smart card with one of the following
numbers from the insurance provider master:
Business Partner Identification Key
Institute indicator (Inst. Ind. field)
Health insurance company number (HIC Number field)
Health insurance company number on healthcare smart card (HICNo HCSC field)
By setting a system parameter in Customizing for IS-H, you specify which of these numbers is used for identifying the insurance
provider. This setting applies to all insurance providers.
The field used for identifying the insurance provider is characterized by the icon (-) in the insurance provider master record.
Determination of Insurance Provider Branch Offices
When you import a healthcare smart card, the system determines the insurance provider(s) for which the number on the healthcare
smart card matches one of the above mentioned numbers in the insurance provider master. The system also checks if the identified
insurance provider is the head office. The system determines the branch offices assigned to each head office.
Branch offices are insurance providers for which you specified the identification key of the head office, in other words of the identified
insurance provider, in the Head Offce field of the insurance provider master.
Note
If you specified a head office in the insurance provider master, invoices are sent to the head office. However, if you want to bill the
insurance provider branch offices for charges incurred by cases, select HSC in the insurance provider master. If you set this
indicator, the system uses the head office specification only to be able to determine the branch offices of the insurance provider
when importing the healthcare smart card.
An example illustrates this.
For more information about importing the healthcare smart card, see the section entitled Configure Healthcare Smart Cards in the IS-H
1.2.12.4.4 Example: Head Office and Branch Determination at

Healthcare Smart Card Import
The following illustration shows how the system identifies insurance providers when you import an insured persons healthcare smart
card.
The example assumes that you have defined the HIC number field of the insurance provider master in Customizing for IS-H as the
comparison field for the comparison with the health insurance company number on the healthcare smart card.
PUBLIC
Page 56 of 75
The system determines the insurance provider as follows:

1. The system imports the healthcare smart card and determines all insurance providers in the IS-H database which have the health
insurance company number on the healthcare smart card in the HIC number field (here 1234).
This is insurance provider A in the above example.
2. The system now determines all branch offices of insurance provider A. These are insurance providers for which you specified the
identification key A in the Head offce field of the insurance provider master.
The system determines the branch offices A1, A2, A3 and A4 in the above example.
3. You can create a case-related insurance relationship with one of the insurance providers found.
If you create an insurance relationship with the insurance providers A1, A2 or A4, the head office is billed.
If you create an insurance relationship with insurance provider A3, the insurance provider branch office is billed, since the HIC field
is selected in the insurance provider master. This specifies that the head office entered is used only to determine the insurance
provider branch office when a healthcare smart card is imported and that this specification is not relevant for billing.
1.2.12.4.5 Insurance Provider: Head Office

Billing the Head Office
In the Hd Office field of the insurance provider master record, you specify the identification key of the insurance provider to which
invoices are to be sent, for example the head office of an insurance provider. However, you can bill the head office only if you have also
created the head office as an insurance provider and a customer for the head office is defined in Financial Accounting.
Note
If you bill the head office of the insurance provider, the branch office of the insurance provider need not necessarily have a
corresponding customer in Financial Accounting. The head office-branch office relationship can also have several levels. It is
important to remember that the specification you make in the Head Office field refers to an insurance provider to which no insurance
provider is assigned as a head office and for which a customer exists in Financial Accounting.
Billing the Branch Office

If you want to send bills to the insurance provider branch office rather than to the head office, you can proceed in one of two ways:
Do not specify an insurance provider in the Hd Office field.
You have to specify the headquarters of the insurance provider, to ensure that the system determines both the insurance provider
head office and its associated branch offices when you import a healthcare smart card. In this case, select the HSC indicator.
For more information, see Insurance Provider: Relevant Fields for Importing the Healthcare Smart Card.
Correspondence with the Head Office
If you want not only to send invoices to the head office but also to have all correspondence handled by the head office, you have to
specify the identification key of the head office in the Hd. Office field and select Forms. As a result, the system addresses all patientrelated and insurance-provider related forms, for example insurance verification requests or admission notifications, to the head office.
PUBLIC
Page 57 of 75
Note
The system sends invoices to the head office only if the HSC indicator is not set at the same time.
Insurance Provider Head Office Determination

You can specify different head offices for an insurance provider in relation to relation to the institution and the case type. You can make
this distinction for the following relationships between the insurance provider and the head office:
Invoices for the insurance provider are addressed to the head office.
The head office is relevant for the forms. The system thus makes the data available to the head office in the appropriate form
structures.
You can differentiate the insurance provider relationships in the IMG activity DE: Define Insurance Provider Relationships or by editing
the insurance provider master data.
More Information
For more information about insurance provider head office determination, see the documentation for the report IS-H: Migrate Insurance
Provider Master Head Office into TNREL (RNUX_463B_TNREL) and the documentation for the IMG activity DE: Define Insurance
Provider Relationships in the IS-H Implementation Guide under SAP Healthcare - Industry-Specific Components for Hospitals
Hospital Basic Data Business Partner DE: Define Insurance Provider Relationships .
1.2.12.4.6 Insurance Provider: Health Insurer Search Name

The health insurer search name is a unique search term from the insurance provider master file issued by the Federal Association of
Panel Physicians. It serves as the identification attribute when the insurance provider data is modified by the central insurance provider
master file.
The HI Search Name field in the insurance provider master record is only filled when the insurance provider master data is
automatically transferred from the insurance provider master file. You cannot maintain the field manually.
If you do not use the insurance provider master file to automatically modify insurance provider data in the IS-H system or to transfer
insurance providers into the IS-H system, this field is not filled. If such is the case, you should use screen modification to suppress this
field from the insurance provider search screens, since a search using this field is not appropriate.
If you use the insurance provider master file, this field is filled and can be used when searching for insurance providers.
1.2.12.4.7 Insurance Provider: Control Parameters

You set control parameters in the insurance provider master to define the specific nature of certain function flows.
Note
Note that control parameters of the insurance provider are taken into account only if the IPType indicator is not set in the insurance
provider master. If this indicator is set, the system uses the control parameters you set for the assigned insurance provider type.
You call the control parameters from the address screen of the insurance provider by choosing Further Indicators. For more information
on the control parameters, choose F1 on the various fields.
Integration
The control parameters essentially affect the following areas:
Insurance verification procedure
You can specify whether the insurance provider takes part in the insurance verification procedure, whether reminders should be
created for outstanding insurance verification request, etc.
You enter this data in the appropriate fields in the Insurance Verification Control Parameters group box.
Billing (invoicing)
For the insurance provider in question, you can specify whether an interim invoice or final invoice may be created if confirmation of
coverage has not been received, and so on.
You enter this data in the relevant fields in the Billing Parameters group box.
Information about billing without confirmation of coverage:
The following restriction applies to the Int.Bill. w/o CoC (Interim Billing Without Confirmation of Coverage) and Fin. Billing w/o CoC
(Final Billing Without Confirmation of Coverage) parameters: You can either make identical settings for each parameter, or allow
interim billing without confirmation of coverage while not allowing final billing without confirmation of coverage.
The following parameter combinations are thus permitted:
PUBLIC
Page 58 of 75
Indicator Int.Bill. w/o CoC

Set
Indicator Fin.Billing w/o CoC

Not set
Set
Set
Not set
Not set
The following parameter combinations are not permitted:

Indicator Int.Bill. w/o CoC
Not set
Indicator Fin.Billing w/o CoC

Set
You can select both Final Billing and Interim Billing on the selection screen of the mass billing program. Even when incomplete
insurance verification data causes the program to switch from final billing to interim billing mode, only the setting of the Final Billing
without Confirmation of Coverage in the insurance provider master or in the insurance provider type determines processing.
If you set the Fin. Bill. Diagnosis indicator, when performing final billing the system checks whether the relevant diagnosis has been
entered.
In the IMG activity Set Parameters for Diagnosis Documentation, you can stipulate whether the system is to check for the existence
of the discharge diagnosis and/or the hospital main diagnosis when this indicator is set.
Invoice Printing
With regard to the printout of invoice forms, you can control, for example, whether invoices addressed to a particular insurance
provider should be printed as single invoices and/or within a collective invoice.
If, for example, invoices are transmitted to an insurance provider exclusively in electronic form, you can specify that invoice printout
should be suppressed altogether.
You can set the appropriate indicators in the Invoice Print group box.
Copayment Processing
You can characterize an insurance provider as requiring copayment and specify the copayment procedure by means of which the
insurance provider processes the copayment.
You enter this data in the appropriate fields in the Other Control Information group box.
1.2.12.4.8 Find Insurance Providers Without Customers

You can bill insurance providers for services only if a customer exists for the insurance provider in Financial Accounting (FI) The
insurance provider and the FI customer are linked by the IS-H customer. The FI customer number is stored in the master record of the
IS-H customer.
Features
You can use an evaluation program to create the following insurance provider lists:
List of insurance providers for which the IS-H customer business partner function does not exist. There are also no FI customers
assigned to these insurance providers.
List of insurance providers for which the IS-H customer business partner function exists, but for which there are no FI customers.
List of insurance providers for which there is no IS-H customer business partner function and for which there are IS-H customers, but
no FI customers. This is a combination of the first two lists above.
List of all insurance providers regardless of whether IS-H customers or FI customers exist. Insurance providers without IS-H customers
and without FI customers are indicated.
The system takes existing head office-branch office hierarchies into account in the evaluation. This means that the system outputs an
insurance provider in the list of insurance providers without customers only if one of the following conditions is satisfied:
The insurance provider is not assigned to a head office and does not have a customer.
The insurance provider (branch office) is assigned to a head office and the head office does not exist as a customer. In this case,
only the head office is output in the list. The branch offices assigned to it are not output in the list if customers do not exist for them.
You can execute the program immediately or in the background. If you do not execute the program in the background, a number of
functions available in the evaluation list enable you to edit the layout of the list and the scope of the data displayed.
If you execute the program in the background, you can print the evaluation list. The system prints the selection criteria used to generate
the list above the actual list.
Selection Criteria
You can select the insurance providers you want to evaluate as follows:
Insurance Provider
You can specify the identification key of the insurance providers you want to evaluate.
Insurance Provider Name
You can select the insurance providers by specifying the insurance provider name.
Insurance Provider Type
You can evaluate insurance providers of one or more insurance provider types.
Date Created
You can select insurance providers that were created on a specific date or within a specific time interval.
If you do not specify any selection criteria, the system selects all of the insurance providers that exist in the IS-H database.
You can specify the scope of the list to be output as follows:
To output a list of the insurance providers which do not have the IS-H customer business partner function in the system and
consequently to which no FI customers are assigned, select Ins. provider w/o IS-H customer.
To output a list of the insurance providers which have the IS-H customer business partner function in the system, but do not have an FI
PUBLIC
Page 59 of 75
customer, select Ins. provider w/o FI customer.

To output a list of the insurance providers which do not have the IS-H customer business partner function and the insurance providers
which have an IS-H customer but no FI customer, select Ins. provider w/o IS-H customer and Ins. provider w/o FI customer.
To output a list of all insurance providers, regardless of whether an IS-H customer or FI customer exists, select Ins. provider total.
Activities
See Finding Insurance Providers Without Customers.
1.2.12.4.9 Determine Insurance Providers Without Customers

Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Statistics/Information Report Tree Basic Data
Business Partners IS-H: Ins.Providers w/o FI Customer or IS-H Customer .
The IS-H: Ins. Providers w/o FI Customer or IS-H Customer selection screen appears.
2. Specify the selection criteria and choose
(Execute).
The system evaluates the selected insurance providers, and outputs the list. The system displays the following icons for the
insurance providers in the Ok field:
(-): An IS-H customer exists for the insurance provider and an FI customer is assigned to the IS-H customer.
(-): Insurance provider without customer (IS-H customer or FI customer).
The icons have the following meaning in the FI customer field:
(-): An IS-H customer exists for the insurance provider.
(-): No IS-H customer exists for the insurance provider.
1.
Example
The system characterizes an insurance provider for which there is an IS-H customer, but no FI customer, as follows:
The
(-) indicator is selected in the Ok field.
The
(-) indicator is selected in the FI customer field.
You can edit the list layout. For more information about this, call the program documentation by choosing
Help Application help .
1.2.12.5 IS-H Customer (Business Partner Function)

The IS-H customer is the link between the business partner in the IS-H System and the customer in Financial Accounting (FI System).
Postings are made automatically from the IS-H System to the customer accounts, provided you have maintained the FI customer-tobusiness partner assignment in the master data of the IS-H customer.
The following topics describe the customer-specific master data you can maintain for the IS-H customer.
Integration
The following topics also cover how you create the assignment of the IS-H customer to the FI customer and process customer data.
More Information
Creating IS-H Customers
Changing Customers
Determination of IS-H Customers Without FI Customers
Determine Insurance Providers Without Customers
1.2.12.5.1 Customer-Specific Master Data

The IS-H customer data is a subset of the customer master data in Financial Accounting.
PUBLIC
Page 60 of 75
Integration
Edit the customer master record in Financial Accounting in order to store further data.
For more information about customer master data, see Customer Master Data in the online documentation for Financial Accounting.
Features
The following data is displayed in the customer address data screen:
Company Code
Customers are managed in the system on a company code basis. In the customer address data screen, the system displays the
company code to which the customer is assigned. This is the company code to which the institution in which you created the customer
is assigned.
Note
All business partner functions with the exception of the IS-H customer are valid for all institutions of a given client. IS-H customers
are only valid for one institution.
Customer Number
If the corresponding customer already exist in Financial Accounting, you can assign it to the IS-H customer.
Create Customer indicator
If you set this indicator, the system calls the Create Customer function in Financial Accounting in the background, and automatically
creates the corresponding FI customer.
The following data is displayed in the Financial Accounting data screen:
Bank details
You can store the bank details of the customer here. If you enter a bank number that is not yet defined in the system, you can store
general bank data (name, address, etc.) for this bank number in a catalog. If you enter further bank details with this bank number, this
general data is already available.
You can maintain further bank details by choosing the Bank Details function.
If several sets of bank details exist for a customer, you can list them by choosing Bank Details List.
Account Management
You can store the reconciliation account and the sort key here.
Payment Data
You specify the payment terms that apply to the customer here.
Reminder data
Here you specify the dunning procedure via which you want to control dunning for this customer.
1.2.12.5.2 Creating IS-H Customers

How you create an IS-H customer depends on whether the corresponding customer already exists in Financial Accounting.
Features
FI Customer Does Not Exist
When creating an IS-H customer, you can have the FI customer created automatically when you save the IS-H customer. For this
purpose, the system uses the master data you stored in the IS-H customer. The system automatically creates the assignment between
the IS-H customer and the FI customer.
Proceed as described in Creating Customers in IS-H and FI.
FI customer already exists
It may be case that customers already exist in Financial Accounting, but not in the IS-H System. This situation can arise if, for example,
you implemented the Financial Accounting System before the IS-H System. In this case, you have to create the business partner in the
IS-H System and then manually maintain the assignment of the FI customer to the IS-H customer.
Proceed as described in Creating IS-H Customers and Assigning FI Customers.
If you have created an IS-H customer without creating an FI customer at the same time, you can create the FI customer at a later date
and assign it to the IS-H customer. Proceed as described in Assigning FI Customers to IS-H Customers.
1.2.12.5.3 Creating Customers in IS-H and FI

To create a customer in the IS-H System along with the corresponding customer in Financial Accounting, proceed as follows:
PUBLIC
Page 61 of 75
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners Customer Create .
The Create Customer: Initial Screen appears.
2. If the customer you wish to create already exists as a general business partner, specify the identification key of the business partner,
and then choose
(Create). If you do not know the identification key of the business partner, determine it using the business partner
search, and then choose the required record from the resulting hit list.
If the customer you wish to create does not exist as a general business partner, create it now.
(Create).
(Create).
3. Maintain or check the address data.
4. To have the system automatically create the corresponding FI customer when you save this data, select Create.cust.
1.
Note
You can use a system parameter in Customizing for IS-H to have this field selected by default.
5.
Go to the second customer data screen by choosing Financial acctg data.

Here you store the customer master data with which the system creates the FI customer. Fields that require you to make an entry in
the Financial Accounting customer master are also required-entry fields here.
Note
In Customizing for IS-H, you can specify default values for these fields with the exception of the Bank number and Bank account
fields. You can overwrite these default values here.
Customizing for IS-H provides a user exit for you to define default values for further fields of the customer master record in
Financial Accounting.
6.
Save the data.

The system creates the IS-H customer and the FI customer. You can complete the customer master data in Financial Accounting.
More Information
Changing Customers
1.2.12.5.4 Sensitive Fields

You can define fields as sensitivein the customer and vendor master records. If you define a field in the customer/vendor master
record as sensitive, the corresponding customer/vendor account is blocked for payment if the entry in this field is changed. To remove
the block, a second person with authorization must check the change, and confirm or reject it.
Integration
If you have defined fields as sensitive for dual control (see below) in the Financial Accounting Implementation Guide, note the following:
For changes to customers that were generated from patient management or the general business partner to take effect in the Financial
Accounting System, a second user in the FI System must confirm them.
The following fields can be used for the FI System:
SORT1: Search term 1
SORT2: Search term 2
HSNM1: House number
HSNM2: Supplementary house number
CITY3: City (alternative to postal city)
TZONE: Time zone of address
TXJCD: Jurisdiction for tax calculation tax jurisdiction code
PERNR: Personnel number
CONAM: Name (not the occupant)
STREET2: Street 2
STREET3: Street 3
BUILD: Building code
ROOM: Room
FLOOR: Floor
These fields are available in the user exits for defaulting data in the FI System. Check if you want to enter IS-H field content (for example,
street supplement) in the available FI System fields (for example, STREET2).
Country Version Singapore
PUBLIC
Page 62 of 75
If you use the country version Singapore, you should check whether you have to copy and modify user exits
ISH_FILL_KNA1_SZ_DEBI and ISH_FILL_KNA1_ISH_DEBI, as there are fields for building code, room and floor in the FI
System. Previously, this data was entered in customer fields under name (technical name: KNA1-NAME1, KNA1-NAME2, KNA1NAME3, and KNA1-NAME4). You should also check whether the house number and street should be entered in field HSNM1 or HSNM2
and the street supplement in field STREET2 or STREET3.
Effects on Customizing
For more information about maintaining sensitive fields when you enter a customer, see the section entitled Define Sensitive Fields
for Dual Control (Customers) in the Financial Accounting Implementation Guide.
For more information about function modules for defaulting data in the FI System, see the section entitled Define Function Modules
for Presetting FI Data in the IS-H Implementation Guide.
1.2.12.5.5 Creating IS-H Customers and Assigning FI

Customers
You can create a customer in the IS-H system and assign an existing FI customer to it.
Procedure
1.
2.
3.
4.
5.
6.
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners Customer Create .
The Create Customer: Initial Screen appears.
If the customer you wish to create already exists as a general business partner, specify the identification key of the business partner,
and then choose
(Create). If you do not know the identification key of the business partner, determine it using the business partner
search, and then choose the required record from the resulting hit list.
If the customer you wish to create does not exist as a general business partner, create it now.
1. If you are working with external number assignment, specify the identification key of the business partner, and then choose
(Create).
2. If you are working with internal number assignment, choose
(Create).
Maintain or check the address data.
Specify the number of the corresponding customer in Financial Accounting in the Cust. no. field.
A dialog box appears containing a subset of the customer master data from Financial Accounting.
To assign this FI customer to the IS-H customer, choose Copy customer.
Save the data.
The system creates the IS-H customer and assigns the FI customer to it.
More Information
Changing Customers
1.2.12.5.6 Assigning FI Customers to IS-H Customers

You can later assign FI customers to IS-H customers which do not have FI customers. How you do this depends on whether the required
customer already exists in Financial Accounting.
Procedure
FI Customer Exists
1.
2.
3.
4.
5.
6.
On the SAP Easy Access screen, choose Hospital Basic Data Administration Business Partners Customer Change .
The Change Customer: Initial Screen appears.
Specify the identification key of the IS-H customer to which you want to assign an FI customer.
Choose
(Change).
Specify the number of the customer from Financial Accounting in the Cust. no. field.
A dialog box appears containing a subset of the customer master data from Financial Accounting.
To assign this FI customer to the IS-H customer, choose Copy customer.
Save the data.
The system assigns the FI customer to the IS-H customer. You return to the initial screen of the function.
FI Customer Does Not Exist
PUBLIC
Page 63 of 75
2. Specify the identification key of the IS-H customer for which you want to create an FI customer.
3. Choose
(Change).
4. Select Creat.cust., and save the data.
The system creates a customer in the FI System and assigns it to the IS-H customer. You return to the initial screen of the function.
1.
1.2.12.5.7 Changing Customers

You can change the customer master data both via the IS-H customer and the FI customer. Whereas the IS-H customer merely
comprises a subset of the customer data, the FI customer allows you to process the complete set of customer data.
If you edit the IS-H customer, you can change the following data:
Name and address data
Financial accounting data
Bank details
Account management data
Payment data
Reminder data
As a rule, the system automatically applies any changes you have made in the IS-H customer to the FI customer and vice versa. When
you edit address data, there are, however, cases in which changes are not applied.
Editing the IS-H customer
If you delete the address data (street, postal code, city) of the IS-H customer, the system does not delete this data from the customer
master record in Financial Accounting. The old address is retained here.
However, the system also makes changes to the address data in the FI customer.
Note
When creating invoices, the system determines the invoice address from the FI customer.
Editing the FI customer
If you change the address data in the FI customer, the system does not apply these changes to the IS-H customer. To always have
the most recent data both in the IS-H customer and the FI customer, you must therefore make the changes in the IS-H customer.
For further information about editing the FI customer, see Customer Master Data in the online documentation on Financial Accounting.
Procedure
1.
2.
3.
4.
5.
Specify the identification key of the customer. If you do not know the identification key, determine it using the business partner search,
and then choose the required record from the resulting hit list.
You can change the address data here.
To change the Financial Accounting data, go to the second data screen by choosing Financial acctg data.
You can change the Financial Accounting data here. The following functions are also available here:
Create Bank Details
Edit bank details list
Then save the data.
1.2.12.5.8 Create Bank Details

Procedure
If bank details do not exist for a customer, create these as follows:
1. Call the customer data in change mode. (For further information about changing customers, see Changing Customers).
The Change Customer: Financial Accounting screen appears.
2. Specify the bank details on the Change Customer: Financial Accounting screen.
3. If you specify a bank key which does not yet exist in the IS-H database, a dialog box appears for you to maintain the bank details.
Maintain the bank details, and then choose Continue.
4. Then save the data.
If you have already created bank details for a customer, the system displays the first set of these bank details.
You create further bank details as follows:
PUBLIC
Page 64 of 75
From the Change Customer: Financial Accounting screen, choose Bank details.
The Create Bank Details screen appears.
2. Specify the bank details.
If you specify a bank key which does not yet exist in the IS-H database, a dialog box appears for you to maintain the bank details.
Maintain the bank details, and then choose Continue.
To change existing bank details, proceed as described in Editing the Bank Details List.
1.
1.2.12.5.9 Edit Bank Details List

You can display and edit the list of bank details for a customer.
Procedure
Call the customer data in change mode. (For further information about changing customers, see Changing Customers).
The Change Customer: Financial Accounting screen appears.
2. On the Change Customer: Financial Accounting screen, choose
(Bank Details List).
A dialog box appears listing the existing bank details.
3. The following functions are available to you in this list:
To change the bank details, select the bank details, and then choose
(Change). Change the bank details, and then choose
(Continue).
To print the list of bank details, choose
(Print).
To search for bank details in the list, Choose
(Find). A dialog box appears for you to carry out the search.
1.
1.2.12.5.10 Determination of IS-H Customers Without FI

Customers
To be able to post to customer accounts in Financial Accounting (FI) when billing in the IS-H System, you need to have created the
customer business partner in the IS-H System as an IS-H customer. An FI customer must be assigned to the IS-H customer.
You can evaluate the existing IS-H customers to determine whether an FI customer is assigned to them. The evaluation program outputs
a list of IS-H customers to which no FI customer is assigned.
Selection Criteria
You can use the following criteria to select the IS-H customers you wish to evaluate:
Customer
You can specify the identification key of the IS-H customers you wish to evaluate.
Customer name
You can select the IS-H customers by specifying the customer name.
Date Created
You can select IS-H customers you created at a specific date or within a specific time interval.
If you do not specifying any criteria, the system evaluates all IS-H customers which exist in the specified institution.
Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Statistics/Information Report Tree Basic Data
Business Partners IS-H:IS-H Customers w/o RF/FI Customers .
The IS-H: IS-H Customers w/o RF/FI Customers selection screen appears.
2. Specify the selection criteria and choose
(Execute).
The system evaluates the selected IS-H customers and outputs the list of IS-H customers to which no FI customer is assigned.
3. Choose
(Back) to exit the list.
You return to the initial screen of the program.
1.
More Information
Assigning FI Customers to IS-H Customers
PUBLIC
Page 65 of 75
1.2.12.6 Hospital (Business Partner Function)

You can store hospitals that are in contact with your institution, for example referring or postdischarge hospitals, as business partners in
the system.
To identify the hospital, you can store the institute indicator of the insurance provider in the Inst. Ind. field in the hospital master record. In
Germany, the institute indicator is assigned by the Federal Office for Statistics.
You can assign a hospital type to each hospital in the Hospital Type field. This makes it possible to combine hospitals in groups. You
define the permitted hospital types in Customizing for IS-H.
Example
Possible entries are:
PB: Public
PR: Private
OT: Other
More Information
Hospital in Insurance Provider Role
1.2.12.6.1 Hospital in Insurance Provider Role

When you treat patients from an external hospital, you perform services for the external hospital. You bill the external hospital for these
services.
For this to be possible, the hospital must also perform the Insurance provider business partner function. If this condition is satisfied, you
can create an insurance relationship for the patient and case with the hospital as insurance provider and can charge the hospital for the
services.
If you create hospitals and insurance providers/customers from separate number ranges, you should create two business partners for
the hospital:
A business partner performing the Hospital function
A business partner performing the insurance provider and customer functions
1.2.12.7 Employee/Physician (Business Partner Function)

You can specify natural persons as business partners in the IS-H System. Persons can be external physicians and employees of your
institution. You can differentiate employees by means of the following person categories:
Physician
Employee
Nurse
You can additionally classify physicians as external physicians by means of the appropriate person category.
You use persons as business partners when documenting the persons who are involved in a case. For example, you can store the
referring physician in the admission data. Using the case-to-person assignment, you can assign any persons performing user-defined
functions to a case.
Specific Master Data of Employees/Physicians (Person Category, Rank and Physician Indicator)
In addition to the general business partner data, you can maintain the following data for employees and physicians.
Note
When searching for a business partner (the referring physician, for example) in the IS-H System, you can restrict the search by
specifying the majority of these indicators and data.
Sex/date of birth
2nd extension
You can specify an extension number in addition to a persons normal extension number.
In HR System indicator
The system sets this indicator automatically if you enter a person who already exists in the Human Resources System (RP or HR).
Using screen modification in customizing for IS-H, you can define specific fields of the person master record which should be
PUBLIC
Page 66 of 75
maintained exclusively in the human resources system as display fields and consequently prevent their values from being
overwritten.
Person category
Using the person category, you can categorize persons as internal physicians, nurses, external physicians, and so on. You can set an
appropriate combination of several indicators for one person.
Example
You can assign the Physician and Employee person categories to a hospital physician.
When you assign persons holding the functions Referring Physician or Attending Physician to a case, the system checks whether
the assigned business partner has the person category Physician.
Physician indicators
You can store the following additional information for physicians (persons of the person category Physician). For more information,
see the F1 help.
Accredited
External Accreditation
Physician number: identification number of the service performer, which applies independently of the place of work
Place of work number (BSNR): used to assign the physician service to the place at which it was performed
SpecialtyYou can enter the specialties for the physician/employee using the pushbutton adjacent to the Specialty field. You cannot
make an entry in the Specialty field itself. The system displays the specialty assignment first entered for the physician in the
Specialty field.
Specialist Type
References
External personnel number
If the person exists in a partner system, or if you have transferred the persons data from a partner system, here you can specify the
identification key under which the person was managed in this system.
Institute Indicator
To identify the physician, you can store the institute indicator of the physician. In Germany, the institute indicator is assigned by the
Federal Office for Statistics.
TARMED Data (Country Version Switzerland)
The Qualitative Grade and Quantitative Grade fields are provided for entering the specialist qualification or level of training of the
employee. This information is stored in relation to a specific period.
TARMED stipulates that certain services can only be billed for by physicians with a particular training. You can activate service rules that
check that these prerequisites are satisfied.
Caution
You cannot enter the qualitative grade 9999 or 9995 here. The system automatically performs checks and mappings if one of the
mentioned grades was stored in the service master. 9999 in the service means that it can be billed for by physicians with any
qualitative grade. 9995 in the service means that it can be billed for by physicians with one of the following qualitative grades: 0011,
0200, 0300, 0400, 0600, 0800, 0810, 0900, 1000, 1005, 1800, 1900, 2000, 2100, or 2900.
More Information
Service Check with Regard to Qualitative Grade (C11)
Service Check with Regard to Quantitative Grade (C12)
1.2.12.8 External Ordering Party (Business Partner Function)

[CH]
1.2.12.9 Fee Recipient (Business Partner Function) [CH]

PUBLIC
Page 67 of 75
1.2.12.10 Assign Contract Partner Number (AT)

1.3 Service Master Data

Description of possible services for documentation, billing or cost accounting purposes. This includes services only used for billing, for
example, flat rates per case or procedures surcharges.
All services that can be entered into the system are listed in service catalogs. You can import external service catalogs and, if
necessary, change and enhance them, or you can create your own catalogs.
Integration
Select this component if you want to enter planned services or services already performed. Service entry provides the basis for the
following subsequent functions:
Insurance verification
Billing
Integration with Controlling
Creation of government-mandated statistics
Service communication of IS-H*MED
Features
For Information On
Service master data
See
Service Master
Service group
Service Group
Service list
Service List
Transporting service master data
Transport Service Master Data
1.3.1 Service Master

For each service, the service master comprises specific data that affects service entry and billing. All services are managed in relation
to service catalogs. In Germany, such service catalogs are DKG-NT, GO, and E-GO.
Prerequisites
You define these catalogs (the catalog columns, for example) in Customizing for IS-H. For more information, see the sections entitled
Define Service Catalog Types and Define Service Catalog Columns in the IS-H Implementation Guide.
Features
For information about the initial screen, see Service Master: Initial Screen.
You maintain the service master data for the various areas on the following tab pages:
Service Master: Service Texts
Service Master: Columns
Service Master: Classification
Service Master: Other
Service Master: Medical Indicators
Service Master: FR/PS (Germany)
For more information about important master data relative to flat rates per case and procedures surcharges (Germany), see Important
Master Data for Flat Rates per Case and Procedures Surcharges (Germany).
Activities
Creating the Service Master
Changing the Service Master
Delimiting the Validity of the Service Master
Service Overview
Maintaining Add. Data for FR/PS (Germany)
PUBLIC
Page 68 of 75
1.3.1.1 Creating the Service Master

Procedure
To create services in a service catalog, choose Hospital Basic Data Administration Service Master Data Service Create on
the SAP Easy Access screen.
The initial Create Service screen appears.
2. Specify the institution, service catalog and identification code of the service you want to create. Also specify the validity period of the
service.
1.
Note
In Customizing for IS-H, you can define institution-specific default values for the validity start and end dates of service master
records. If you do not enter a validity interval on the initial screen of the service master record, the system automatically uses the
default values defined in Customizing. For more information about this, see Define Validity Period of Service Master Data in the
IS-H Implementation Guide.
Choose
(Create).
The Create Service screen appears. Your cursor is positioned on the first tab page of the service master record (Service Texts tab
page).
4. Maintain the data on the tab pages as required:
Service Texts
Columns
Classification
Other
Med. Indicators
Communication
FR/PS (Germany)
Planned Values
5. Save the data.
3.
More Information
Service Overview
1.3.1.2 Service Master: Initial Screen

To create services, you have to specify a permitted value (the identification key of a defined service catalog) in the Service Catalog
field on the initial screen of the function.
The validity interval of the service master record contributes to the system's ability to track historical data. If you do not specify a validity
interval, the system proposes the dates that were defined in Customizing for IS-H. For more information about this, see Define Validity
Period of Service Master Data in the IS-H Implementation Guide.
Note
If you do not enter a validity interval and thus accept the default values defined in Customizing for IS-H, validity intervals will be
consistent. In this way, you can avoid having to adjust validity when combining services in service groups, for instance.
You can enter the identification code of an existing service in the Service field in the Template group box. The system proposes the
values from this template service in the subsequent steps involved in creating the service.
To change or display services, you have to specify an institution and an identification code for the service concerned. If you enter a
validity start date, the system goes directly to the interval of the service master in which the specified date occurs. If you do not enter a
validity start date, all existing validity intervals which exist for the specified service are selected. From this overview list, you can choose
the validity interval you want to edit. If only one validity interval is defined in the IS-H database, the system goes directly to the service
master record.
1.3.1.3 Service Master: Service Texts

PUBLIC
Page 69 of 75
On the Service Text tab page, you store the short and long texts for the service and make specifications relative to the service group
and the entry block.
Use Pictures in Service Master
To make a service more easily recognizable, you can assign a picture to each service. For more information about this, see Use of
Pictures in the Service Master.
Features
The short text is used to display services in the service entry function. A field 120 characters in length is provided for this text.
In the Long Text field, you can store a long text to describe the service more precisely. If the input field is not long enough, you can call
up the text editor to enter a text of any length. To do this, choose the pushbutton adjacent to the input field.
The Comment field allows you to store additional information about a service. Just like when entering the long text, you can call up the
text editor here.
The Expand Group indicator lets you specify whether a service group is to be directly expanded in the service entry function. This
indicator is only relevant for services that are classified as service groups. If you do not wish service groups to be expanded directly
after entry in the service entry transaction, do not set this indicator. In this case, you have to explicitly specify in the service entry
transaction that a service group should be expanded.
You can prevent a service from being entered in the service entry function (Entry Block option). This can be useful for services
that are simply required for structuring service groups and thus only occur as hierarchy nodes.
1.3.1.4 Service Master: Columns

On the Columns tab page of the service master record, you store information that qualifies the service with respect to the service
catalog. For this purpose, you can specify values for the defined service catalog columns. The system checks whether these entries
match the input values authorized by the column definitions of the selected service catalog.
Features
The Columns tab page lists the columns of the service catalog that were assigned to the catalog in question in Customizing for IS-H.
You enter the values (charge factors or amounts) for these columns. In the case of currency-related amount columns, the currency key
from the assigned service catalog is displayed.
Note
In Customizing for IS-H, you specify for each column of a service catalog whether the column contains either charge factors or
currency amounts. For more information about this, see the section entitled Define Catalog Columns in the IS-H Implementation
Guide.
As of IS-H Release 4.02, you can no longer maintain hybrid forms. In other words, you cannot fill particular columns in the individual
service master records partially with amounts and partially with charge factor values.
If a service exists and you enter a new service master record for this service with a different validity interval, the system checks
whether this change affects the existing validity intervals of the service. If this is the case, the system limits the existing validity interval
accordingly and displays the change to the existing validity intervals. You can go ahead this change by choosing Create. If you do not
want to execute the change, choose Cancel.
1.3.1.5 Service Master: Classification

You can set various indicators for a service on the Classification tab page of the service master. For instance, it is relevant for service
entry whether a service can be billed for or whether it is an immediate service (e.g. X-ray) or an extended service. The Billable indicator
setting is used as a default in the service entry and insurance verification functions. You can, however, change the value of this setting in
these functions.
You can assign up to two service categories to a service (fields Service Ctgry and Svce Ctgry 2). You must have defined these service
categories beforehand in Customizing for IS-H. For more information about this, see Maintain Service Categories in the IS-H
You can use service categories for the following purposes:
PUBLIC
Page 70 of 75
To...
Re-map services (rules for determination
of billing catalog)
SvceCtgry
X
Svce Ctgry 2
Determine charge factor values (assign

currency amounts to charge factors)
Determine revenue accounts and prices
Create your own analyses and evaluations X
Recommendation
The use of service categories is optional. It is, however, especially recommended, if particular settings apply for a group of services.
The Adm. Date Price option enables you to stipulate the date that is relevant for pricing for inpatient and day patient cases. The relevant
pricing date can either be the date when the service is performed or the date of patient admission. If you do not select this option, the
system uses the date of service performance for pricing.
Example
Select this indicator of you want to use the date of admission as the pricing date for flat rates per case, for example.
You can also use the date of the case's first visit to determine the price of an outpatient case. To do this, set the Determine Price from
Date of 1st Visit indicator.
For integration with Controlling, you must flag the services to be transferred to Controlling (CO) as relevant for CO. If you want to use
Cost Object Controlling in CO, you must flag certain services for which you have defined preliminary costings in CO as cost objects.
You also store the charge type of a service on this tab page. You classify services using the charge types flat rate per case,
procedures surcharge, departmental per diem, etc. Numerous checks within the service entry and billing functions make use of the
charge type of a service. In Germany, this particularly applies for checks concerning billing pursuant to the Federal Regulation for
Hospitals 1995.
You also specify the flat rate per case type (Germany) in the Service categories / Types group box here. It is used in particular to
specify different flat rates per case for obstetrics and to define flat rates per case with a maximum length of stay for intensive care. The
flat rate per case type affects the charge check and charge determination.
Example
If, for example, you assigned the flat rate per case type Obstetrics multiple birth, when the charge proposal runs, the system checks
whether the case involves a multiple birth. Only if this criterion is satisfied does the system propose this flat rate per case.
You can also specify on this tab page whether an alternative price can or must be maintained in the service entry function, or whether
an alternative price may not be maintained for the service in question. Make the corresponding entry in the
Alternat. Price field. If you are using the country version Singapore, the additional fields Srv. Sum. Code and Op. Table are available to
you:
By making a valid entry in the Op. Table field, you define the assignment of a service to a table of operation.
By assigning a service summary code, you can combine the same type of services (i.e. with identical summary codes) in one invoice
item on the summary invoice.
1.3.1.6 Service Master: Other

The attributes Sex, Minimum Age and Maximum Age belong to the Other tab page in the service master.
Note
You can specify these attributes as exclusion criteria for flat rates per case and procedures surcharges (country version Germany).
For more information, see Important Master Data for Flat Rates per Case and Procedures Surcharges (Germany).
In addition to these attributes, you can specify further attributes and a link from the service to a material in Materials Management on this
tab page.
Country Version Germany: OPS Localization
For procedures that are performed on pair organs, the official OPS version 2005 contains the indicator that stipulates that the
localization must be specified. You can stipulate this in the service master data (indicator OPS Localization Oblig.).
If you select the indicator in the service master, the system issues an error messages when such procedures are entered without the
localization being specified. You cannot save the procedure data until you have specified the localization.
You can enter valid customer-specific localizations in the Customizing activity Maintain Medical Localization. Note that each customerspecific localization must be assigned to an official localization
For information about this, see SAP Healthcare - Industry-Specific Components for Hospitals Medical/Nursing Documentation
Maintain Medical Localization in Customizing.
PUBLIC
Page 71 of 75
Country Version Germany: OPS Indicator Living Donor

The system uses the OPS Indicator Living Donor field to make a default entry in the LD (living donor transplantation) field during
procedure entry.
For more information, see 301 Data Transfer for Outpatient Billing Areas.
1.3.1.7 Service Master: Medical Indicators

The medical indicators describe, for example, whether a service is used in a particular area (e.g. administrative service, medical
service, nursing service).
Medical indicators can only be selected if IS-H*MED is active in your system.
1.3.1.8 Service Master: Communication

The following fields are available on the Communication tab page in the service master:
Charge Key
This field determines characters 1 and 2 characters 1 of the charge type according to 301 of the German Code of Social Law (SGB
V). The workers' compensation association procedure DALE-UV uses this field for the service item code.
Additional Key
The additional key is used to determine the 3rd character of the charge type according to 301 SGB V.
Charge Type 301
This field determines characters 4 through 8 of the charge type according to 301 SGB V.
Individual Remuneration (Outpatient Surgery)
This field contains information about special materials (indicated by code 3 in addendum 2 to 301 SGB V, individual remuneration for
outpatient surgery, notes). These materials are reimbursed by individual cases and transferred in EZV segments.
Charge Type 301 Outpatient
This field contains the outpatient charge type defined according to the 10th update of 301 SGBV to mark services at outpatient
institutions that are transferred externally using the AMBO invoice record as of January 1st, 2012.
Report Service Master: Convert UAS Code as Outpatient Charge Type (RNUENTGAMB) can be used to make an initial entry in the
field. For more information, see the report documentation.
Special Features for Country Version Singapore
If you are using the country version Singapore, the field Ext. Chrg. Type is available to you in the External Communication group box.
This assignment is used to specify an external charge type for communication with external partners.
More Information
For more information about the fields, see the field help.
1.3.1.9 Service Master: FR/PS (Germany)

Besides the master data of a service, you also specify further master data pertaining to flat rates per case and procedures surcharges.
These specifications include:
Planned number of flat rates per case or procedures surcharges per year
Maximum length of stay for the flat rate per case and maximum length of stay for intensive care when the service is performed by the
main department
Maximum length of stay for the flat rate per case and maximum length of stay for intensive care when the service is performed by an
external physician
Standard length of stay for the flat rate per case and standard length of stay for intensive care treatment performed by the main
department
Standard length of stay for the flat rate per case and standard length of stay for intensive care treatment performed by an external
physician
The system uses this data when creating the flat rate per case statistics. Furthermore, when carrying out the charge check the system
uses the maximum length of stay specifications to determine whether the maximum length of stay has been reached for a case or not.
Features
PUBLIC
Page 72 of 75
Time-Dependent Maintenance
You can maintain the information on the maximum and standard length of stay for a specific time interval. This enables you to document
changes to the maximum and standard length of stays resulting from amendments to the Federal Regulation for Hospitals 1995 (BPflV
1995).
Valuation Relationships/Charge Factors
For flat rates and procedures surcharges, you can specify valuation relationships in the form of charge factors for personnel and
materials (corresponding to attachments 1 and 2 of BPflV 1995). These charge factors are evaluated in the V2/V3 statistics where they
are used to calculate the amount of the charge.
More Information
Important Master Data for FR/PS (Germany)
1.3.1.9.1 Important Master Data for FR/PS (Germany)

This documentation is only relevant for the country version Germany and is not available in English.
1.3.1.9.2 Maintaining Add. Data for FR/PS (Germany)

Prerequisites
1.3.1.9.3 Add. Data: Displaying and Delimiting Validity Intervals

(Germany)
1.3.1.10 Service Master: Additional Data (Switzerland)

1.3.1.10.1 Maintaining Add. Data for Service Catalogs and Fees

(Switzerland)
1.3.1.10.2 Maintaining Additional Data for TARMED

PUBLIC
Page 73 of 75
1.3.1.10.2 Maintaining Additional Data for TARMED

(Switzerland)
1.3.1.10.2.1 Maintain Swiss Service Master (TARMED) Using

Tables
1.3.1.10.2.2 Import TARMED Service Master Data (Switzerland)

1.3.1.10.3 Import Tariff Types (Switzerland)

You can use the Import Report for Internal Tariff Types (Domain NWCH_TARTYPI) program to import the tariff types currently valid in
the country version Switzerland into the system as fixed values for the NWCH_TARTYPI domain.
Prerequisites
You can download the tariff types as an Excel file from the homepage of the information platform FORUM DATENAUSTAUSCH and
make it available as an input file in a converted format to the import program.
Activities
You execute the report as follows:
1. Enter transaction code SE38 to access the initial ABAP Editor screen.
2. Specify the program RNWCHTARTYP_DOM and choose
(Execute) to access the initial IS-H CH: Import Report for Internal Tariff
Types (Domain NWCH_TARTYPI) screen.
3. Enter the file that was converted beforehand and choose
(Execute) to execute the report.
For more information about this, see the documentation for the IS-H CH: Import Report for Internal Tariff Types (Domain
NWCH_TARTYPI) program (RNWCHTARTYP_DOM).
1.3.1.10.4 Alternative Service Code (Switzerland)

1.3.1.11 Service Master: Additional Data (Austria)

PUBLIC
Page 74 of 75
1.3.1.12 Maintaining Planned Values for Services

In addition to the service master data, you can also specify the planned values for services. For each service, you can store timedependent planned quantities per service and the requesting departmental organizational unit (OU). Furthermore, you can specify the
number of planned days per service and the planned number of days on which you charge a discounted departmental per diem (e.g.
relevant for procedures surcharges).
By entering an asterisk (*) for the requesting departmental OU, you maintain planned values for the entire institution.
Procedure
1.
2.
3.
4.
5.
On the SAP Easy Access screen, choose Hospital Basic Data Administration Service Master Data Service Planned Values .
The Change View IS-H: Planned Values per Service and Organizational Unit overview screen appears.
To create a new entry, choose New Entries.
The detail screen of the entry appears.
To change an existing entry, select the entry and choose
(Change).
The detail screen of the entry appears.
Maintain the data.
Save the data.
Note
You can also maintain the planned values for a service on the Planned Values tab page in the service master.
1.3.1.13 Changing the Service Master

Procedure
On the SAP Easy Access screen, choose Hospital Basic Data Administration Service Master Data Service Change .
The initial Change Service screen appears.
2. Specify the institution, service catalog and identification code of the service you want to change.
3. Choose
(Change).
The Change Service screen appears.
1.
Note
If several validity intervals are defined for the service and you have specified a valid-from date on the initial screen, the system
displays the basic data screen of the service master record for the validity interval in which the specified valid-from date occurs.
If several validity intervals exist, the system first displays the list of defined validity intervals. Select, then choose the validity
interval you require. The system displays the basic data screen of the service master record for the validity interval you have
selected.
Maintain the data on the appropriate tab pages.
Service Texts
Columns
Classification
Other
Med. Indicators
Communication
FR/PS (Germany)
Planned Values
5. Save the data.
4.
More Information
Service Overview
PUBLIC
Page 75 of 75

01.saphelp Erp60 SP en 1b Cb0d50aa85d047e10000000a44176f Content-Ish-BasicData

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

01.saphelp Erp60 SP en 1b Cb0d50aa85d047e10000000a44176f Content-Ish-BasicData

Hochgeladen von

Copyright:

Verfügbare Formate

BASIC DATA

PDF download from SAP Help Portal:

1.2.6.1 General Business Partner Data

1.1 Hospital Structure

Introduction to the Building Structure

1.1.1 Input Help for Organizational Hierarchy

1.1.2 Maintaining Personal Value Help

1.1.3 Organizational Structure

Statistics evaluate specific data in relation to organizational units,

Service transfer into Controlling

To be able to transfer services into Controlling, you must first

1.1.3.1 Creation of Organizational Structure

Creating Organizational Units

Maintain the Organizational Hierarchy

1.1.3.2 Organizational Unit

You Store the Following Data...

Division (country version Switzerland only)

1.1.3.2.1 Organizational Unit: Name and Address Data

1.1.3.2.2 Organizational Unit: Blocking Indicator

1.1.3.2.3 Organizational Unit: Validity Dates

1.1.3.2.4 Organizational Unit: Specialty Keys

1.1.3.2.5 Organizational Unit: Departmental Per Diem

Different Services Within a Nursing OU

1.1.3.2.6 Example: Departmental Per Diem of Departmental

Surgery intensive care

Surgery intensive care

1.1.3.2.7 Organizational Unit: Indicators Relevant to

1.1.3.2.8 Organizational Unit: Division (CH)

1.1.3.2.9 Organizational Unit: Assign Physician (AT)

1.1.3.2.10 Identification Key for Organizational Units

1.1.3.2.11 Creating Organizational Units

1.1.3.2.12 Maintain Organizational Units: Initial Screen

1.1.3.2.13 Changing Organizational Units

Save the data.

1.1.3.2.14 Flagging Organizational Units for Deletion

1.1.3.2.15 Canceling the Deletion Flag for Organizational Units

1.1.3.2.16 Blocking/Unblocking Organizational Units

1.1.3.3 Organizational Hierarchy

1.1.3.3.1 Example: Organizational Hierarchy

1.1.3.3.2 Maintain the Organizational Hierarchy

1.1.3.3.3 Displaying the Hierarchy Overview Graphic

1.1.3.3.4 Interdepartmental Relationships

1.1.3.3.5 Maintain Interdepartmental Relationships

Create New Assignments

1.1.3.4 Maintaining Organizational Unit-to-Building Unit

Create New Assignments

Display and Change Existing Assignments

Select an entry, and then choose

Delete Existing Assignments

1.1.3.5 Maintaining Statistical Bed Figures

Delete Existing Entries

1.1.3.6 Release Organizational Structure

1.1.3.7 Transport Organizational Units

Example Entries for Statistical Beds

Specifications for Program Execution

1.1.3.7.1 Transporting Organizational Units

1.1.4 Building Structure

1.1.4.1 Creation of Building Structure

Maintain building structure:

1.1.4.2 Building Units

1.1.4.2.1 Building Unit: Name Data

1.1.4.2.2 Building Unit: Validity Dates

1.1.4.2.3 Building Unit: Coordinate Data