Sap Is H Rel471 Word

Release
Notes
SAP Patient Management
Release 4.71
February 2003
Release Notes SAP Patient Management 4.71
Version
Release Notes SAP Patient Management Release 4.71
Version 1 (EN) for SAP Service Marketplace, February 2003
Copyright
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.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server
are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX,
S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS,
AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix
Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other
countries.
ORACLE is a registered trademark of ORACLE Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open
Group.
Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, MultiWin and other Citrix product names referenced herein are
trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C,
World Wide Web Consortium, Massachusetts Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under
license for technology invented and implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow,
WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP,
mySAP.com, 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 in several other countries all over the world. MarketSet and Enterprise Buyer are
jointly owned trademarks of SAP Markets and Commerce One. All other product and
service names mentioned are the trademarks of their respective owners.
Legend
Icon
Meaning
Caution
Example
Note
Contents
SAP Patient Management Release 4.71
General Information
Important Activities for Release 4.71

Quick Reference
mySAP Customer Relationship Management for Healthcare 4.0 (New)
Basic Data
9
9
11
13
AT: Technical Number Ranges (Changed)
13
Business Partners
DE: Program for IP Master File Comparison Deleted
Notification of End of Maintenance of "Maintain/Display Insurance Provider Group"
Notification of End of Maintenance of "Create RP Employee"
13
13
13
13
Clinical Work Station

Clinical Work Station (Enhanced)
Modify Columns in the Clinical Work Station (New)
14
14
15
Patient Management
16
Reactivate Preregistration when Canceling Admission/Visit (New)

Detach Preregistration from Case (New)
Notification of End of Maintenance of Old Inpat./Outpat. Admission
Print Appointments in Preregistration (New)
Case List: Add User Field for Cases using BAdI (New)
Case List: Add User Field for Movements Using BAdI (New)
16
17
17
18
19
20
Patient Master Data

CA: Address Data (Changed)
Business Add-Ins for EnjoySAP Admission (New)
21
21
21
Inpatient Case
Indicator for Invalid Movement Types After Discharge (New)
EnjoySAP Admission (Changed)
Transfers: Room and Bed Proposal (New)
22
22
22
23
Outpatient Case
24
General Case Processing

Business Add-In for Case Type Change (New)
Business Application Programming Interfaces for Patient and Case (New)
Screen Modification (Enhanced)
AT: Check at Case Type Change in EnjoySAP Admission (New)
24
24
25
25
26
Care Unit Management

Notification of End of Maintenance of Care Unit and Visit Overviews
26
26
Outpatient Clinic Management

Business Add-In for the Appointment Overview (New)
User Parameters for Error Handling in Appointment Processing (New)
Open Time Slot Search in Visit Scheduling (Enhanced)
Planning Objects and Their Time Slots (Enhanced)
26
26
27
27
27
Medical/Nursing Documentation
29
Basic Medical/Nursing Documentation

Coding Analyses Work Station (Enhanced)
DE: "Length of Stay" Indicator (Changed)
DE: Interface for DRG Coding and Grouping System (Enhanced)
BAPI for Changing, Creating and Canceling Diagnoses (New)
DRG Data Maintenance Business Add-In (New)
Notification of End of Maintenance of Tables NLOP and NICP2
Authorizations in DRG Work Station (Changed)
Procedure Entry (New/Changed)
Patient Accounting
29
29
30
30
30
31
31
32
32
33
AT, CH: Fee Processing (Changed)

DE: DRG Billing According to Option Model 2003 (New)
DE: Billing of Flat Rates per Case According to KFPV (New)
DE: Price Determination for DRG Services
DE: Service Rule R12Generation of Quality Assurance Surcharge (New)
DE: Settings for Billing of DRG Services
33
33
33
33
33
33
Services
Service Rule R2 with Service Action (Changed)
Service Rule R13: Long-Term Accommodation Services (New)
SAPscript Long Texts for Case-Related Services (Changed)
Service Actions with Long Text Support (New)
AT: Status Check in Service Entry
AT: Service Rule A15 Max. Values for Groups w/o Ins. Relationships
AT: Service Rules (Changed)
34
34
34
36
36
37
37
37
Insurance Verification
CH: Changes in Insurance Verification (Changed)
37
37
Billing
CH: Invoicing (Changed)
DE: Interim Billing for DRG Services (Changed)
Collective Invoice for Self-Payers (New)
Printing of Dunning Notices with Smart Forms (Changed)
DE: Determination of Share of Costs for Outpatient WC Billing (Changed)
"Charge Factor Value" Indicator in IMG Activity "Determine Catalog Columns" (Changed)
38
38
38
38
38
39
39
Integration with Materials Management
40
Reports for Material List and Material Consumption (Enhanced)
40
Master Data
Closet (New)
Extraction Healthcare-Specific Attributes of Material Master (New)
40
40
41
Material Requisition
Procurement Type and Document Type Determination (New)
Organizational Unit-Related Material Requisition (Enhanced)
41
41
42
Information System
43
Business Information Warehouse Interface
43
Communication
44
Communication with Systems Outside the Hospital

EDI Worklist (New)
EDI File Status Management for EDI Inbound Processing (Changed)
DE: Supplement to 301 Data Transfer (Changed)
DE: 301 Procedure for DRG Billing (New)
EDI: Recreate Outbound Messages (New)
Tools
44
44
44
45
45
45
46
DE: Output DRG Surcharges and Discounts on Invoice Form (New)
46
SAP Patient Management Release 4.71

