sap patient management

SAP Patient ManagementPDF download from SAP Help Portal:http://help.sap.com/saphelp_erp60_sp/helpdata/en/3c/0ebc3959d39c39e10000000a114084/frameset.htm

Created on July 18, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis 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 SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable 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 expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 68

Table of content1 SAP Patient Management1.1 Industry Solution Hospital1.2 Basic Data1.2.1 Hospital Structure1.2.1.1 Input Help for Organizational Hierarchy1.2.1.2 Maintaining Personal Value Help1.2.1.3 Organizational Structure1.2.1.3.1 Creation of Organizational Structure1.2.1.3.2 Organizational Unit1.2.1.3.2.1 Organizational Unit: Name and Address Data1.2.1.3.2.2 Organizational Unit: Blocking Indicator1.2.1.3.2.3 Organizational Unit: Validity Dates1.2.1.3.2.4 Organizational Unit: Specialty Keys1.2.1.3.2.5 Organizational Unit: Departmental Per Diem1.2.1.3.2.6 Example: Departmental Per Diem of Departmental and Nursing OU1.2.1.3.2.7 Organizational Unit: Indicators Relevant to Processing1.2.1.3.2.8 Organizational Unit: Division (CH)1.2.1.3.2.9 Organizational Unit: Assign Physician (AT)1.2.1.3.2.10 Identification Key for Organizational Units1.2.1.3.2.11 Creating Organizational Units1.2.1.3.2.12 Maintain Organizational Units: Initial Screen1.2.1.3.2.13 Changing Organizational Units1.2.1.3.2.14 Flagging Organizational Units for Deletion1.2.1.3.2.15 Canceling the Deletion Flag for Organizational Units1.2.1.3.2.16 Blocking/Unblocking Organizational Units1.2.1.3.3 Organizational Hierarchy1.2.1.3.3.1 Example: Organizational Hierarchy1.2.1.3.3.2 Maintain the Organizational Hierarchy1.2.1.3.3.3 Displaying the Hierarchy Overview Graphic1.2.1.3.3.4 Interdepartmental Relationships1.2.1.3.3.5 Maintain Interdepartmental Relationships1.2.1.3.4 Maintaining Organizational Unit-to-Building Unit Assignments1.2.1.3.5 Maintaining Statistical Bed Figures1.2.1.3.6 Release Organizational Structure1.2.1.3.7 Transport Organizational Units1.2.1.3.7.1 Transporting Organizational Units1.2.1.4 Building Structure1.2.1.4.1 Creation of Building Structure1.2.1.4.2 Building Units1.2.1.4.2.1 Building Unit: Name Data1.2.1.4.2.2 Building Unit: Validity Dates1.2.1.4.2.3 Building Unit: Coordinate Data1.2.1.4.2.4 Assignment of Identification Keys for Building Units1.2.1.4.2.5 Create Building Units1.2.1.4.2.6 Creating Building Units: Single Entry1.2.1.4.2.7 Maintain Building Units: Initial Screen1.2.1.4.2.8 Changing Building Units: Collective Entry1.2.1.4.2.9 Create Building Units: Collective Entry Screen1.2.1.4.2.10 Change Building Units1.2.1.4.2.11 Changing Building Units: Single Entry1.2.1.4.2.12 Changing Building Units: Collective Entry1.2.1.4.2.13 Flagging Building Units for Deletion1.2.1.4.2.14 Canceling the Deletion Flag for Building Units1.2.1.4.2.15 Blocking/Unblocking Building Units1.2.1.4.2.16 Blocking Building Units on an Hourly Basis1.2.1.4.3 Building Hierarchy1.2.1.4.3.1 Maintaining the Building Hierarchy1.2.1.4.3.2 Displaying the Building Hierarchy Overview1.2.1.4.3.3 Planning Characteristics of Building Units1.2.1.4.3.3.1 Maintain Planning Characteristics


Page 2 of 68

