administration guide sap emr unwired backend adapter for

Administration Guide SAP EMR Unwired Backend Adapter for SAP Patient Management (IS-H) and i.s.h.med SAP ERP 6.0, Industry Extension Healthcare, IS-H 618 Support Package 04 Valid for Country Version Germany and Generic Versions Version of Guide: 1.1 June 13th, 2016

www.sap.com

ADMINISTRATION GUIDE SAP EMR UNWIRED BACKEND ADAPTER FOR SAP PATIENT MANAGEMENT (IS-H) DOCUMENT VERSION 1.0; JUNE 13TH, 2016

Version Status Date

1.0 First version published June 6th, 2016

1.1 Enhancement in chapter 2. June 13th, 2016


3

CONTENTS

1. Introduction ........................................................................................................................................................ 4

2. Sources of Further Information About the SAP EMR Unwired App ..................................................................... 4

3. Prerequisites ....................................................................................................................................................... 4

4. Function of SAP EMR Unwired Backend Adapter in SAP Patient Management ................................................... 5

4.1 General Function ............................................................................................................................................. 5

4.1.1. Patient Lists ........................................................................................................................................................... 5

4.1.2. Patient Search ....................................................................................................................................................... 5

4.1.3. Time Intervals ....................................................................................................................................................... 5

4.1.4. Uploading User Photos ......................................................................................................................................... 6

4.1.5. Creating Patient Photos ........................................................................................................................................ 6

4.1.6. Authorizations ....................................................................................................................................................... 7

4.1.7. Read Access Logging ............................................................................................................................................. 7

4.1.8. Treatment Authorization ...................................................................................................................................... 7

4.1.9. Pseudonymization ................................................................................................................................................. 7

4.2 Use of Individual Facets .................................................................................................................................. 7

4.2.1. Coding Data .................................................................................................................................................... 8

4.2.2. Patient Master Data ....................................................................................................................................... 8

5. Use of SAP EMR Unwired Backend Adapter in i.s.h.med ..................................................................................... 8

5.1 General Functions ........................................................................................................................................... 8

5.2 Use of Individual Facets .................................................................................................................................. 8

5.2.1. Allergies ................................................................................................................................................................ 8

5.2.2. Laboratory ............................................................................................................................................................ 9

5.2.3. Clinical Orders ....................................................................................................................................................... 9

5.2.4. Progress Documentation ...................................................................................................................................... 9


4

1. Introduction SAP EMR Unwired Backend Adapter enables the seamless integration of SAP Patient Management (IS-H) / i.s.h.med and the SAP EMR Unwired app using SAP Mobile Server for Healthcare. SAP EMR Unwired Backend Adapter is available as of SAP ERP 6.0, Industry Extension Healthcare, IS-H 618 Support Package 04. It has been released for the country version Germany and the generic versions. SAP EMR Unwired Backend Adapter is part of the standard delivery of SAP Patient Management (IS-H). It is independent of the Backend Adapter provided by SAP Germany, which is subject to charge. SAP EMR Unwired Backend Adapter is compatible with the app SAP EMR Unwired Version 2.X and the

SAP Mobile Server for Healthcare (component MEMR ADAPTER), Version 1.0, as of Support Package 13.

SAP EMR Unwired Backend Adapter supports the functions in SAP Patient Management and i.s.h.med described below. You can use the configurable EMR Middleware to add customer-specific enhancements to the SAP EMR Unwired app. Contact your regional SAP consultancy if necessary.

2. Sources of Further Information About the SAP EMR Unwired App

Type of Information

Hyperlink

SAP EMR Unwired at the iTunes Store

http://itunes.apple.com/en/app/sap-emr-unwired/id535775761?mt=8

SAP EMR Unwired at the Google Play Store

https://play.google.com/store/apps/details?id=com.sap.mobile.healthcare.emr.v2

SAP EMR Unwired at Microsoft Store

Deutsch: https://www.microsoft.com/de-de/store/apps/sap-emr-unwired/9wzdncrdn09t English: https://www.microsoft.com/en-us/store/apps/sap-emr-unwired/9wzdncrdn09t

Administrator’s Guide for SAP EMR Unwired solution on the Service Marketplace

http://service.sap.com/~sapidb/012002523100000687752012E

SAP Security Guides http://service.sap.com/securityguide

Table 1: Overview of Hyperlinks to Sources of Further Information

3. Prerequisites This document describes how to configure the specific Backend Adapter to connect the SAP EMR Unwired app to the product SAP Patient Management (IS-H) and Cerner’s clinical solution i.s.h.med.