These release notes provide an overview of the new features offered by SAP Patient
Management Release 4.71.
Please note that this release requires SAP R/3 Enterprise Release 4.70/mySAP
Technology Components Release 6.20. The previous SAP Patient Management
Release 4.63B was based on the standard SAP Release 4.6C.
If you have skipped one or more releases, it is essential that you read the release notes
for the release(s) in question both those for the SAP Patient Management Releases
and those for the releases pertaining to the mySAP Technology Components. You'll
find the SAP Patient Management Release Note on the SAP Service Marketplace
(http://service.sap.com) under the alias healthcare-releasenotes. You'll find the
release notes for the mySAP Technology Components on the SAP Service Marketplace
under the alias /releasenotes; Choose mySAP Technology Components in the
navigation area there.
For information about how to generate the release note structure, refer to the SAP
note 195299. This release note also contains details on how to generate countryspecific release note structures.
This new release contains new functionality and improvements. Some of these may
require you to modify your system configuration after upgrading. Consequently, you
are asked to check, and, if necessary, perform the Customizing activities mentioned
in the following documentation. This applies, in particular, to the activities listed in the
section entitled Overview of the Most Important Activities for Release 4.71. Such
activities are usually necessary if you wish to use new or enhanced functions.
In many chapters of the online release notes, you can directly access the relevant
section of the IS-H Implementation Guide. In Customizing, you can also generate a
view containing all upgrade Customizing and/or delta Customizing activities. When
doing this, please make the following specifications:
Specify IS-H as the Add-On ID.
You have to respect a particular notation when entering the values for From
Release and To Release. Examples of the naming convention from earlier IS-H
Releases are 4.01A/0, 402A, 403A, 461A, 462, 463 and 463B. The name of
current release is 471. For comprehensive information on generating views,
please refer to the online documentation which you accessif the latest
documentation CD has been installedby choosing Help SAP Library. Then
choose SAP Library mySAP Technology Components SAP Web
Application Server Customizing (BC-CUS) Customizing (BC-CUS).
A number of release notes relate exclusively to developments for particular country

versions. Such release notes are identified by country keys in their short text. For
example:
AT: Release note for the country version Austria
CA: Release note for the country version Canada
CH: Release note for the country version Switzerland
DE: Release note for the country version Germany
SG: Release note for the country version Singapore
The functions described in country-specific release notes have not been released for
other country versions.
If various changes described in a release note apply to particular country versions,

this is indicated by a reference to the country versions, or by the country key.
The next SAP Patient Management Release is scheduled for 2004. Changes that
result from legal requirements before this date will be shipped in Add-On Support
Packages.
mySAP Healthcare Development
General Information
Important Activities for Release 4.71
Use
DE: DRG Billing

This information is not available in English.
Changes to authorizations in the transactions NPDRG1 and NPDRG2

In previous releases, the system checked for the value NPDRG instead of the
transaction code (NPDRG1 or NPDRG2) for the transactions NPDRG1 und
NPDRG2 in the authorization object N_EINR_TCO. Please take this into account
in your authorization objects.
Notification of End of Maintenance of Functions

Maintenance will end for a number of functions, or old functions will be replaced
by new ones in the next release or in the next release but one. You'll find
information about this in the following release notes:
Notification of End of Maintenance of Old Inpat./Outpat. Admission (see p. 17)
Notification of End of Maintenance of Care Unit and Visit Overviews (see p. 26)
Notification of End of Maintenance of "Maintain/Display Insurance Provider
Group" (see p. 13)
Notification of End of Maintenance of "Create RP Employee" (see p. 13)
Notification of End of Maintenance of Tables NLOP and NICP2 (see p. 31)
Quick Reference
EnjoySAP Admission
As of this release, the new, clearly laid out EnjoySAP Admission (transaction code
NV2000) provides you with all of the functions from the old patient admission
transactions.
To make the use of the EnjoySAP admission more flexible, you can now define your
own presettings for the fields in the various subscreens or your own checks on the
admission data using Business Add-Ins (BAdIs).
As concerns input control for the various fields, as of this release you can also
differentiate admission variants in screen modification. This means that you can
define input types for fields in relation to each admission variant.
As of this release, it is possible for you to switch to another variant from within the
variant you are currently using. All variants now give you direct access to the integral
service entry procedure.
It is now also possible to change the case type from inpatient to outpatient and vice
versa. By implementing a BAdI, you can run your own checks when changing the
case type.
SAP will cease maintenance of the old inpatient and outpatient admission as of the
next release but one.

To make working with the Clinical Work Station faster, you can now interface with it
using function keys. You can define which function keys the system should use.
As of this release, you can stipulate in the selection variants whether the user must
make an entry in the individual fields, or whether the fields should be suppressed or
protected.
Additional fields, such as DRG key figures for a case, are now available to you in the
field catalogs for the view types Occupancy, Arrivals and Departures.
SAP will cease maintenance of the visit and care unit overviews as of the next
release but one. These will be replaced by the view types that are already available
to you in the Clinical Work Station.
To simplify the free time slot search in visit scheduling, you can now save default
values for search variants in relation to the user.
For time slots defined for rooms, you can now stipulate an attending physician
(person) in the planning object master data or in the rooms' day program.
Patient Accounting
To reduce the administrative work load and reduce the number of individual bank
transfers, as of this release you can also create collective invoices for self-payers.
The Smart Form interface and checks for form printing have been enhanced
accordingly.
Materials Management and Logistics
As of this release, you can define closets and incorporate these in the decentralized
material requisition function. This means that the system will determine the order
quantity. The address of the storage location is noted on the goods issue/receipt slip
to enable the closets to be replenished quickly.
You can now flexibly control whether a decentralized material requisition is created
as a reservation or purchase requisition in relation to the institution, the requesting
organizational unit, the material and the point of issue.
SAP Business Information Warehouse
As of this release, you can also transfer healthcare-specific attributes for the material
master into the Business Information Warehouse (BW). This means that you also get
information such as ATC code and active ingredient in the BW material analyses.
Communication
A uniform interface is now available to you for handling EDI messages. A new EDI
Worklist replaces the previous inbound and outbound worklists. A new function
makes the reimport of individual inbound messages simpler.
A new program makes the assembling and resending of existing outbound EDI
messages easier than ever before.
Customer Relationship Management (CRM)
Customer Relationship Management lets you create a global view on persons and
organizations that have a business relationship with your hospital. As of CRM
Release 4.0, SAP provides healthcare-specific business partner roles, including
patient, physician and health insurance provider. CRM 4.0 also provides predefined
business partner relationships, such as between patient and health insurance
provider or patient and attending physician.
10
Special Features in Country Version Germany

Special Features in Country Version Switzerland
Special Features in Country Version Austria
mySAP Customer Relationship Management for Healthcare 4.0 (New)

Use mySAP Customer Relationship Management (CRM) for Healthcare 4.0 lets you
create a global view on your customers. By customers of a hospital, we mean all
persons and organizations that have a business relationship with the hospital.
Examples of such are:
Patients
General practitioners
Health insurance providers
Suppliers
Hospital employees
On the basis of this knowledge about your customers, you can offer customeroriented services, such as:
Interaction Center support
Efficient appointment management
Invitations for preventive and aftercare medical examinations
Internet Self-Services
Target group-specific advertising
Support of mobile outpatient nursing services.
The described functions are based on mySAP CRM software. As of Release 4.0, you
are able to maintain healthcare-specific business partner roles and healthcarespecific business partner relationships in CRM Business Partner Management.
Consequently, you can now also use CRM functions for the specific needs of a
hospital. This equally creates the basis for setting up data exchange involving
business partners and business partner relationships with connected systems.
In addition to the business partner roles contained in the CRM 4.0 standard
shipment, the following hospital-specific business partner roles with corresponding
attributes for data management are available to you:
Patient
Physician
Health insurance provider
HMO member
(HMO = Health Maintenance Organization, usually used only in USA. A
healthcare providing organization that provides and finances the medical and
hospital care of its members).
Doctor's practice
Hospital
11
In addition to the business partner relationships contained in the CRM 4.0 standard
shipment, the following hospital-specific business partner relationships with
corresponding attributes for data management are available to you:
Business partner relationship between patient and health insurance provider
Business partner relationship between patient and attending physician
Business partner relationship between patient and family physician
Business partner relationship between patient and employer
Business partner relationship between physician and doctor's practice

(workplace)
Business partner relationship between physician and hospital (workplace)
The business partner relationship "Contact Person Relatationship" ("Is Contact

Person For" / "Has Contact Person") provided with the standard CRM delivery has
been enhanced with attributes for maintaining responsibilties. This relationship lets
you maintain contact persons for a health insurance provider and their areas of
responsibility.
See also
You'll find comprehensive information about mySAP CRM in the SAP Service
Marketplace under http://service.sap.com/crm.
You'll find the documentation for mySAP CRM in the Help Portal (help.sap.com)
under mySAP.com Cross-Industry Solutions mySAP Customer Relationship
Mgmt.
12
Basic Data
General Information
AT: Technical Number Ranges (Changed)

Use
This release note is relevant for the country version Austria only. Documentation is
not available in English.
Business Partners
DE: Program for IP Master File Comparison Deleted
Use
This release note is relevant for the country version Germany only. Documentation is
Notification of End of Maintenance of "Maintain/Display Insurance Provider

Group"
Use
Please note that with the next release of SAP Patient Management (scheduled for
2004), SAP will end maintenance for the maintenance and display of insurance
provider groups. This concerns the following transaction codes
NG20 Display Insurance Provider Group
NG21 Maintain Insurance Provider Group
Notification of End of Maintenance of "Create RP Employee"

Use
In previous releases, the transaction NG30 Create Employee/Physician let you
create employees/physicians in a specially reserved number range (RP). The
indicator IS-H: Personal Data Originates in HR System (technical name NPERRPPKZ) was set for these persons in the table Persons (technical name NPER).
2004), SAP will end maintenance for the entry of RP employees via this separate
transaction.
Note that the transaction NG04 (Create Employees/Physicians) will continue to exist.
With the next release of SAP Patient Management (scheduled for 2004) it will be
possible also to create persons in the specially reserved number range using the
transaction NG04.
13

Clinical Work Station (Enhanced)
Use
Use of Function Keys
You can now also use function keys, and not just the mouse, to operate the clinical
work station. You define which function keys can be used for each view by defining
the function variant as an attribute of a function.
The keys Ctrl-F1 to Ctrl-F12 are available in each view.
Selection Variant Indicators
When defining selection variants you can set the following indicators for each
selection field:
Required entry field
Hide field
Protect field
The system will also take these selection variant attributes into account in the
selection dialog boxes of the individual view types.
The Hide Until Field indicator and Deactivate GPA (Preset Using Set/Get
Parameter) indicator are not taken into account in the current release.
Copying Views
If you copy views, the name of the new work environment or the new view will be
copied into the description of the variant, to simplify maintenance. This means you
can differentiate between the new variants and the original variants.
Field Catalog Enhancement
In the field catalogs for the Occupancy, Arrivals and Departures view types, the
following additional fields are now available:
VIP indicator
Admission date
Number of days since admission
Indicator, that a planned discharge exists for a case
Date of last surgery
Number of days since last surgery
DRG indicator for case

DRG service
Length of stay for case in days
Maximum, average and minimum length of stay in main/external physician
department in days
Maximum, average and minimum number of days that length of stay may be
exceeded by
14
Indicator, that maximum/average/minimum length of stay is exceeded

Number of days until maximum length of stay is reached
Cost weight for DRGs maximum/average/minimum length of stay
The DRG key figures for a case are also available in the field catalog of the Coding
Analyses view type.
The DRG key figures are only available in the field catalogs of the vie w types, if
DRG billing is performed according to option model 2003. You can find more
information on this in the release note DE: DRG Billing According to Option Model
2003 (New) (not available in English).
Modify Columns in the Clinical Work Station (New)

Use
This release makes available to you the Business Add-In (BAdI) IS-H: Modify
Columns in Clinical Work Station (ISH_WP_VW123_COLUMN). The BAdI lets you
add columns to the occupancy, arrivals and departures views in the Clinical Work
Station, or change the contents of existing columns.
The BAdI replaces the customer exit SAPLN1WP. For new enhancements to the
Clinical Work Station, you should use Business Add-Ins and not SMOD exits. You
should migrate existing SMOD implementations to BAdIs wherever possible.
See also
For further information, refer to the documentation for the BAdI IS-H: Modify
Columns in Clinical Work Station, the interface documentation and the method
documentation for the BAdI.
15
Patient Management
General Information
Reactivate Preregistration when Canceling Admission/Visit (New)

Use
You can use the preregistration to enter patients for a treatment, or an inpatient
admission which may be necessary, into the system. As long as you do not schedule
an appointment for the treatment or the inpatient admission, the preregistration
represents an entry in the waiting list.
The patient will only appear in the Outpatient Clinic/Service Facility view of a specific
organizational unit (OU) once you have scheduled an appointment for him there.
IS-H*MED: For IS-H*MED this process also applies to surgeries (ORs). You can use
the preregistration to enter patients for a surgery as well as for the corresponding
inpatient admission, which may be necessary for this, into the system. As long as
you have not planned an appointment for the inpatient admission, the system will
display the preregistration as an entry in the waiting list. Once you have assigned an
appointment, the patient will appear in the OR plan of the OU for which the surgery
appointment is scheduled. When the patient arrives for his surgery, you create a visit
for the scheduled surgery appointment.
When the patient arrives for his treatment, you create a visit for the scheduled
treatment appointment. In the same way, the preregistration will only appear in the
Arrivals view of the care unit, for which the inpatient admission appointment is
scheduled, when you create an appointment for the inpatient admission. There are
several ways to enter this:
New Admission
You select the appointment in the appointment overview of the initial screen and
then create the visit.
Surgery (IS-H*MED only)

You enter the first time stamp for a surgery thereby setting the surgery to
"started"
Outpatient Clinic, Service Facility (IS-H*MED only)

You select the appointment in the Outpatient Clinic/Service Facility view and
then execute the Admission with Appointment Context or Register Patient
function.
Outpatient Clinic, Service Facility

You create a visit for the appointment.
When the patient arrives for his inpatient admission appointment, you create an
admission for the scheduled appointment. You do this in the new admission by
selecting the inpatient admission appointment and then creating the admission.
With all these possibilities, the preregistration is then linked to the case which you
selected in the admission. The appointment is linked to the visit or admission
movement. From this point onwards, the system assumes that appointment was
kept.
16
If you accidentally selected the wrong appointment, you should cancel the created
visit or admission. As of this release, the system will no longer automatically cancel
the preregistration and the appointment. You can now recreate the original status of
the preregistration from before the creation of the visit or admission.
This can be important if you require reporting or the evaluation of waiting list entries.
You will only receive evaluations, for example, over the period of time between the
preregistration and the completion of the surgery/treatment, if a patient is
represented by the same waiting list entry during the entire planning phase.
Process from a User's Point of View:
IS-H*MED only: When you cancel a visit in IS-H*MED, the system will produce a list
of all objects which are connected to this object. This includes visit appointments,
services, and the preregistration. If the appointment and preregistration are not
selected, they will remain active once the visit has been canceled.
The following also applies to SAP Patient Management (IS-H):
If the visits or the inpatient admission to be canceled are the only link to the case, the
preregistration will become caseless once the visit or admission has been canceled.
This means that you can assign the preregistration to a different case at a later date.
See also
You should also refer to the release note Detach Preregistration from Case (New)
(see p. 17).
Detach Preregistration from Case (New)

Use
Under some circumstances, you may need to place a preregistered patient, who has
already been admitted, back on the waiting list. One reason for this could be that the
surgery for which the patient was admitted, cannot be performed during the current
inpatient stay for medical reasons.
As of this release, the preregistration offers the Detach Preregistration from Case
function for such circumstances.
You can only execute this function, if the preregistration is already connected to a
case.
The Detach Preregistration from Case function separates the preregistration, the
preregistered services, and the scheduled appointments from the case. The inpatient
admission movement for the surgery or treatment will remain active even after you
have executed the Detach Preregistration from Case function.
See also
You should also refer to the release note Reactivate Preregistration when Canceling
Visit (New) (see p. 16).
Notification of End of Maintenance of Old Inpat./Outpat. Admission

Use
Please note that with the next release of SAP Patient Management but one (planned
for 2005), SAP will end maintenance for the old inpatient admission and the old
outpatient admission transactions. This concerns the following transaction codes:
17
NV01: Create Inpatient Admission
NV02: Change Inpatient Admission
NV03: Display Inpatient Admission
NP11: Create Inpatient Admission Data
NP12: Change Inpatient Admission Data
NP13: Display Inpatient Admission Data
NV04: Create Inpatient Quick Admission
NV05: Change Inpatient Quick Admission
NV06: Display Inpatient Quick Admission
NV07: Create Inpatient Emergency Admission
NV08: Change Inpatient Emergency Admission
NV09: Display Inpatient Emergency Admission
NV41: Create Outpatient Admission
NV42: Change Outpatient Admission
NV43: Display Outpatient Admission
NV44: Create Outpatient Quick Admission
NV45: Change Outpatient Quick Admission
NV46: Display Outpatient Quick Admission
NV47: Create Outpatient Emergency Admission
NV48: Change Outpatient Emergency Admission
NV49: Display Outpatient Emergency Admission
NP40: Create Outpatient Visit Data and Outpatient Case
NP41: Create Outpatient Visit Data and Outpatient Case
NP42: Change Outpatient Visit Data
NP43: Display Outpatient Visit Data
As a consequence, the transaction NV2000 will replace the previous functions for
inpatient and outpatient admission. SAP recommends that you use the transaction
NV2000 instead of the above mentioned old functions as soon as possible.
Outlook: As of the next release of SAP Patient Management, the functional scope of
the transaction NV2000, with which you can only execute the EnjoySAP Admission
in this release, will be enhanced by the functions Create, Change and Display
Surgeries, Transfers, Discharges, Absences and Patient Master Data.
Print Appointments in Preregistration (New)

Use
When displaying and editing preregistrations, you can print all of the appointments
planned in the preregistration on a form.
For this purpose, the following pushbuttons are available to you in the
preregistration:
Standard Form
If you click on the Standard Form pushbutton, the system prints the
appointments on the preset standard form.
18
Choose Form...
If you click on the Choose Form... pushbutton, you can select the desired form
from the list returned by the system.
Both functions let you print the following appointments on a form:
Admission appointment
Surgery/treatment appointment
Any other appointments planned in the treatment contexts of the preregistration.
The system automatically saves the preregistration and all planned appointments
when you execute the print function.
Effects on Customizing
To be able to print appointments on a form, you must have defined one or more
forms for the events APPINS and APPUPD in Work Organizer Management.
For further information about this, refer to the IS-H Implementation Guide under SAP
Healthcare Industry-Specific Components for Hospitals Tools Work
Organizer Management.
Case List: Add User Field for Cases using BAdI (New)
Use
The Business Add-In (BAdI) IS-H: Add Case Level User Field to Case List
(ISH_CASELIST_CASEFLD) lets you add your own field to each case on the case
list. You can also use this BAdI to add a title for this field in the case list heading. The
field and title of the field are both 30 characters in length.
To add the case field, you have to implement your field in the BAdI method
ISH_CASELIST_CASEFLD~GET_CASE_FIELD. The system calls this method for
each case on the case list. The system passes patient, case and movement data to
the BAdI method. This makes it possible to derive the case field title based on data
of the patient, the case itself, and all movements of the case list.
You can use the following data in the BAdI method
ISH_CASELIST_CASEFLD~GET_CASE_FIELD:
Patient data
Case data
Movements of the case
To add the title for your field to the case list heading, you have to implement the BAdI
method ISH_CASELIST_CASEFLD~GET_CASE_FIELD_TITLE. The system passes
the data for the patient, all cases in the list, and all movements in the case list to the
BAdI method. This makes it possible to derive the case field title based on the data
of the patient and all of the cases and movements displayed on the case list.
ISH_CASELIST_CASEFLD~GET_CASE_FIELD_TITLE:
Patient data
Case data for all cases displayed on the case list
Movement data for all cases displayed on the case list.
See also
For more information, refer to:
19
The documentation for the BAdI
The documentation for the BAdI methods

ISH_CASELIST_C ASEFLD~GET_CASE_FIELD_TITEL
ISH_CASELIST_C ASEFLD~GET_CASE_FIELD
The documentation for the BAdI interface

IF_EX_ISH_CASELIST_CASEFLD
Case List: Add User Field for Movements Using BAdI (New)
Use
The Business Add-In (BAdI) IS-H: Add Movement User Field to Case List
(ISH_CASELIST_MVMTFLD) lets you add your own field to each movement on the
case list. You can also use this BAdI to add a title for this field in the case list
heading. The field and title of the field are both 30 characters in length.
To add the movement field to the case list, you have to implement your field in the
BAdI method ISH_CASELIST_MVMTFLD~GET_MVMT_FIELD. The system calls
this method for each movement in the case list. The system passes patient, case,
and movement data to the BAdI method. This makes it possible to derive the field for
each movement on the case list based on the data of the patient, the case itself, and
the movements of the case.
ISH_CASELIST_MVMTFLD~GET_MVMT_FIELD:
Patient data
Case data
Movement data (for each movement on the case list as the system calls the BAdI
once for each movement in the case)
Movement data for all movements of the case
To add the title for your field to the case list heading, you have to implement the BAdI
method ISH_CASELIST_CASEFLD~GET_CASE_FIELD_TITLE. The system passes
the data for the patient, all cases, and all movements in the case list to the BAdI
method. This makes it possible to derive the movement field title based on the data
of the patient and all of the cases and movements displayed on the case list.
ISH_CASELIST_MVMTFLD~GET_MVMT_FIELD_TITLE:
Patient data
Case data for all cases displayed on the case list
Movement data for all movements displayed on the case list
See also
For more information, refer to
The documentation for the BAdI
The documentation for the BAdI methods

ISH_CASELIST_M VMTFLD~GET_MVMT_FIELD_TITEL
ISH_CASELIST_M VMTFLD~GET_MVMT_FIELD
The documentation for the BAdI interface

IF_EX_ISH_CASELIST_MVMTFLD
20
Patient Master Data

CA: Address Data (Changed)
Use
For SAP Patient Management Release 4.71, the Region field has been added to the
following data objects in the country version Canada:
Patient's employer
Next of kin/associated party
Main person insured
Employer of main person insured.
You can suppress this field from the screen using screen modification. For
information about this, refer to the section entitled Maintain Screen Modification in
the IS-H Implementation Guide.
Business Add-Ins for EnjoySAP Admission (New)

Use
In the EnjoySAP Admission (transaction code NV2000), you can now use Business
Add-Ins (BAdIs) to preset or check admission data to meet your individual
requirements.
For this purpose, the following three BAdIs are provided in the IS-H Implementation
Guide under SAP Healthcare Industry-Specific Components for Hospitals
Patient Management Patients Business Add-Ins for Patient Admission:
ISH_NV2000_PBO: BAdI: EnjoySAP AdmissionPreset All Subscreens

This BAdI lets you preset the fields of the EnjoySAP Admission. The system calls
the BAdI at the event PBO, in other words, when the EnjoySAP Admission has
just been called.
The system calls the BAdI at least once for each subscreen. You can decide
whether the BAdI is called only the first time the EnjoySAP Admission
transaction is accessed, or whether it runs each time a screen is recompiled.
You can tailor both variants to satisfy your own individual requirements. Note that
the system does not check whether the data has been preset correctly. You
cannot, however, save incorrect data later.
For further information, refer to the
interface documentation
method documentation
ISH_NV2000_PAI: BAdI: EnjoySAP AdmissionCheck Data of Individual

Subscreens
This BAdI lets you check the fields of a subscreen in the EnjoySAP Admission.
The system calls the BAdI at the event PAI, in other words, after the individual
subscreen of the EnjoySAP Admission have been processed. You can decide
whether the BAdI only returns messages, or whether the subsequent process
flow should be modified. By modifying the subsequent process flow, you can, for
example, preset data on the basis of user input. You can do this using the above
mentioned BAdI ISH_NV2000_PBO (Preset All Subscreens).
21
ISH_NV2000_PAI_COMPL: BAdI: EnjoySAP AdmissionCheck Complete Data

This BAdI lets you check the fields of all subscreens in the EnjoySAP admission
and the associated technical fields. The system calls the BAdI at the event PAI,
in other words, after the EnjoySAP Admission processing. You can decide
whether the BAdI only returns messages, or whether the subsequent process
flow should be modified. By modifying the subsequent processflow, you can, for
example, preset data on the basis of user input. You can do this using the above
mentioned BAdI ISH_NV2000_PBO (Preset All Subscreens).
For presetting and checking the individual screens of the BAdIs BAdI: Enjoy
AdmissionPreset All Subscreens and BAdI: Enjoy AdmissionCheck Data of
Individual Subscreens, a sample implementation is provided as a template for your
own implementations.
See also
For further information about the detailed use of the BAdIs, refer to the
documentation for the methods and interfaces of the respective BAdIs.
Inpatient Case
Indicator for Invalid Movement Types After Discharge (New)

Use
After you have discharged a patient, not all movement types are valid for an
outpatient visit. You can therefore now set an indicator for each movement type,
which prevents the use of the movement type when an outpatient visit is created
after the patient has been discharged.
The system checks if a discharge exists for the selected case and whether an
outpatient visit should be created. In this case, the value help you call to select the
movement type will only contain the movement types for which this indicator was not
set.
The movement type for which this indicator is set remains permanently invalid for the
given case after discharge.
You can set the indicator for a movement type in the following IMG activity in the ISH Implementation Guide: SAP Healthcare Industry-Specific Components for
Hospitals Patient Management Movements Define Movement Types.

Use
The following functions are now available to you in EnjoySAP Admission (transaction
code NV2000):
22
Case Type Change

The Case Type Change function lets you change the case type from inpatient to
outpatient and vice versa.
Other Variant
The Other Variant... function lets you choose another variant for processing the
current movement on the data screen.
Service Entry
Besides service forms, the entire service entry procedure is now available to you
in EnjoySAP Admission. You access this procedure, irrespective of the set
variant, by clicking the Services pushbutton, or by choosing Extras More
Extras Services.
Transfers: Room and Bed Proposal (New)

Use
The user parameter NOV lets you stipulate for a given user whether the system is to
propose the values in the input fields for the room and bed assignment when this
user creates a transfer. The following settings are possible:
Parameter Value
Meaning
The system does not transfer proposal into the room and
bed assignment data of the transfer.
'_'
The system either proposes the current room and bed

assignment of the case or the room and bed assignment of
a movement for the room and bed assignment of the
transfer.
In addition to this user-related parameter, this release give you the possibility to
control the proposed values in relation to movement type. You control this using an
indicator in the Room/Bed Prop. field in the IMG activity Define Movement Types (the
field is only active with movement category 3 (transfer).
The following dependencies exist between the user parameter and this indicator:
NOV
Ind. in Transfer Type
Change*
Behavior
blank
set
yes
no proposal
blank
set
no
proposal**
blank
not set
yes
not cleared
blank
not set
no
cleared
'X'
set
--
no proposal, nothing
cleared
'X'
not set
--
no proposal, nothing
cleared
*: department, nursing OU, room or bed changed

**: if new transfer: values proposed from previous movement; if existing transfer:
proposed values the transfer had prior to the user accessing the transfer screen
23
The proposed values are based on the transfer type in the transactions Create
Transfer (NV11) and Change Transfer (NV12) and on the settings you made in the
IMG activity Define Movement Types.
The proposed values relate to the following fields in the transactions mentioned
above:
Room
Room Identifier
Bed
Bed Identifier
Nursing organizational unit (OU) and the four hierarchy fields for the nursing OU.
In the IMG activity Define Movement Types, stipulate for which transfer types the
room and bed assignment should be active.
For more information about this, see Patient Management Movements Define
Movement Types in the IS-H Implementation Guide.
Outpatient Case
see p. 22.
General Case Processing
Business Add-In for Case Type Change (New)

Use
In the EnjoySAP Admission (transaction code NV2000), you can now use the
Business Add-In (BAdI) ISH_NV2000_CASTYPCHG (BAdI: EnjoySAP Admission
Check Data at Case Type Change) to implement your own checks on patient data
when the case type is changed.
You access this BAdI in the IS-H Implementation Guide by choosing SAP Healthcare
Industry-Specific Components for Hospitals Patient Management Cases.
This BAdI lets you check all case and movement data for the patient and the
associated technical fields. The system calls the BAdI when you click on the Case
Type Change pushbutton in the initial screen of the EnjoySAP Admission following
the system-internal checks. The BAdI returns messages in a table. By issuing
messages of the type "A" or "E", you can prevent the case type from being changed.
See also
For further information about the detailed use of the BAdI, refer to the:
24
Business Application Programming Interfaces for Patient and Case (New)

Use
In the Business Object Repository (BOR), you can now access the system via four
new Business Application Programming Interfaces (BAPIs). These BAPIs provide
you with lists and details pertaining to cases and movements. The following BAPIs
are available to you:
Patient.GetCaseList
For a specified institution and patient number, this BAPI returns a list of all the
cases for the patient in question. The canceled cases can also be displayed by
setting the appropriate indicator. The admitting and discharging organizational
units together with the date and time of admission and discharge have been
added to the case data.
Patientcase.GetPatCaseList
This BAPI provides the same functionality as the above mentioned BAPI for the
patient. However, the case number is also passed to the interface as a selection
option. The patient is determined in relation to this case number, and the
corresponding cases are output in a list.
Patientcase.GetDetail
For a specified case number and institution, this BAPI returns all of the data for
the given case along with the relevant text fields.
Patientcase.GetMovementList
For a specified institution and case number, this BAPI returns a list of all of the
movements for the case in question.
Furthermore, all BAPIs return tables in which any problems encountered are listed as
messages.
See also
For further information about authorizations and functionality, refer to the
documentation for the BAPIs.
Screen Modification (Enhanced)

Use
In previous releases, screen modification let you maintain the type of input (for
example, required entry field) for various fields on a screen. In this connection, it is
now possible to make a distinction according to variants for the EnjoySAP
Admission. You can thus make a separate definition of the input type for each variant
created in the system. For example, you can distinguish an emergency admission
variant, for which there are no required entry fields, from a standard admission
variant, in which you define the patient's last name and birthdate as required entry
fields.
Effects on Existing Data
It is not necessary to modify existing data. The assumption will continue to be that
entries without a variant specification are valid for all variants.
25
In the IS-H Implementation Guide, you access the maintenance of the input types by
choosing SAP Healthcare Industry-Specific Components for Hospitals Basic
Settings Screen Control Maintain Screen Modification. Two new columns have
been added to the table:
Work Environment Type (W.Env.Type)

This field describes the type of variant selected. This type is defined by the
context in which the variant was created. At present, only the work environment
type Admission Work Station (AD1) supports the maintenance of variants in
screen modification. You can call a value help for this field.
Work Environment (Work Envir.)

In this field, you determine the variant for which you wish to maintain screen
modification. You can call a value help for this field. If you don't make an explicit
entry in this field, the system automatically places an asterisk ("*") in it.
AT: Check at Case Type Change in EnjoySAP Admission (New)

Use
Care Unit Management

Use
2004), SAP will end maintenance for the Care Unit Overview (transaction code
NR11) and for the Visit Overview (transaction code NR14). These will be replaced
by the Clinical Work Station (transaction code NWP1), available to you since
Release 4.63.
Business Add-In for the Appointment Overview (New)

Use
The Business Add-In (BAdI) ISH_TIMESLOT_TXT (BAdI: Change Appointment
(Time Slot) Text in Appt Overview) lets you custom tailor a time slot or a visit
appointment in the daily schedule of a planning object to satisfy your particular
requirements.
26
This BAdI replaces the SAP enhancement NR160003; it lets you modify the entry in
the daily schedule and also supply a long text that the system outputs as the quick
info for the entry.
For further information, see under SAP Healthcare Industry-Specific Components
for Hospitals Patient Management Scheduling Scheduling of Visit
Appointments BAdI: Change Appointment (or Time Slot) Text in Appointment
Overview in the IS-H Implementation Guide.
User Parameters for Error Handling in Appointment Processing (New)

Use
InVisit Scheduling, the system displays error messages in the Maintain Appointment
dialog box when you maintain appointment data and in a modeless dialog box when
you are searching for an open time slot in the available time slot list. You can now
specify the position of this dialog box by means of the following user parameters.
You make the parameter specifications in pixels:
NAPP_ERR_POPUP_TOP
Appointment dialog: Upper position of the error dialog box
NAPP_ERR_POPUP_LEFT
Appointment dialog: Left position of the error dialog box
NATSL_ERR_POPUP_TOP
Appointment list: Upper position of the error dialog box
NATSL_ERR_POPUP_LEFT
Appointment list: Left position of the error dialog box
Open Time Slot Search in Visit Scheduling (Enhanced)

Use
For the open time slot search in visit scheduling, you can define frequently used
search criteria as search variants that can be reused.
The new function Settings Search Variant Use as Default Values lets you
define one of your search variants as the user-specific default setting for the
Standard Search and for the Advanced Search. When you call the Standard Search
or the Advanced Search, the system presets the values of this search variant.
Planning Objects and Their Time Slots (Enhanced)

Use
When defining planning objects and their time slots for inition in the daily schedule of
the planning object. This lets you override the person assignment in the master data.
If a person is stored for a planning object of the type "room", the system uses this
person as the attending physician when you create an appointment.
27
Moreover, as concerns the definition of planning objects and their time slots, the list
of planning objects for a treatment organizational unit is output using the SAP List
Viewer (ALV). You can now maintain the planning object data and the time slot data
in this list by means of hotspot functions.

see p. 26.
28
Medical/Nursing Documentation
Basic Medical/Nursing Documentation
Coding Analyses Work Station (Enhanced)

Use
As of Release 4.71, the view type Coding Analyses for the Clinical Work Station
includes the following new features:
Selection Screen for the View Type Coding Analyses
Case Selection group box

Discharged from Dept indicator
This indicator lets you stipulate that only discharges from the department you
specified in the case selection are to be shown.
Healthy Newborns indicator
The Healthy Newborns indicator lets you include the relevant cases in the
case selection.
The selection options in the Case Selection group box are linked with "and".
DRGs tab page

DRG Catalog and DRG Code indicators
The selection options on the DRGs tab page are linked with "or".
Other tab page

The output of the selection fields is only relevant if you bill for DRGs according to
KFPV (ordinance regulating hospital flat rate per case systemGermany) in your
institution.
Min. LOS Shortfall indicator (minimum length of stay for a DRG service)
If you set this indicator, the system includes the case in the worklist for the
output list if the length of stay falls short of the minimum length of stay for a
DRG service.
Max. LOS Overrun indicator (maximum length of stay for a DRG service)
If you set this indicator, the system includes the case in the worklist for the
output list if the length of stay exceeds the maximum length of stay for a
DRG service.
Discount for Transfers indicator (shortfall of average length of stay for a DRG
service)
Discounts for transfers are taken into account for a case, when the transfer
in question is from or into an external hospital. If you set this indicator, the
system includes a case in the worklist of the output list, if the length of stay
falls short of the average length of stay for a DRG service.
The selections on the Other tab page are linked with "or".
Field Catalog
The column selection for the view type "Coding Analyses" has been enhanced as
follows:
Diagnosis Information Area

DRG principal diagnosis (diagnosis catalog, diagnosis code, diagnosis text)
Note that the output of the case-related diagnosis information is linked to
whether the user is authorized to display the determined diagnosis.
29
DRG Information Area

The output of the case-related DRG key figures is only relevant if you bill for
flat rates per case according to KFPV (ordinance regulating hospital flat rate
per case systemGermany) in your institution.
Information on DRG service (service catalog, service, service short text)
Length of stay of a case in days (LOS Fall)
Maximum length of stay (LOS) for a DRG service (Max. LOS)
Minimum LOS for a DRG service (Min. LOS)
Average length of stay for a DRG service (Average LOS)
Maximum LOS overrun main/external physician department in days (>
MLOS (D))
Minimum LOS shortfall main/external physician department in days (< mLOS
(D))
Average LOS shortfall main/external physician department in days (< ALOS
(D))
Indicator for maximum LOS overrun (icon > MLOS)
Indicator for minimum LOS shortfall (icon < mLOS)
Indicator for average LOS shortfall (icon < ALOS)
Maximum LOS reached in days (MLOSR (D))
Cost weight maximum length of stay (CW MLOS)
Cost weight minimum length of stay (CW mLOS)
Cost weight average length of stay shortfall (CW ALOSS)
See also
For more information, refer to the release notes entitled DE: DRG Billing According
to Option Model 2003 and DE: Billing of Flat Rates per Case According to KFPV (not
available in English).
DE: "Length of Stay" Indicator (Changed)

Use
DE: Interface for DRG Coding and Grouping System (Enhanced)

Use
BAPI for Changing, Creating and Canceling Diagnoses (New)

Use
This release makes available to you the new Business Application Programming
Interface (BAPI) BAPI_CASEDIAGNOSIS_MODIFYMULT that lets you create,
change and cancel diagnoses in a single step.
30
See also
For further information about authorizations and functionality, refer to the
documentation for the BAPI.
DRG Data Maintenance Business Add-In (New)

Use
With this release, the Business Add-In (BAdI) IS-H: Check Medical Documentation in
NPDRG2 (ISH_NPDRG2_FINAL_CHK) is available to you in the DRG work station
(transaction code NPDRG2).
This BAdI lets you check the following data and, if necessary, issue messages that
prevent the data from being saved:
Case data
Patient data
Movement data
Procedure data
Diagnosis data
DRG data
The system calls the BAdI when the Check and Save functions are executed.
You have to activate the BAdI.
See also
You'll find further information about the BAdI in the IS-H Implementation Guide under
SAP Healthcare Industry-Specific Components for Hospitals Medical/Nursing
Documentation Business Add-Ins for Medical/Nursing Documentation BAdI:
Check Medical Documentation in NPDRG2.
You'll find information about activating a BAdI in the SAP Library under SAP Web
Application Server ABAP Workbench Changing the SAP Standards
Business Add-Ins.
Notification of End of Maintenance of Tables NLOP and NICP2

Use
2004), SAP will end maintenance for the following tables:
NLOP IS-H: Assignment Table ServiceSP CodeDiagnosis
NICP2 IS-H: DRG-Relevant Surgical Procedure Codes
The table NLOP has already been superseded by the following tables:
NICP IS-H: Surgical Procedure Codes Performed
NLICZ IS-H: Table of Service-to-Surgical Procedures Code Asgmts
NDICZ IS-H: Table of Diagnosis-to-Surgical Procedures Code Asgmts
The data in the table NICP2 was already remapped to the table NICP in SAP Patient
Management Release 4.62. The table NICP contains case-related procedures,
surgery-related procedures and DRG-relevant procedures.
31
The tables mentioned above will be deleted with the next release.
For this reason, these tables must no longer be used in programs or reports as of the
next release. If needs be, modify customer-specific programs/reports.
Authorizations in DRG Work Station (Changed)