1.2.1.4.3.4 Facilities of Building Units1.2.1.4.3.4.1 Maintaining Facilities of a Building Unit1.2.1.4.3.5 Release of Building Structure1.2.1.4.3.5.1 Releasing the Building Structure1.2.1.4.3.6 Transport Building Units1.2.1.4.3.6.1 Transporting Building Units1.2.1.4.4 Maintain Building Units for Care Unit Graphic1.2.1.4.4.1 Planning the Graphical Representation of the Care Unit Structure1.2.1.4.4.2 Example of Care Unit Aligned with SAP Coordinate System1.2.1.4.4.3 Rooms in the Care Unit Overview Graphic1.2.1.4.4.4 Corridors in the Care Unit Overview Graphic1.2.1.4.4.5 Bed Locations in the Care Unit Overview Graphic1.2.1.4.4.6 Doors in the Care Unit Overview Graphic1.2.1.4.4.6.1 Define the Location of Room and Corridor Doors1.2.1.4.4.6.2 Examples of Vertical and Horizontal Doors1.2.1.4.4.6.3 Maintaining Doors1.2.2 Business Partner1.2.2.1 BAPIs for Business Partners1.2.2.2 Business Partner Concept1.2.2.3 Business Partner Identification Key1.2.2.4 Business Partner Search1.2.2.5 Business Partner List1.2.2.6 Creation of Business Partners: Strategies1.2.2.6.1 General Business Partner Data1.2.2.6.2 Creating General Business Partners1.2.2.6.3 General Business Partner: Initial Screen1.2.2.6.4 General Business Partner: Entry Screen1.2.2.7 Blocking Business Partners1.2.2.8 Unblocking Business Partners1.2.2.9 Displaying the Blocking Interval of the Business Partner1.2.2.10 Deletion of Insurance Providers1.2.2.10.1 Flagging Business Partners for Deletion1.2.2.10.2 Displaying Business Partners Flagged for Deletion1.2.2.10.3 Cancelling the Deletion Flag for Business Partners1.2.2.10.4 Deleting Insurance Providers Flagged for Deletion1.2.2.10.5 Deletion of Insurance Providers: Selection Criteria1.2.2.11 Display of Business Partner Administrative Data1.2.2.11.1 Displaying the Administrative Data of General Business Partners1.2.2.12 Business Partner Functions1.2.2.12.1 Displaying the Administrative Data of Business Partner Functions1.2.2.12.2 Creating Business Partner Functions1.2.2.12.3 Employer (Business Partner Function)1.2.2.12.4 Insurance Provider (Business Partner Function)1.2.2.12.4.1 Insurance Provider-Specific Master Data1.2.2.12.4.2 Insurance Provider: Insurance Provider Type1.2.2.12.4.3 Ins. Prov.: Relevant Fields for Importing Healthcare Smart Card1.2.2.12.4.4 Example: Head Office and Branch Determination at Healthcare Smar1.2.2.12.4.5 Insurance Provider: Head Office1.2.2.12.4.6 Insurance Provider: Health Insurer Search Name1.2.2.12.4.7 Insurance Provider: Control Parameters1.2.2.12.4.8 Find Insurance Providers Without Customers1.2.2.12.4.9 Determine Insurance Providers Without Customers1.2.2.12.5 IS-H Customer (Business Partner Function)1.2.2.12.5.1 Customer-Specific Master Data1.2.2.12.5.2 Creating IS-H Customers1.2.2.12.5.3 Creating Customers in IS-H and FI1.2.2.12.5.4 Sensitive Fields1.2.2.12.5.5 Creating IS-H Customers and Assigning FI Customers1.2.2.12.5.6 Assigning FI Customers to IS-H Customers1.2.2.12.5.7 Changing Customers1.2.2.12.5.8 Create Bank Details1.2.2.12.5.9 Edit Bank Details List


Page 3 of 68