http://itunes.apple.com/en/app/sap-emr-unwired/id535775761?mt=8

https://play.google.com/store/apps/details?id=com.sap.mobile.healthcare.emr.v2

https://www.microsoft.com/de-de/store/apps/sap-emr-unwired/9wzdncrdn09t

https://www.microsoft.com/de-de/store/apps/sap-emr-unwired/9wzdncrdn09t

https://www.microsoft.com/en-us/store/apps/sap-emr-unwired/9wzdncrdn09t

https://www.microsoft.com/en-us/store/apps/sap-emr-unwired/9wzdncrdn09t

http://service.sap.com/~sapidb/012002523100000687752012E

http://service.sap.com/securityguide


5

Before using the app, you must install and configure the required middleware together with all the necessary components. These settings are not covered by this documentation. When installing and configuring the middleware, please refer to the Administrator’s Guide for SAP EMR, which is linked above, and where the basic functions of the SAP EMR solution are also described. The guide also describes the necessary settings for mobile devices and for the app itself. See SAP Note 2313856 for information on how to configure the middleware for SAP Patient Management and i.s.h.med. We recommend that you install SAP Afaria for device management.

4. Function of SAP EMR Unwired Backend Adapter in SAP Patient Management

Once you have met prerequisites for using the SAP EMR Unwired app as described in section 3, you can, in principle, connect it to SAP Patient Management without having to make further settings. The function of the app in general, as well as that of individual facets, is described below. The various sections contain notes on how to configure the system behavior.

4.1 General Function

4.1.1. Patient Lists Data retrieval in the backend system takes place primarily using the existing functions of the Clinical Work Station (transaction NWP1). In effect, the app displays all the Movement and Outpatient Clinic/Service Facility views that are already assigned to the user in the Clinical Work Station. The app does not display views that are not assigned a selection variant, since predefined selection parameters (such as Organizational Unit) are not available in this case.

4.1.2. Patient Search The system searches all the institutions for which the user has authorization. If a patient is found in more than one institution, the app displays the name of the institution and the patient’s name so that you can distinguish between them.

4.1.3. Time Intervals You can select a timeframe for the data displayed for the patient in the detailed facets using time intervals. If you do not make any further settings, the app lists the patient’s individual cases as a time interval, as well as an “unlimited” time interval displaying all the patient’s data. In the Customizing activity Define Time Intervals (in Customizing under SAP Healthcare - Industry-Specific Components for Hospitals → Tools → Integration with SAP EMR Unwired), you define which additional "case-independent" time intervals are available for the user to select in the SAP EMR Unwired app.


6

Example

Data since yesterday

Data from past week

Data from last 4 weeks

For more information, see the documentation for the Customizing activity.

4.1.4. Uploading User Photos

In transaction OAOR, you can store a photo in the system for each mobile device user. The system then

displays this photo alongside the user name in the logon facet. To upload a photo, call up transaction OAOR

and enter the following parameters:

1. Class name: PICTURES

2. Class type: OT

3. Object key: &USERNAME& 4. Choose Execute (F8) 5. Expand Standard Doc. Types in the subscreen in the bottom left-hand corner and double click on

Screen. 6. Select image from local file directory and upload it.

Caution Make sure you adhere to the data protection regulations that apply in your hospital/institution with regard to images.

4.1.5. Creating Patient Photos You can use the SAP EMR Unwired app to take photos of patients and transfer them to the backend for storage. The photo is then loaded from the backend when a record for the corresponding patient is accessed. The Backend Adapter helps you update and display patient photos using the Business Document Service

(BDS), transaction OAOR. To this end, a file with the following attributes is stored for each patient:

Name of patient photo: #<10-digit patient number with leading zeros>#

Class name = PICTURES

Class type = OT Before you can take photos of patients on mobile devices and store them, you must configure the image format in the SAP system. You do this as follows:

1. Call up transaction SM30.

2. Select table/view V_TOADD.

3. Choose Edit. 4. Choose New Entries.

5. Document class: ZPNG

6. Description: Portable Network Graphic 7. MIME type: image/png 8. Application: [leave field blank]

The system also displays these patient photos in the patient header and case header in the Clinical Process

Builder (transaction NV2000), in the case monitor, and in the i.s.h.med patient organizer.


7

Caution Make sure you adhere to the data protection regulations that apply in your hospital/institution with regard to images.

4.1.6. Authorizations Users who will be using the SAP EMR Unwired app on mobile devices need to be assigned the following authorizations in the backend system:

S_RFCACL – Authorization Check for RFC User (e.g. Trusted System)

S_SERVICE – Check at Start of External Services

S_RFC – Authorization Check for RFC Access

The SAP EMR Unwired app uses the authorizations already assigned to the user for their previous tasks for read access to the patient data in the backend system.

4.1.7. Read Access Logging SAP EMR Unwired Backend Adapter supports the read access logging function in SAP Patient

Management. In the report for displaying the logs (RNALOGEVAL), instances of read access initiated by the

app are indicated by the transaction code RFC and program names beginning with the prefix /ISHMEMR/.

4.1.8. Treatment Authorization SAP EMR Unwired Backend Adapter supports the treatment authorization in SAP Patient Management. If the user does not have treatment authorization for a patient, they cannot display details in the app.

4.1.9. Pseudonymization If you use the pseudonymization function in SAP Patient Management, the app behaves in exactly the same way as SAP Patient Management. The user can see original data or pseudonymized data depending on their authorization.

4.2 Use of Individual Facets You only need to make the settings described here for the individual facets if you want to use them and the relevant function is in operation in the backend system.


8

4.2.1. Coding Data In the country version Germany of SAP Patient Management, diagnoses, procedures, DRG data (DRG: Diagnosis Related Group), and problems are transferred to the "Coded Data" facet for display; you do not need to make any further settings to display this data on mobile devices. In the generic version of SAP Patient Management, diagnoses, procedures, and problems are transferred to the "Coded Data" facet for display; you do not need to make any further settings to display this data on mobile devices. The system does not display detailed DRG data (such as maximum length of stay) in the "Coded Data" facet, since this data is not available in the generic version. However, the system does display the patient’s medical DRG in the patient lists and the patient header.

4.2.2. Patient Master Data The following master data is transferred to the corresponding facet:

Patient address and contact data

Religion

Risk factors/allergies

Health insurance information. The app only displays the highest ranking insurance relationship. If there are other insurance relationships, the app simply displays a message indicating that these exist.

Family physician and referring physician

Employer No further settings are necessary.

5. Use of SAP EMR Unwired Backend Adapter in i.s.h.med

5.1 General Functions As of IS-H 618 Support Package 04, i.s.h.med provides a standard implementation of the available Business Add-Ins (BAdIs) for data connection to support the following facets:

Laboratory

Clinical Orders

Progress Documentation (SAP EMR Unwired Progress Notes)

Allergies Support of other facets is planned for future Support Packages.

5.2 Use of Individual Facets

5.2.1. Allergies You do not need to make any further settings to display allergies with patient data.


9

5.2.2. Laboratory If you use the standard cumulative laboratory findings function in i.s.h.med, which is based on documents of

type N2LABOR, the standard system supports the transfer of laboratory data. You do not need to make any

further settings for this facet. If you use a customer-specific solution to display laboratory data, you need to create your own

implementation for BAdI /ISHMEMR/ISH_PAT_LAB_RESULTS. In this case, please contact your

implementation partner or SAP Consulting for advice on setting up a customer-specific connection to the laboratory system.

5.2.3. Clinical Orders The system transfers clinical orders for display in the Clinical Orders facet. The system does not take service requests into account. The system breaks down clinical orders into their services for display. This means a number of individual services may be displayed on the mobile device for one clinical order in i.s.h.med. You do not need to make any additional settings for display in SAP EMR Unwired if you use the standard system.

5.2.4. Progress Documentation The standard system supports the transfer of entries in progress documentation. Before you can use this facet in SAP EMR Unwired, you need to configure progress documentation in the backend. If you use the progress documentation function, you do not need to make any further settings to display the entries in this facet.

To simplify the creation of new entries, you can create text modules in transaction N2TBS in i.s.h.med. You

can, in principle, use all user-related text modules when creating progress entries on a mobile device. You

can also define specific text modules. To do this, create the set EMRC_ISHMED_VD and assign the text

modules to this set ID. Inpatient and outpatient progress notes are not supported. However, you can enable these applications by

defining your own implementation of the BAdI /ISHMEMR/ISH_PAT_NOTES. In this case, please contact

your implementation partner or SAP Consulting for advice on setting up a customer-specific connection.


10

© Copyright 2016 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 purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries.

All other product and service names mentioned are the trademarks of

their respective companies. Please see www.sap.com/corporate-

en/legal/copyright/index.epx#trademark for additional trademark

information and notices.

administration guide sap emr unwired backend adapter for

Documents