Use
In previous releases, SAP Patient Management checked with the value NPDRG in
the authorization object N_EINR_TCO for the DRG work station (transaction codes
NPDRG1 and NPDRG2). With SAP Patient Management Release 4.71, the system
checks with the transaction code (NPDRG1 or NPDRG2).
Take this into consideration in your authorization objects.
In previous releases, the DRG work station could only be called in display mode
(transaction code NPDRG1) if you had authorization to change at least for one
organizational unit of the case. You will now need authorization to display at least
one of the organizational units of the case.
To be able to execute the Group function in the DRG work station, you need to be
assigned the activity '01' for Create DRG Code in the authorization object N_NDRG.
When you generate a new DRG code using the Group function, the system
automatically cancels the previous DRG code and creates a new DRG code. To be
able to cancel DRG codes, the user requires the activity '02'Change DRG Code,
since canceling is implicitly carried out also when you change existing DRG codes.
Procedure Entry (New/Changed)

Use
Procedure Sort Sequence

In previous releases, when you entered procedures and chose Sort, the system
sent a dialog box with five procedure fields, each of which you could use as a
sort criterion. As of this release, you can position the cursor on a column in the
procedure table, and choose either Sort in Ascending Order or Sort in
Descending Order. In this way, all of the columns or fields that are displayed in
your procedure table are available for sorting the table content.
Sorting according to columns is available to you:
in surgery data maintenance
in DRG data maintenance
in case-related procedure maintenance.
Business Add-In (BAdI) ISH_PROCEDURE_SORT (changed)