1.2.2.12.5.10 Determination of IS-H Customers Without FI Customers1.2.2.12.6 Hospital (Business Partner Function)1.2.2.12.6.1 Hospital in Insurance Provider Role1.2.2.12.7 Employee/Physician (Business Partner Function)1.2.2.12.8 External Ordering Party (Business Partner Function) [CH]1.2.2.12.9 Fee Recipient (Business Partner Function) [CH]1.2.2.12.10 Assign Contract Partner Number (AT)1.2.3 Service Master Data1.2.3.1 Service Master1.2.3.1.1 Creating the Service Master1.2.3.1.2 Service Master: Initial Screen1.2.3.1.3 Service Master: Service Texts1.2.3.1.4 Service Master: Columns1.2.3.1.5 Service Master: Classification1.2.3.1.6 Service Master: Other1.2.3.1.7 Service Master: Medical Indicators1.2.3.1.8 Service Master: Communication1.2.3.1.9 Service Master: FR/PS (Germany)1.2.3.1.9.1 Important Master Data for FR/PS (Germany)1.2.3.1.9.2 Maintaining Add. Data for FR/PS (Germany)1.2.3.1.9.3 Add. Data: Displaying and Delimiting Validity Intervals (Germany1.2.3.1.10 Service Master: Additional Data (Switzerland)1.2.3.1.10.1 Maintaining Add. Data for Service Catalogs and Fees (Switzerland1.2.3.1.10.2 Maintaining Additional Data for TARMED (Switzerland)1.2.3.1.10.2.1 Maintain Swiss Service Master (TARMED) Using Tables1.2.3.1.10.2.2 Import TARMED Service Master Data (Switzerland)1.2.3.1.10.3 Import Tariff Types (Switzerland)1.2.3.1.10.4 Alternative Service Code (Switzerland)


Page 4 of 68

1 SAP Patient Management

Industry Solution Hospital

PurposeAn enhancement of the standard system designed specifically for use in hospitals. It supports patient management, medical and nursing documentation, andpatient accounting, and integrates these with

Financial Accounting Controlling Materials Management

The information system contains evaluations of patient and hospital data that can be used both internally and externally. This industry solution also contains acommunication component that enables data transfer both within the hospital and to external parties.

1.2 Basic Data Important master data on which Patient Management and Patient Accounting are based.

FeaturesMaster data includes:

Organizational unitsBuilding unitsBusiness partner dataService master dataCatalogsClinical work station

1.2.1 Hospital Structure Modeling of the organizational structure and building structure of a hospital in hierarchical form.

IntegrationYou 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 andbeds) in Care Unit Management or Outpatient Clinic Management and want to assign patients to rooms and beds. You also must have created the buildingstructure to be able to use the care unit graphic.

FeaturesYou model the structure of your hospital in the IS-H system using organizational and building structures.

For Information On SeeOrganizational structure Organizational Structure

Creation of Organizational Structure: Procedure in OverviewOrganizational UnitsOrganizational HierarchyInter-Departmental RelationshipsStatistical Bed FiguresRelease of Organizational StructureTransport Organizational Units

Building structure Introduction to the Building StructureCreation of Building Structure: Procedure in OverviewBuilding Units


Page 5 of 68

Building HierarchyMaintain Organizational Unit-to-Building Unit AssignmentsPlanning Characteristics of Building UnitsFacilities of Building UnitsMaintenance of Building Units for Care Unit Overview GraphicRelease of Building StructureTransport Building Units

1.2.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.

NoteTo enable personalization to be configured centrally, you can copy the personal settings for the organizational hierarchy input help from one user to anotherusing program RNUHLP00. For more information about this, see the program documentation.

Features

Personal Value ListYou can custom tailor the display of the organizational hierarchy to satisfy your needs. This involves maintaining a personal value list that is then displayed bydefault when you call the input help. Additional fields are available to you for outputting information (for example, category, name and telephone number of theorganizational/building unit).

NoteYou should use additional fields sparingly, otherwise entries can run into the next line.

Activities

Maintain Personal Value ListYou can maintain the personal value list either using ( - ) or using the personalization settings (Ctrl + F4). When you insert an organizational unit in thepersonal 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 thecomplete hierarchy by choosing the globe symbol.

NoteIf you have maintained personal values for the input help, the cursor is only positioned on an organizational unit already entered in the list if thecorresponding path is found in the personal values.

You can expand all nodes of the hierarchy in one go.

NoteYou can accelerate the generation of the hierarchy using the new institution-specific, time-independent system parameter OE_LOAD. Read thedocumentation relating to this system parameter in the IS-H Implementation Guide by choosing Basic Settings System Parameters MaintainInstitution-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.2.1.2 Maintaining Personal Value Help

ProcedureTo 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, andchoose ( Add to Favorites ).

The hierarchy path is inserted in your personal value list.


Page 6 of 68

Alternative ProcedureYou 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 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 aredisplayed in the right section.

3. You can insert selected paths in your personal value selection, or remove them using the ( - ) and ( - ) pushbuttons.

NoteYou can exclude particular organizational categories from the display. Specify the organizational categories that are not to be displayed under Do notdisplay organizational categories on the Settings tab page.

NoteYou can stipulate that outpatient clinics should no longer be included in your personal value list for OUs.You can stipulate that care units should no longer be included in your personal value list for OUs.

1.2.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 anorganizational unit, you assign an organizational category to it. The organizational category determines which organizational units can be brought into relationwith 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 OrganizationalUnit Categories of the IS-H Implementation Guide .

ExampleExamples of such categories are:

ClinicDepartmentCare UnitAdmitting DepartmentOutpatient clinic

You create an organizational unit with the appropriate organizational category for each organizational unit in your institution. The organizational category determineswhich attributes you can store for an organizational unit.

ExampleExamples of such attributes are:

Outpatient treatmentDepartmental assignmentNursing assignmentSupports interdepartmental bed assignment

The organizational structure you define in the IS-H System is used in the following areas:

Area UsePatient 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 determineswhether you can store different services on different levels of the organizationalhierarchy.

Statistics Statistics evaluate specific data in relation to organizational units, for example the patientcensus, 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 assignedorganizational units to cost centers. You should, therefore, also include service facilitiessuch as laboratories and X-ray departments in the organizational hierarchy, so as to beable to post to the corresponding cost centers when carrying out internal activityallocation.

Prior to creating an organizational structure, you should analyze which results you require in the respective areas and create the organizational structureaccordingly.

1.2.1.3.1 Creation of Organizational Structure


Page 7 of 68

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 theorder specified.

Process1. Creating Organizational Units2. Maintain the Organizational Hierarchy3. Maintain Interdepartmental Relationships4. Maintain Organizational Unit-to-Building Unit Assignments5. Release Organizational Structure

1.2.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 departmentalorganizational unit.

On Tab Page You Store the Following Data...Label Name Data

Blocking indicatorValidity dates

Specialty, Indic. Specialty KeyDepartmental per DiemIndicators Relevant for Assignment/Occupancy

Other Data Other DataAddress AddressGen. Switzerland Division (country version Switzerland only)

More InformationIdentification Key for Organizational UnitsCreating Organizational UnitsChanging Organizational UnitsBlocking/Unblocking Organizational UnitsFlagging Organizational Units for Deletion

1.2.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 NameYou specify the long name of the OU here.OU Short TextYou 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 andthe organizational unit hierarchy.

NoteTo ensure the short text is maintained for each OU, you should define the corresponding field as a required-entry field in Customizing. For moreinformation about this, see the Section Maintain Screen Modification of the IS-H Implementation Guide .

OU IdentifierThe 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 organizationalhierarchy.To list the identifiers already used, choose Extras Existing Identifier List .

NoteThe identifiers are not supported in the Clinical Process Builder.

ActivitiesEnter the name data on the Description tab page.Enter the address of the OU on the Address tab page.


Page 8 of 68

1.2.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 theblocking 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 beused again.

ActivitiesYou can select or deselect the blocking indicator on the Description tab page. For the exact procedure, see Blocking/Unblocking Organizational Units.

1.2.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 movementsor other OUs within the organizational structure to OUs outside of their specified validity periods.

NoteIf 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 themovements 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.

ActivitiesYou enter the validity dates on the Description tab page.

1.2.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 government-mandated statistics byspecialty. 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 underNo Specialty Assigned in the statistics.

PrerequisitesIn Customizing for IS-H, you specify according to which statutory regulations you assign OUs to specialties. For more information about this, see the sectionsentitled Define Specialty Categories, Code Specialties and Maintain Specialty Hierarchy in the IS-H Implementation Guide.The following possibilities exist:

Statutory regulations GermanySpecialties pursuant to the Federal Regulation for Hospitals 1995Specialties pursuant to the Federal Regulation for Hospitals 1985Specialties pursuant to Statistical Regulatory RequirementsSpecialties pursuant to the Nursing Staff Regulation

Statutory regulations AustriaSpecialties pursuant to KRAZAFRegulations NetherlandsSpecialties pursuant to POLIS

Additionally, you can classify OUs according to specialties of your choosing.

ActivitiesYou assign specialties to OUs on the Specialty, indic . tab page.

1.2.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 patientis assigned to this OU.

Features


Page 9 of 68

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 OUIn 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 thedepartmental 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 OUShould certain departmental per diem charges only be billed for for stays on particular nursing organizational units of a department, you can specify this in themaster data of the nursing OU. The system then enters the departmental per diem of the nursing OU rather than that of the departmental OU.

CautionIf 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 thisOU (inter-departmental bed assignment authority), the system always enters, in relation to a case, the departmental per diem of the nursing OU, irrespectiveof 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 OUIn 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 servicesare 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 asfollows (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 nursingOU. 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 OUIf 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 assignpatients 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 actualdepartmental OU in the organizational hierarchy. You subordinate the nursing OU to the auxiliary organizational unit.

Example 2

ActivitiesYou can store the departmental per diem for an OU on the Specialty, Indic. tab page.

1.2.1.3.2.6 Example: Departmental Per Diem of Departmentaland Nursing OU The example below illustrates two departmental organizational units (OUs), each of which is assigned a specific departmental per diem. An alternative


Page 10 of 68

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 EnteredSurgery Surgery unit 1 SRGFRSurgery Surgery unit 2 SRGU2FRSurgery Surgery intensive care INTFRUrology Urology unit 1 UROFRUrology Urology unit 2 UROFRUrology Surgery intensive care INTFRUrology Surgery unit 2 SRGU2FR

1.2.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 theOU.

FeaturesThe indicators listed below are available to you. You can obtain comprehensive information about each indicator via the F1 help. The following documentationconsiders only specific aspects of using the indicators in the system.

Indicators Relevant for Assignment/OccupancyDepartmental AssignmentNursing assignmentOutpatient visitInter-departmental assignment authorityInter-departmental OUIntensive care treatmentOUs 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 requirementsIn 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 ofstay of the intensive care stay.In the maintenance of nursing acuities pursuant to the Nursing Staff Regulation.

NoteThe intensive care treatment indicator is not taken into account in statistics (with the exception of statistics pursuant to hospital statistical regulatoryrequirements). OUs are considered as intensive care units only if they are assigned to a specialty for which the intensive care indicator is set inCustomizing for IS-H. For more information about this, see the Section Code Specialties of the IS-H Implementation Guide and the FI help for theintensive care treatment indicator ( I field) in the corresponding Customizing table.

Other DataAdmitting DepartmentWithin admission data you can specify the facility that admits the patient. You can only specify OUs for which this indicator is set.Medical record archiveIn 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 bean organizational unit for which you have set this indicator.Pediatric indicatorYou set this indicator for departmental and nursing OUs of pediatrics.


Page 11 of 68

When maintaining nursing acuities pursuant to the Nursing Staff Regulation (Germany), you classify cases that are assigned to an OU with the pediatricindicator using the nursing acuities of infant and children care.Exclusion from nursing acuity classificationYou set this indicator for OUs that are excluded from the regulatory nursing acuity classification (Germany). These include dialysis units and psychiatricunits.Data protectionIf 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 displayauthorization.Care Unit Storage LocationIf 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 careunit storage facility.CalendarIn 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. Formore information about this, see the section entitled Define Organizational Unit Categories in the IS-H Implementation Guide .

ActivitiesYou 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.2.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.2.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.

1.2.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). InCustomizing for IS-H, you can specify whether one of these two number assignment methods should be excluded. In Customizing, you can also define the numberranges authorized for internal and external number assignment.

NoteIf 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 identificationkey 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 numberassignment, 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.

NoteIf you have defined several institutions in one client and are using external number assignment, you can specify a prefix for each institution which the systemplaces at the start of the identification key of the institutions. This enables you to designate the organizational units which belong to the organizational structureof an institution.

1.2.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 unitwith 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 OUOU IdentifierRelease IndicatorThe system automatically sets the release indicator when you release the organizational structure.

Procedure1. 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.


Page 12 of 68

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 DataOrganizational Unit: Departmental Per DiemOrganizational Unit: Specialty KeysOrganizational Unit: Indicators Relevant to ProcessingOrganizational Unit: Validity DatesOrganizational 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 thanthe 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 doubleclicking the Higher OU field.

4. Save the data.

1.2.1.3.2.12 Maintain Organizational Units: Initial Screen To create an organizational unit (OU), specify the following data on the initial screen:

InstitutionSpecify the institution for which you want to create the OU.Identification key of the OUIf you are working with internal number assignment, leave the Organizational Unit field blank. The system automatically assigns an identification keywhen you save the data.If you are working with external number assignment, enter the required identification key in the Organizational Unit field.Type of OUSpecify the category of the organizational unit to be created in the OU Category field. The organizational unit categories available depend on the specifiedinstitution.TemplateIf 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 theOrganizational 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 theidentification key, you select it from the value help.

1.2.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 OUsto not released :

Change to the validity datesChange to the organizational hierarchyYou change the organizational hierarchy whenever you change the higher-level OU in the master data of the OU.

CautionNote that making changes to organizational units in production operation can lead to inconsistencies within existing data.

Procedure1. Choose Hospital Basic Data Administration Hospital Structure Organizational Structure Organizational Unit Change on the SAP Easy

Access screen.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 DataOrganizational Unit: Departmental Per DiemOrganizational Unit: Specialty KeysOrganizational Unit: Indicators Relevant to ProcessingOrganizational Unit: Validity DatesOrganizational Unit: Blocking Indicator

NoteIf 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 issituated outside the validity period of the OU. To do this, choose Check Consistency . Note that this consistency check can take a long time and mayterminate if the runtime exceeds the maximum dialog time.

5. Save the data.You return to the initial screen.

1.2.1.3.2.14 Flagging Organizational Units for Deletion


Page 13 of 68

PrerequisitesYou cannot delete organizational units (OUs) directly. Deleting OUs without first checking whether dependent objects exist would constitute a serious threat to dataconsistency 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 areretained. 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 fordeletion. 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.

NoteOUs flagged for deletion are not listed in the input help.




The organizational unit entry screen appears.4. Choose Set Deletion Flag .

A dialog box appears. Confirm that you want to flag the building unit for deletion by choosing ( Continue ).5. Save the data.

You return to the initial screen.

More InformationCanceling the Deletion Flag for Organizational Units

1.2.1.3.2.15 Canceling the Deletion Flag for Organizational Units




The entry screen of the OU appears.4. Choose Organizational unit Deletion flag Cancel .

A message box informs you that that the deletion flag was canceled. Confirm this message by choosing ( Continue ).5. Save the data.


More InformationFlagging Organizational Units for Deletion

1.2.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 subsequentfunctions. 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.




The Change Organizational Unit: Administrative Data screen appears. Your cursor is positioned on the Description tab page.4. To block the OU, select Blocking indicator .5. To unblock the OU, deselect Blocking indicator .6. Save the data.



Page 14 of 68

1.2.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. Todo 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 thecorresponding assignment records in the organizational hierarchy.

StructureThe 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 IS-H, you specify whichbuilding categories may be assigned to each other. For more information about this, see Maintain Hierarchy of Organizational Unit Categories in the IS-HImplementation Guide .

More InformationMaintain the Organizational HierarchyDisplaying the Hierarchy Overview Graphic

1.2.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 thesystem.

CautionDo not assign departmental OUs below nursing or treatment OUs (i.e. care units or outpatient clinics) in the hierarchy.

CautionDo not make recursive assignments.

1.2.1.3.3.2 Maintain the Organizational Hierarchy


Page 15 of 68

Procedure1. 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 AssignmentsDisplay and Change Existing AssignmentsDelete Existing Assignments

Now proceed with the following steps in relation to the processing option you wish to use:

Create New Assignments Display and Change Existing Assignments Delete Existing Assignments

1. Choose ( Create ).The Maintain Organizational Hierarchy screenappears.

2. Specify the identification keys of the OUs you wantto assign to one another.You need to have created these organizational unitsbeforehand. You can only assign OUs to each otherif both OUs are created in the same institution.The system uses the validity period common toboth organizational units as the default validityperiod for the assignment. You can further restrictthe validity period of the assignment.

3. Save the data.You return to the list of existing assignments.

1. Select an entry, and then choose ( Details ).The assignment detail screen appears. Theinstitution for which this assignment is valid isdisplayed in the Hierarchy group box.

2. Change the data as required, and then save.A dialog box appears containing the changed data.

3. Confirm the changes by saving the data.You return to the list of existing assignments.

The detail screen provides a navigation function to enableyou to edit individual assignment records quickly anddirectly. To go directly from the detail screen to the detailscreen of the next entry, choose ( - ). To go to the detailscreen of a specific entry, specify the data of the requiredentry in at least one field in the Table Entry Selectiongroup box. Then choose ( - ).To display the master data of the assigned OUs, you candouble-click (choose) the required OU on the assignmentdetail screen.

1. Select the entry you want to delete, and then choose ( Details ).

The assignment detail screen appears.2. Choose ( Delete ).

A confirmation prompt is issued.3. Confirm the delete operation.

The system deletes the entry and returns to the listof existing assignments.

1.2.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 youcan specify for which OU you want to display all the lower-level (dependent) OUs.

Procedure1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Organizational Structure 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.

NoteIf 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.

1.2.1.3.3.4 Interdepartmental Relationships In addition to the organizational relationships between organizational units (OUs) you define within the organizational hierarchy, interdepartmental relationships canalso exist between OUs. An interdepartmental relationship exists if one OU is authorized to assign patients to beds on another OU even though no organizationalrelationship 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.AsgmtAuth . 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 bemade.The following illustration is an example of an organizational hierarchy with interdepartmental relationships.


Page 16 of 68

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 ofthe surgery department.

CautionDo 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 alsoflagged as departmental OUs and as authorized to assign patients to beds on OU of other department (Interdept. Asgmt Auth. indicator set).

More InformationMaintain Interdepartmental Relationships

1.2.1.3.3.5 Maintain Interdepartmental Relationships

Procedure1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Organizational Structure Interdept. Bed

Asgmt Maintain .The list of existing assignments appears.

2. The following editing options are available from this list:Create New AssignmentsDisplay and Change Existing AssignmentsDelete Existing Assignments

Now proceed with the following steps depending on the editing option you are using:Create New Assignments Display and Change Existing Assignments Delete Existing Assignments

1. Choose ( Create ).The assignment detail screen appears.

2. In the Org. Unit field, enter the identification keyof the OU to whose beds patients can beassigned by OUs of other departments. In theAsgmt By field, specify the identification key of

the OU with inter-departmental assignmentauthority.You need to have created these organizationalunits beforehand.In the Max. Number of Beds field, you canspecify the maximum number of beds on thecare unit to which the department may assignpatients from other departments. You can displaythis specification in the bed scheduling function ofcare unit management. When you assign

1. Select an entry, and then choose ( Details ).The assignment detail screen appears.

2. Change the data as required, and then save.3. If you have changed the validity dates, a dialog

box containing the changed time intervalsappears. Confirm the changes by choosing ( Save ).

4. If you have changed the OU assignment, thesystem deletes the changed entry and creates anew entry. It issues a warning messageaccordingly. Confirm this operation by choosing

( Continue ).You return to the list of existing assignments.The detail screen provides a navigation function toenable you to edit individual assignment records quicklyand directly. To go directly from the detail screen to the

1. Select the entry to be deleted, and then choose ( Details ).



The system deletes the entry and returns to the list ofexisting assignments.


Page 17 of 68

patients, at present the system does not checkwhether the maximum number of inter-departmental beds has been reached.The system uses the validity period common toboth organizational units as the default validityperiod for the assignment. You can further restrictthe validity period of the assignment.You can specify sort numbers in the Sort Orderfield. These are taken into account when the listof free bed locations is output.


and directly. To go directly from the detail screen to thedetail screen of the next entry, choose ( - ). To go tothe detail screen of a specific entry, specify the data ofthe required entry in at least one field in the Table EntrySelection group box. Then choose ( - ).To display the master data of the assigned OUs, youcan double-click (choose) the required OU on theassignment detail screen.

1.2.1.3.4 Maintaining Organizational Unit-to-Building UnitAssignments You create the link between the organizational hierarchy and the building hierarchy by assigning building units to organizational units (OUs). You can define thebuilding 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) andbuilding units located at the uppermost level of the building hierarchy (for example, rooms, corridors).

