ehs management occupational health

EHS Management Occupational Health

SAP Best Practices for Environment, Health, and Safety Management

© 2011 SAP AG. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

Purpose

Process Overview: Commodity: AllCompanies have to follow a zero-harm-to-the-workforce approach, which must be realized through regular examination and testing of employees to ascertain and maintain their health. These examinations are carried out by an occupational health professional, on all employees who will be exposed to risks in the working environment.

The reporting of statistical injury and occupational illness information is made possible by capturing the information in the injury/illness log.

Highlights:• Master Data building up to pre-configured protocols and specific protocols can be added.

• Example of a Questionnaire.

• Demonstrating protocol proposal ability for workplace exposure and age analysis. Upload of medical test result data is possible e.g. laboratory blood test results.

• Ability to link documents to Medical services, persons and examinations


Purpose, Benefits, and Key Process Steps (Cont’d)

Benefits

The following are the benefits of EHS Management Occupational Health scenario:

• Medical Services with follow-up activities

• Health surveillance protocols

• Injury/illness log

• Reports of examination results, restrictions, diagnoses, questionnaires and assignments

Key Process Steps

• Maintaining Examinations, Protocols and Diagnosis Types and Categories

• Maintaining Questionnaires and Catalogs

• Creating Medical Surveillance and Injury/illness logs


Required SAP Applications and Company Roles

Required• Enhancement package 5 for SAP ERP 6.0

Integration• Integration into HR Personnel Administration• Organizational Management

Company roles involved in process flows• HR Manager• Industrial Hygienist• Occupational Health Physician• Occupational Nurse• Medical Data Manager


Injury/Illness Management

Business Benefits

HR DepartmentOccupational Health Nurse

Incident Investigator

Authorities

•Assignment of exposure ratings to

Exposure Group reduces data

maintenance of person related

exposure assignment

•Tracking of org. assignment and exposure history

•Automatic change in protocol assignment

when org. structure/job/task/po

sition or exposure changes

•Correct proposal based on trigger – i.e. risk driven and

target organ related surveillance

•HR Time management for

leave plan of employee

Create Medical Service

Report Injury/Illness

Medical Station

Record injury detail (i.e. body

part)

Record absence

Create Injury/illness by

Injury type

Maintain Applicant Data / External Person

Investigate Incident

Transfer Injury/Illness to

Incident


Process Flow DiagramEHS Management Occupational Health

EH

S

Man

agem

ent

: O

ccu

pat

ion

al

Nu

rse

Eve

nt

EH

S

Ma

na

gem

en

t:

HR

D

epa

rtm

en

t

Risk Assessment

Verify Health Surveillance

Protocols status

EH

S

Man

agem

ent:

O

ccu

pat

ion

al

Hea

lth

P

hys

icia

n

Injury/Illness Management Other

Assign Questionnaire

for Surveillance

Protocol

Assigning Protocols to a

Person

Creating Medical Service

Schedule Medical

Service and Printing

Invitation and Questionnaire

Entering Questionnaire

Responses

Overview of Medical Service

Performing Medical Service

Person complet

es question

naire

Medical Questionnaire


Process Flow DiagramFor further details, see section 4 in the BPD

Injury/Illness Management

Me

dic

al C

en

ter

Pe

rso

nn

el

Injury occurs

Enter Persons affected and

persons involved

Enter Event location and time

of event

Other

Incident/Accident Management

Occupational Health

Is the patient treated at Medical

Center?

Create Medical Service

Create Injury/Illness log

Select Injury type

Enter Aid given information

Enter Treatment location

informationEnter additional

information

Set relevant injury indicators if applicable

Enter Time of aid given

Enter Plant

Is this related to a Inc/Acc log?

Transfer data from Injury/Illness log

Person absent from work

Update Absence information

Reporting

Injury/Illness management

Yes

No

Yes

No

CBIH72 CBIH72 CBIH72 CBIH72 CBIH72 CBIH72

CBIH72CBIH72CBIH72CBIH72

CBIH72 CBIH72


Transaction Process Flow – OH Medical Surveillance

EHSAMBTAET Enter Questionnaire results

EHSH_D_PCP Plan / Schedule Medical Surveillance

EHSAMBTAET Capture results / Import medical data

EHSAMBTAET Perform Medical Surveillance

EHSAMBTAET Close medical service

EHSAMBTAET Print medical certificates


Transaction Process Flow – OH Injury / Illness Log

CBIH72 Enter Persons affected & persons involved

CBIH72 Create Injury/Illness log

CBIH72 Create Medical Service

CBIH72 Update Injury/Illness log

EHSAMBTAET Close medical service

CBIH72 Close Injury/Illness log


Master Data Used

HR Master Data• Creating Personnel Area

• Defining Daily Work Schedule

• HCM Organizational Management

• Creating Employee, and so on

Master Data steps• Creating Exposure groups (Manual Step)

• Creating Laboratory tests

• Creating Physical tests and Examinations

• Creating Health Surveillance Protocol

• Creating Phrase and Phrase Set Header

• Matching up Master Data

• Creating Work Area Exposure and Data Integration

• Creating Business Partner (Manual Step)

• Create Applicant (Manual Step)


Legend

Symbol Description Usage Comments

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

Hardcopy / Document: Identifies a printed document, report, or form

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Financial Actuals: Indicates a financial posting document


Budget Planning: Indicates a budget planning document


Manual Process: Covers a task that is manually done

Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.

Existing Version / Data: This block covers data that feeds in from an external process

Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines

System Pass / Fail Decision: This block covers an automatic decision made by the software

Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.

Ext

erna

l to

SA

P

Business Activity / Event

Unit Process

Process Reference

Sub-Process

Reference

Process Decision

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Process

Existing Version /

Data

System Pass/Fail Decision

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.

The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario.

Role band contains tasks common to that role.

External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.

Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.

Connects two tasks in a scenario process or a non-step event

Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario

Does not correspond to a task step in the document

Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario

Corresponds to a task step in the document

Process Reference: If the scenario references another scenario in total, put the scenario number and name here.


Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here


Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.

Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

<F

unct

ion>


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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

ehs management occupational health

Documents

examinations2011 sap

sap erp

sap applications

safety management2011

specific protocols

process flow diagramfor

text box

width of box