The system runs this BAdI once before sending the procedure table.
The call takes place
in surgery data maintenance
in case-related procedure data maintenance
in DRG data maintenance.
This BAdI lets you determine the sequence in which the procedures should be
displayed on the initial screen of the respective transactions; for example, first all
procedure codes starting with 5-*, then those with 8-*, and lastly, those with 1-*.
Sample code is delivered in the standard shipment.
32
Patient Accounting
General Information
AT, CH: Fee Processing (Changed)

Use
This release note is relevant for the country versions Austria and Switzerland only.
Documentation is not available in English.
DE: DRG Billing According to Option Model 2003 (New)

Use
DE: Billing of Flat Rates per Case According to KFPV (New)

Use
DE: Price Determination for DRG Services

Use
DE: Service Rule R12Generation of Quality Assurance Surcharge (New)

Use
DE: Settings for Billing of DRG Services

Use
33
Services
Service Rule R2 with Service Action (Changed)

Use
With SAP Patient Management Release 4.71, the service rule R2 now supports a
service action.
The system handles services that you defined as a service pair exclusion in the IMG
activity Maintain Exclusions/Inclusions for Service Pairs (table NLPA) as follows: it
retains the first service as billable and sets the second service to non-billable.
The settings for the service rule R2 in the IMG activity Define Rule Types and
Maintain Check Procedure have been changed as follows:
Rule types: for the rule type R2, the indicator A (IS-H: Indicator that Rule Type
Supports Actions) is now set.
Use (unchanged): Service Check for Check Procedure
Callup Points (unchanged): for the callup points, the indicator A (IS-H: Indicator
that Rule Type Supports Actions) is set.
In the IMG activity, you can modify the institution-related data to satisfy your
individual requirements by choosing Callup Points Institution-Specific Check
Procedure Service Actions.
Service Rule R12 Generation of Quality Assurance Surchanges (New)