Multiple Assignment of Building UnitsYou 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 structureAs 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 isalso 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 differentoutpatient clinics/service facilities For more information, see Multiple Assignment of Building Units in Visit Scheduling.

PrerequisitesThe organizational units and building units for which you want to create an assignment must already exist.

NoteThe 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 whichorganizational unit categories may be assigned to which building unit categories.

Procedure1. 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:

Create New AssignmentsDisplay and Change Existing AssignmentsDelete Existing Assignments

2. Now proceed with the following steps depending on the editing option you are using.

Create New Assignments1. Choose ( Create ).

The assignment detail screen appears.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 furtherrestrict the validity period of the assignment.


Display and Change Existing Assignments1. Select an entry, and then choose ( Details ).

The assignment detail screen appears.2. 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 ).3. 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.4. 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 inthe Table Entry Selection group box. Then choose ( - ).


Page 18 of 68

5. 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.

Delete Existing Assignments1. Select the entry to be deleted, and then choose ( Details ).



The system deletes the entry and returns to the list of existing assignments.

1.2.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. Specifyingstatistical bed figures for a combination of departmental and nursing OUs enables you to also enter statistical bed figures for OUs whose beds are assignedpatients 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 valuesaccording to a number of criteria.

Country Version GermanyIn 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.

Procedure1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Organizational Structure Statistical Beds