see p. 33.
Service Rule R13: Long-Term Accommodation Services (New)

Use
The service rule Long-Term Accommodation Services (R13) automatically generates
immediate services known as long-term accommodation services according to the
30-day rule for patients in long-term accommodation.
The 30-day rule states that patients who are accommodated in a hospital or nursing
care unit for periods exceeding one month, pay for exactly 30 days per month,
regardless of whether the month has 29, 30, or 31 days. The patients can be
accommodated in different categories of long-term accommodation during a month,
i.e. can be transferred from a private room into a semi-private room.
To accommodate this concept, the service rule contains the following functionality:
It creates a long-term accommodation service for each day. This service is

based on the immediate service that you have assigned to the treatment
category and thus indirectly to each movement of the case in Customizing for
SAP Patient Management.
34
The service rule takes into account the 30-day rule as follows:
If a patient is accommodated in long-term accommodation and in an acute
care facility within the same month, the service rule creates a long-term
accommodation services for each day spent in long-term accommodation.
The same applies if the patient is discharged before the end of the month.
If the patient spends a whole or several month(s) in long-term
accommodation, the service rule creates the following services:
For months with 30 days (e.g. April, June), the system creates a long-term
accommodation service for each day in the month.
For months with 31 days (e.g. January, March), the system creates a longterm accommodation service for each of the first 30 days in the month. The
system doesn't create a long-term accommodation service for the 31st day.
For February, the system creates a long-term accommodation service for
each day and at the last day in February, rounds the number of days up to
30: in leap years (February has 29 days), the system sets the quantity of the
long-term accommodation service for February 29 to "2". If the year is not a
leap year, the system sets the quantity to "3".
The service rule automatically deletes incorrect long-term accommodation