Maintain .The Maintain Statistical Bed Assignments screen appears with the existing entries.

2. The following editing options are available from this list:Create New EntriesDisplay and Change Existing EntriesDelete Existing Entries

Now proceed with the following steps depending on the editing option you are using:Create New Entries Display and Change Existing Entries Delete Existing Entries

1. Choose ( Create ).The detail screen appears.

2. Specify the identification key of the OU for whichyou want to store statistical bed figures. This canbe the departmental OU or the nursing OU or acombination of both.You need to have created these organizationalunits beforehand.Note the validity period of the statistical bedfigures. The system uses the validity period ofthe OU per default. If you specified adepartmental OU and nursing OU combination,the system uses the validity period common toboth organizational units as the default validityperiod for the assignment.You can specify the validity of the statistical bedfigures in the Valid From and Valid To inputfields. The system displays the validity periods ofthe OUs in the display fields with the samename.

3. Specify the statistical bed figures. For informationabout the various input fields, see the F1 help.

4. Save the data.You return to the list of existing entries.

1. Select an entry, and then choose ( Details ).The detail screen appears.

2. Make any necessary changes.To display the master data of the OUs specified,double-click (choose) the required OU on thedetail screen.

3. Save the data.You return to the list of existing entries.The detail screen provides a navigation functionto enable you to edit individual assignmentrecords quickly and directly. To go directly fromthe detail screen to the detail screen of the nextentry, choose ( - ). To go to the detail screen ofa specific entry, specify the data of the requiredentry in at least one field in the Table EntrySelection group box. Then choose ( - ).