services. Such services can result from the following situations, for example:
A long-term accommodation service that is not linked to a movement can
come into being if a transfer takes place after the system has already
created the long-term accommodation service for this day.
A duplicate long-term accommodation service can come into being if the
start date of a movement is changed.
The service rule obeys the following rules in relation to transfers and
movements:
The service rule does not create a long-term accommodation service on the
last day of the movement. For transfers, the midnight census logic applies: if
the transfer takes place before midnight, the service rule does not create a
long-term accommodation service but a service defined by the movement.
The service rule does not create a long-term accommodation service on the
discharge day.
The service rule creates long-term accommodation services during absences
and outpatient visits.
For transfers within long-term accommodation, the service rule only creates
a new long-term accommodation service if the transfer causes the treatment
category to change.
Transfers can be performed between acute care and long-term
accommodation. If this happens part way through a month, the 30-day rule
does not apply.
You can activate the service rule for the following callup points:
Service Check Before Billing (NLRG01)
Service Check Before Test Billing (NLRG08)
Service Check Before Accrual Calculation (NLRG10)
Service Check Before Test Accrual Calculation (NLRG11)
Service Check During Service Entry (NLRG00)
Service Check at Admission and Transfer (NLRG02)
Service Check at Discharge (NLRG03)
Service Check at Absences (NLRG06)
Service Check in DRG Work Station (NLRG13)
35
In the IMG activity Define Long-Term Accommodation Services, specify the
immediate service you wish to use as the long-term accommodation service.
For more information about this, see Patient Accounting Service Rules Define
Long-Term Accommodation Services in the IS-H Implementation Guide.
For each treatment category you use in the long-term accommodation area, add a
long-term accommodation service in the IMG activity Assign Services to Treatment
Categories.
For more information about this, see Patient Accounting Treatment Categories
Assign Services to Treatment Categories in the IS-H Implementation Guide.
Activate the service rule R13 for the desired callup points in the IMG activity Define
Rule Types and Maintain Check Procedure.
For more information about this, see Patient Accounting Service Rules Define
Rule Types and Maintain Check Procedure in the IS-H Implementation Guide.
SAPscript Long Texts for Case-Related Services (Changed)

Use
This release note is only relevant if you have developed your own programs for
reading the SAPscript long texts for the fields Comment and Multiplication Factor
Reason from the database where case-related services are concerned (e.g. when
printing invoices).
As of this release, the relevant long text indicator REMKZ (for the comment) and
BEGKZ (for the multiplication factor reason) in the table IS-H: Services Performed
(NLEI) contains the language key of the related SAPscript long text.
If a long text does not exist, the field is initial. It can be the case that accessing the
long text with the logon language yields incorrect results. For this reason, when
reading the long texts, you should always use the language defined in the table IS-H:
Services Performed (NLEI).
Service Actions with Long Text Support (New)

Use
As of SAP Patient Management Release 4.71, service actions also let you maintain
the SAPscript long texts for service comments and multiplication factor reasons.
For this purpose, add the table parameter ERNLRT with type ISH_T_RNLRT to your
function modules for service actions. You can pass the texts to be modified to the
system using this table parameter.
To delete a SAPscript text, specify the relevant language key without any text in the
new parameter.
The specified texts are linked to the corresponding service records in the same way
as physician assignments using the fields IS-H: Rule Type (RGART) and IS-H:
Sequence Number of a Service Action (LFDAK).
For performance reasons, the existing texts are not passed via the interface. If needs
be, you have to read the texts using the function module ISH_TEXT_GET. To do
this, fill the interface parameters as follows:
36
ss_tdobject = 'NLEI'
ss_tdid = '0001'
ss_tdname = <EINRI><FALNR><LNRLS><ID>
" <ID> = '01' for multiplication factor reason
" = '02' for comment
SS_KZTXT = <short text>
" NLEI-BEGTX for multiplication factor reason
" NLEI-REMRK for comment
ss_lgtxt = ' '
ss_langu = <language>
" NLEI-BEGKZ for multiplication factor reason
" NLEI-REMKZ for comment
You can tell whether a SAPscript text exists or not from the related language
indicator (NLEI-BEGKZ or NLEI-REMKZ). If the corresponding field is empty, there is
not text.
AT: Status Check in Service Entry

Use
AT: Service Rule A15 Max. Values for Groups w/o Ins. Relationships
Use
AT: Service Rules (Changed)

Use
Insurance Verification
CH: Changes in Insurance Verification (Changed)
Use
This release note is relevant for the country version Switzerland only. Documentation
is not available in English.
37
Billing
CH: Invoicing (Changed)

Use
This release note is relevant for the country version Switzerland only. Documentation
is not available in English.
DE: Interim Billing for DRG Services (Changed)

Use
Collective Invoice for Self-Payers (New)

Use
In previous releases, you were able to create collective invoices for insurance
providers. With SAP Patient Management Release 4.71, you can also create
collective invoices for self-payers.
Multiple single invoices are issued in particular for day clinic patients and patients
with frequent outpatient visits. A collective invoice for self-payers offers greater clarity
for these patients and saves unnecessary bank transfer costs since the patient can
transfer the amount for multiple invoices in a single operation.
Checks at Form Printout
Once a self-payer invoice is assigned to a collective invoice, you can only execute
the form print function for this invoice in test print mode. This affects mass print
(RNADIN03) and the case-related invoice overview (NA30).
Change to Smart Forms
The parameter RNF01_SELFPAYER has been added to the Smart Forms interface.
If a collective invoice exists for a self-payer, the patient data is passed to this
structure. Add this parameter to the form interface of your Smart Form if you create
collective invoices for self-payers in your institution.
See also
For further information, refer to the documentation for the program Create Invoice
Selection.
Printing of Dunning Notices with Smart Forms (Changed)

Use
In previous releases, you were only able to print items from SAP Patient
Management using the FI dunning program (transaction code F150) in SAPscript
format. SAP Patient Management Release 4.71 lets you print dunning notices with
Smart Forms as well.
38
The new function module ISH_DUNNING_EVENT_CREATE_SF has been provided

for this purpose.
If you wish to switch over the printing of dunning notices to Smart Forms, make the
appropriate settings for the items from SAP Patient Management in Customizing for
Financial Accounting under Financial Accounting Global Settings Business
Transaction Events. (event:00001720, application: IS-H). Note that you also have to
change settings for Financial Accounting here.
See also
For more information about Smart Forms, refer to the SAP Note 430621.
For information about configuring dunning notice printing with Smart Forms in
Financial Accounting, refer to the release notes for FI.
DE: Determination of Share of Costs for Outpatient WC Billing (Changed)

Use
"Charge Factor Value" Indicator in IMG Activity "Determine Catalog

Columns" (Changed)
Use
The Charge Factor Value indicator is no longer available to you in the IMG activity
Determine Catalog Columns in SAP Patient Management Release 4.71.
In previous releases, you had to set this indicator if the catalog column used by the
system to determine the basic price for service invoicing contains a charge factor
value.
With this release, SAP Patient Management gets this information directly from the
catalog column definition in the IMG activity Define Catalog Columns.
39
Integration with Materials Management

General Information
Reports for Material List and Material Consumption (Enhanced)

Use
The following changes have been made to the reports for the material list and
material consumption for SAP Patient Management Release 4.71:
Report IS-H: Material List (RNLMAT01)