1. Select the entry you want to delete, and thenchoose ( Details ).The detail screen appears.

2. Choose ( Delete ).A confirmation prompt is issued.

3. Confirm the delete operation.The system deletes the entry and returns to thelist of existing entries.

1.2.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 thatthe 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 keyof 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.


Page 19 of 68

NoteWhen releasing the organizational hierarchy the system checks the assignment of building units to OUs for consistency. However, it does not release thebuilding 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 validityChange to the organizational hierarchyChange to the assignment of OUs to building unitsChange 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 thisOU in the organizational hierarchy. To release these OUs again, you have to release the entire organizational structure once more.

Procedure1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Organizational Structure 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 testmode. 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 the OUs. To enablethis 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 organizational structure and then displays the log. The log shows which OUs have beenreleased and which have not been released.

1.2.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 requestor create a new one.

CautionDo 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.

PrerequisitesEnsure that no inconsistencies arise when transporting OUs to another client or another system.

CautionThe 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 customizingchanges.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 systemThe OUs have a different identification key in the source systemThe OUs were created in a different order in the source systemThe order in which the OUs are created can lead to inconsistencies since address management essentially works with internal assignment and as aresult 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 thesource 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 toexecuting the transport. You could then run the release program in test mode in the target system to check the result of the transport.

FeaturesYou can further restrict the OUs data to be transported by using the following selection criteria on the program selection screen:

InstitutionOUCreation dateChanged on


Page 20 of 68

Include the assignments of OU to cost centersIf you wish to include the OU-to-cost center assignments in the transport operation, select With OU-to-Cost Center Asgt .

NoteThe selection criteria are linked by an AND operator. Thus if you enter an interval for building unit creation and change, the transport will include theOUs 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 creationinterval and a second time specifying the change interval. For this reason there may be duplicate entries in the request. These do not represent aproblem.

The following data is included in the transport request:OUs flagged for deletion, to ensure that the flag is passed on to the target systemLong texts for the OUs selectedEntries for the organizational hierarchyInter-departmental assignmentsAssignment to building unitsStatistical bedsGeneric 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 thedependent tables.

Example Entries for Statistical BedsEntries Transport request* - * These entries for the statistical beds are never included.* - SURG1 These entries would be included, if the OU SURG1 were selected.

NoteThis 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 ExecutionYou 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 transportrequest in live mode. However, the objects to be transported are not actually included in the transport request. To execute the program in test mode, selectTest 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 InformationTransporting Organizational Units

1.2.1.3.7.1 Transporting Organizational Units

Procedure1. From the SAP Easy Access screen, choose Hospital Statistics/Information Report Tree Basic Data Hospital Structure IS-H: 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 requestNumber of the taskNumber of records included per table

1.2.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 organizationalstructure 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 structureInformation functions, for instance public list with room specifications


Page 21 of 68

Outpatient clinic managementCare unit overview graphicPatient assignment to rooms and beds

1.2.1.4.1 Creation of Building Structure To create the building structure, work through the following activities in the order specified.

Process1. Maintain building structure:

For more information about this, see Building Structure and the related sections.2. Maintaining building hierarchy:

For more information about this, see Building Hierarchy and the related sections.3. Maintain relationships to organizational structure:

For more information about this, see Maintaining Organizational Unit-to-Building Unit Assignments.4. Maintain planning characteristics:

For more information about this, see Maintaining Planning Characteristics.5. Maintain facility characteristics:

For more information about this, see Maintaining Facilities of a Building Unit.6. Maintain doors:

For more information about this, see Maintaining Doors.7. Release building structure:

For more information about this, see Releasing the Building Structure.

1.2.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 BuildingUnit Categories in the IS-H Implementation Guide .

StructureYou can store the following data within the master data of a building unit:

Building Unit: Name DataBuilding Unit: Validity DatesBuilding Unit: Coordinate Data

IntegrationOnly categories of building units which you have characterized as rooms or bed locations in Customizing for IS-H are of functional significance. The followingfunctions are supported for rooms and bed locations:

Assignment of patients to rooms and bed locationsGraphical representation in the care unit overview graphic

More InformationAssignment of Identification Keys for Building UnitsCreate Building UnitsChange Building UnitsBlocking/Unblocking Building UnitsFlagging Building Units for DeletionCanceling the Deletion Flag for Building Units

1.2.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 textYou 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


Page 22 of 68

defined for the room.Building unit identifierThe identifier of the building unit is output on many screens, for example in the case list, the care unit overview graphic, the room and 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 orbuilding unit located above them in the hierarchy.You can use the identifier when entering the patient assignment.