The choice field ATC Code is available to you in the Data Selection group
box on the selection screen.
You can further restrict your selection by active ingredient in the Restriction
group box.
The active ingredient fields and additional text fields are available to you in
the output list.
Report Ad Hoc Purchasing and Consumption Analysis (RNLMAT02)

The material number and the corresponding short texts are available to you in
the output list.
See also
For further information, refer to the documentation for the reports:
IS-H: Material List
Ad Hoc Purchasing and Consumption Analysis
Master Data
Closet (New)
Use
SAP Patient Management Release 4.71 lets you depict closets to be used with the
OU-related material requisition function.
A closet is usually divided into storage locations with shelves and bins that you can
use as "addresses" for a rational replenishment process.
This is taken into account as follows in the OU-related material requisition function:
In previous releases, the system took the order quantity and order unit from the
default values when a material was entered. If the material wasn't on the default list,
the system took the quantity and unit from the catalog, as standard.
40
With this release, the system first checks if the material you're entering is contained
in a closet assigned to the requesting organizational unit. If this is the case, the
system takes the order quantity and order unit from here and transfers these values
into the material requisition. The system also transfers the address of the storage
location into the Goods Recipient field. In this way, the storage location address of a
material is available, for example, for output on a goods issue/goods receipt slip.
Make the relevant settings for the closets in the IMG activity Define Closet.
Extraction Healthcare-Specific Attributes of Material Master (New)see p. 43.
Material Requisition
Procurement Type and Document Type Determination (New)
Use
SAP Patient Management Release 4.71 makes available to you the IMG activity
Determine Procurement Types and Document Types. This IMG activity lets you
determine how a material, which is requested using the material requisition function,
is procured for a specific institution.
In previous releases, the material type of the material to be requested determined
whether a material requisition was created from SAP Patient Management as a
reservation or a purchase requisition in Materials Management. Reservations were
created for materials kept in stock and purchase requisitions for materials not kept in
stock.
The new IMG activity enables this decision to be made more flexibly on the basis of
the following parameters:
Institution
Requesting organizational unit
Material
Issuing point
If you wish even greater flexibility in controlling the procurement type and document
type, this release makes available to you the Business Add-In (BAdI) IS-H MM:
Procurement Type/Document Type Determination (ISH_MM_DOCTYPE).
The Doc.Type PReq parameter to be set in the basic settings for Materials
Management in SAP Patient Management is obsolete. You now have to set this
parameter using the new document type determination.
After upgrading to the new release, you don't have to perform any activities on
account of the new functionality. An XPRA applies the Customizing settings so that
the material requisition functions as in previous releases.
41
Organizational Unit-Related Material Requisition (Enhanced)

Use
SAP Patient Management Release 4.71 provides the following new functionality in
the OU-related material requisition:
In the IMG activity Maintain Basic Settings you can preset the desired delivery date
in relation to the current date. The Preset field (instparameter) is available to you for
this purpose on the basic settings detail screen. The desired delivery date contains
the current date by default.
42
Information System
Business Information Warehouse Interface
Extraction Healthcare-Specific Attributes of Material Master (New)

Use
Since SAP Patient Management Release 4.63B, healthcare-specific fields (e.g.
active ingredients, ATC code) of the material master have been available to you for
the hospital pharmacy application area.
The DataSource IS-H: DataSource Healthcare-Specific Fields for Material
(OHC_MATERIA_ATTR) in SAP Patient Management Release 4.71 now lets you
extract these attributes into the SAP Business Information Warehouse.
See also
For information about the DataSource, refer to the documentation for the SAP
Business Information Warehouse Release 3.10 under Business Content Industry
Solutions Healthcare DataSources IS-H: Datasource Healthcare-Specific
Fields for Material.
43
Communication
Communication with Systems Outside the Hospital
EDI Worklist (New)

Use
As of SAP Patient Management Release 4.71, the EDI Worklist (RNCEDIWORK2,
transaction code NEDIW) replaces the previous inbound worklist (IS-H EDI: Inbound
Messages, Manual Postprocessing, RNC301I2) and the previous outbound worklist
(IS-H: EDI Messages, RNC301U2).
The result is a standardized interface for working with EDI messages. Moreover, the
Reimport function simplifies reimporting individual inbound messages.
You can still access the outbound and inbound worklists using the transaction
codes NEDIOUT and NEDIIN respectively.
See also
For detailed information about the functions, refer to the documentation for the EDI
Worklist.
EDI File Status Management for EDI Inbound Processing (Changed)

Use
File status management for EDI inbound processing has been simplified in SAP
Patient Management Release 4.71. The following file statuses are available to you:
external error: the system sets this file status when it rejects a file.
ok, completed: the system sets this file status when it has uploaded a file.
If the system rejects a file more than once, a separate file management record is
kept for each rejection. The system renames rejected files in the file system to avoid
collisions with corrected files received at a later date. You'll find the renamed files in
the file overview.
During the release upgrade, the XPRA RNXPRA471_1 automatically checks all EDI
inbound file management records of the current and previous years for incorrect
error status specifications and corrects these, if needs be.
See also
You'll find more information in the SAP note 540729, which provided you with this
functionality in advance of the current release.
44
DE: Supplement to 301 Data Transfer (Changed)

Use
DE: 301 Procedure for DRG Billing (New)

Use
EDI: Recreate Outbound Messages (New)

Use
SAP Patient Management Release 4.71 makes available the program IS-H EDI
Recreate Outbound Messages (RNCEDIRECREATE).
This program lets you assemble existing outbound EDI messages according to
different selection criteria, and recreate all of the selected messages at once.
See also
For more information, see the documentation for the program IS-H EDI Recreate
Outbound Messages,
45
Tools
General Information
DE: Output DRG Surcharges and Discounts on Invoice Form (New)

Use
46

Sap Is H Rel471 Word

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Is H Rel471 Word

Uploaded by

Copyright:

Available Formats

Release

Release Notes SAP Patient Management 4.71

Release Notes SAP Patient Management 4.71

Important Activities for Release 4.71

AT: Technical Number Ranges (Changed)

Clinical Work Station

Reactivate Preregistration when Canceling Admission/Visit (New)

Patient Master Data

General Case Processing

Care Unit Management

Outpatient Clinic Management

Release Notes SAP Patient Management 4.71

Basic Medical/Nursing Documentation

AT, CH: Fee Processing (Changed)

Integration with Materials Management

Reports for Material List and Material Consumption (Enhanced)

Business Information Warehouse Interface

Release Notes SAP Patient Management 4.71

Communication with Systems Outside the Hospital

DE: Output DRG Surcharges and Discounts on Invoice Form (New)

Release Notes SAP Patient Management 4.71

Release Notes SAP Patient Management 4.71

SAP Patient Management Release 4.71

Specify IS-H as the Add-On ID.

A number of release notes relate exclusively to developments for particular country

AT: Release note for the country version Austria

CA: Release note for the country version Canada

CH: Release note for the country version Switzerland

DE: Release note for the country version Germany

SG: Release note for the country version Singapore

Release Notes SAP Patient Management 4.71

If various changes described in a release note apply to particular country versions,

Release Notes SAP Patient Management 4.71

DE: DRG Billing

Changes to authorizations in the transactions NPDRG1 and NPDRG2

Notification of End of Maintenance of Functions

Release Notes SAP Patient Management 4.71

Clinical Work Station

Release Notes SAP Patient Management 4.71

Special Features in Country Version Germany

mySAP Customer Relationship Management for Healthcare 4.0 (New)

Health insurance providers

Interaction Center support

Efficient appointment management

Invitations for preventive and aftercare medical examinations

Target group-specific advertising

Support of mobile outpatient nursing services.

Health insurance provider

Release Notes SAP Patient Management 4.71

Business partner relationship between patient and health insurance provider

Business partner relationship between patient and attending physician

Business partner relationship between patient and family physician

Business partner relationship between patient and employer

Business partner relationship between physician and doctor's practice

Business partner relationship between physician and hospital (workplace)

The business partner relationship "Contact Person Relatationship" ("Is Contact

Release Notes SAP Patient Management 4.71

AT: Technical Number Ranges (Changed)

Notification of End of Maintenance of "Maintain/Display Insurance Provider

NG20 Display Insurance Provider Group

NG21 Maintain Insurance Provider Group

Notification of End of Maintenance of "Create RP Employee"

Release Notes SAP Patient Management 4.71