NoteTo ensure the short text is maintained for each building unit, you should define the corresponding field as a required-entry field in Customizing.

NoteIn 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 bedlocation is situated. If you work with the enhanced occupancy list, you should define the bed location identifiers such that they also contain the roomidentification.

1.2.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 organizationalunits outside of their specified validity period. It is also impossible to assign patients to them.

NoteIf 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 thatthe 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.2.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 overviewgraphic. 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 InformationMaintain Building Units for Care Unit GraphicRooms in the Care Unit Overview GraphicCorridors in the Care Unit Overview GraphicBed Locations in the Care Unit Overview Graphic

1.2.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 numberassignment). In Customizing for IS-H, you can specify whether one of these two number assignment methods should be excluded. In Customizing, you can alsodefine 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 internalnumber assignment, the system always selects the next number from the internal number range. With external number assignment, the system prevents anumber, which is already assigned, from being assigned again.

NoteIf you work with external number assignment, choose the identification keys such that you can quickly create building units of several organizational units bycopying the identification key and making slight changes to the resulting copy. For instance, if the building structure of different floors is similar, you caninclude 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 furtherbuilding units and only have to change the floor number in the identification key.

NoteIf you have defined several institutions in one client and are using external number assignment, you can specify a prefix for each institution which the systemplaces 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


Page 23 of 68

institution.

1.2.1.4.2.5 Create Building Units You can use the following editing methods to create building units:

Creating Building Units: Single EntryYou 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 EntryIn collective entry, you can create several building units on a collective entry screen and in doing so subordinate them to building units or organizationalunits. You cannot maintain the complete master data of the building unit on the collective entry screen. You can, however, go directly from collective entry tothe master data of the building unit.

1.2.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 requiredcategory 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 templatebuilding unit as default values into the new master record. The following data is not transferred:

Building unit identifierRelease IndicatorThe system automatically sets the release indicator when you release the building structure.

Procedure1. 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 DataBuilding Unit: Validity DatesBuilding Unit: Coordinate Data


1.2.1.4.2.7 Maintain Building Units: Initial Screen To create a building unit, specify the following data on the initial screen:

InstitutionSpecify the institution for which you want to create the building unit.Identification key of the building unitIf you are working with internal number assignment, leave the Building unit field blank. The system automatically assigns an identification key whenyou save the data.If you are working with external number assignment, enter the required identification key in the Building unit field.Building unit categorySpecify the category of the building unit to be created in the Build. unit category field.TemplateIf you want to use an existing organizational unit as a copying template when creating your OU, specify the identification key of the existing organizationalunit 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 theidentification key, you select it from the value help.

1.2.1.4.2.12 Changing Building Units: Collective Entry

Procedure1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Building 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.

NoteYou 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


Page 24 of 68

choose ( Details ). The master data of the building unit appears. To return to the overview screen, choose ( Back ). When you save the masterdata 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 overviewscreen.

4. You can confirm your entries by choosing ( Check ) or ( Enter ). The system checks the consistency of the data, and changes the Bld. unit inputfield 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.

NoteProvided 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.2.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 KeyIf 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 savethe data..Building unit categorySpecify 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 textYou enter the short text of the organizational unit in this field.Building unit identifierThe 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 orbuilding unit located above them in the hierarchy.Validity datesYou 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 wayyou simultaneously maintain the building hierarchy or the link between the organizational hierarchy and the building hierarchy. You can do this only if the buildingunit or organizational unit to which you subordinate the building unit already exist.

Assignment to a building hierarchyTo 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 thehigher level building unit in the Higher BU field.Assignment to an organizational hierarchyTo 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 theHigher OU field.

1.2.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 EntryYou 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.Changing Building Units: Collective EntryIn collective entry, you can change several building units on a collective entry screen and in doing so change their assignment to other building units ororganizational units. You cannot maintain the complete master data of the building unit on the collective entry screen. You can, however, go directly fromcollective 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 datesChange to the assignment to building units or organizational units

1.2.1.4.2.11 Changing Building Units: Single Entry

Procedure1. 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 identifierValidity datesCoordinates


Page 25 of 68

NoteIf 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 amovement that is situated outside the validity period of the building unit. To do this, choose ( Consistency ). Note that this consistency check can takea long time and may terminate if the runtime exceeds the maximum dialog time.


1.2.1.4.2.12 Changing Building Units: Collective Entry

Procedure1. On the SAP Easy Access screen, choose Hospital Basic Data Administration Hospital Structure Building Structure Building Unit

Collective Entry .The Collective Entry Building Units: Overview screen appears. The overview displays all the existing building units and their assignment to other buildingunits 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.

NoteYou 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 thenchoose ( Details ). To return to the overview screen, choose ( Back ). When you save the master data on the detail screen, you not only save themaster data of the building unit but also all of the changes you made on the collective entry overview screen.

3. Then save the data.You return to the SAP Easy Access screen.

1.2.1.4.2.13 Flagging Building Units for Deletion

PrerequisitesYou cannot delete building units directly. Deleting building units without first checking whether dependent objects exist would constitute a serious threat to dataconsistency 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 thebuilding 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 thebuilding units flagged for deletion. Note that there are no restrictions on using building units flagged for deletion.

Procedure1. 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 identificatio

sap patient management

Documents