Nexus Program

Business Process Reengineering (BPR)

Overview
August 2012
Copyright 2010 Allscripts Healthcare Solutions, Inc.

Agenda
Definition

Strategic Alignment & Benefits

Assumptions Organization & Timeline Standards & Methods Document Management

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Definition
Business Process Reengineering (BPR) typically includes:

Business Goals & Strategy

Key Performance Indicators (KPIs) & Metrics Process Redesign (Current to Future State) Process Integration (across Business Cycles) Process Simulation (validate future state performance) Process Optimization (fine tuning & recalibration)

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Strategic Goals
The purpose of the Nexus Business Process Reengineering

(BPR) initiative is to ensure that the strategic goals are

achieved: Enable Legacy Allscripts and Legacy Eclipsys integration
Solve for future state including process organizational alignment

Automate & streamline our processes & operations

Reduce process complexity

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Strategic Alignment
Future processes are engineered: In alignment with business simplification & integration strategy To optimize key performance indicators (KPIs) & key process metrics To position Allscripts for growth and market leadership

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Methodology Context

Business Process Re-engineering

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Benefits
Serve as blueprint for business integration & automation Enable process engineering at all levels of the organization Minimize cost of rework (exponential increase without BPR) Enable cross-functional gap analysis & closure

Provide framework for downstream project deliverables (traceability)

Serve as on-boarding guide for new hires Serve as starting point for future BPR initiatives

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Traceability

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Future State Level 0

Allscripts

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Future State Level 1

Allscripts > Finance to Reporting

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

10

Future State Level 3

Allscripts > Finance to Reporting > Accounts Receivable

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

11

Assumptions
Achieve BPR goals with minimal impact on current

projects
Focus on release 4 end-state (no interim states for now) Future state flows will be reviewed by Operating Committee Feedback will be processed & incorporated when

applicable
Process ownership (swim lanes) will be clearly delineated
A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Concept to Item future state will be limited to level 1

12

BPR Organization
OC# Business Cycle BPR Lead Vince McCant Vince McCant Vince McCant Nexus Lead Chip Stephenson Chris Tyrrell Joseph Ilebode Chandra N Satinder Singh Mike Greer Hugo Balboa Paige Peterson Business Lead Dunn & Roberts Kemmy Lee TBD Amanda Mitchell / K. Lee Michael Scott/Alex Small Alexis Zecher Alexis Zecher Billy Moffat 1, 2 Market to Quote 1, 2 Order to Cash - Oracle 2 Concept to Item

2 3
3 3 4 4 4 5 5

Master Data Mngt. Hire to Retire

Procure to Invoice / AP Acquire to Retire Project to Profit - Oracle Project to Profit - Clarity Finance to Reporting LMS SABA e-Learning Case to Resolution

Vince McCant Fouad Guediri

Rob Littwin Rob Littwin Vince McCant Vince McCant Srini Mukkuvilli Vince McCant Rob Littwin

Jody Adams Hugo Balboa

Chuck Hillson Wayne Johnson

Tim ORoark Hugo Balboa/John King

Brom Stevens Bill Talbert

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

13

BPR Leads Responsibilities

Future State

Consolidate & standardize process flows

Collect leadership feedback & resolve gaps Close integration gaps across business cycles Current State Document current state processes Close gaps between current & future state

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

14

Operating Committee Reviews

OC Review #1
Offsite

Agenda Market to Quote Order to Cash Order to Cash (contd) Sales Contract Admin.; Subsidy; 3rd Party; Instance Management Case to Resolution Master Data Management Customer, Item, BOM, Configuration; Pricing; Design to Release Project to Profit Procure to Invoice, Accounts Payable (AP) Acquire to Retire Finance to Reporting Hire to Retire LMS SABA e-Learning

Dates 3/19 3/20 6/11 6/12

Status Done Done

#2
Onsite Atlanta

#3
Onsite Atlanta

7/16 7/18

Done

#4
Onsite Atlanta

8/20 8/22

Done

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

15

This section outlines the Business Process Reengineering standards & methods used across all Nexus programs

STANDARDS & METHODS

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

16

Standard Shapes (1)

Symbol
Subprocess

Name Subprocess

Description Shape indicates that this process has a further level of detail. Clicking on this shape should lead to a lower level process flow Shape indicates that this process step is performed entirely by the system, such as a Batch Job that runs in the background Shape indicates that this process is supported by an enterprise system. The user can enter data manually, but the data is stored & processed by the enterprise system Shape indicates that the enterprise system requires customization in order to support this process

Fully Automated Process

Fully Automated Process System Supported Process Customized Process

Systemsupported Process

Customized Process

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

17

Standard Shapes (2)

Symbol
Manual Process

Name Manual Process

Description Process is performed outside of an enterprise system, such as entering data on a paper form or local Excel file

Off-page Outgoing

Off-page Outgoing
Off-page Incoming External Flow

Shape is hyperlinked to an incoming connector into another process flow

Shape is hyperlinked to an outgoing connector from another process flow Information flow from/to a process outside of level 0 scope, such as external client process

Off-page Incoming

External Flow

Document

Document
Data

Paper document
Data container, such as spreadsheet, project plan, etc.
18

Data

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Modeling Approach
Proceed top-down starting from level 0

Maintain focus on business objectives, KPIs & Metrics

Identify all process actors (organizations and roles) Capture all relevant process inputs & outputs Identify cross-functional dependencies Differentiate manual from automated steps Specify underlying information systems & event IDs

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

19

Modeling Rules (1)

Use latest Nexus BPR Template (Workspace)

Always use shapes from Nexus BPR stencil (part of

template) Provide brief description of what the process does Minimize number of shapes per page (5 12) All levels (1,2,3) must connect back to level 0

Swim-lanes represent business functions or roles (not

systems)
A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Swim-lane names must be standardized

20

Modeling Rules (2)

Process co-ownership must be justified (pick a primary

owner)
Off-page outgoing connectors must be named after the destination process name Off-page incoming connectors must be named after the originating process name

Off-page connector pairs (outgoing / incoming) must

have the same color
A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.
21

BPR Stencil
Use these steps to import the standard BPR Visio

Stencil
Open Workspace (Nexus Document Management System) Go to folder /Documentation/Bus Process Reengineering/BPR

Methods
Download the NEXUS BPR Visio Stencil Save stencil to your local drive /Documents > My Documents > My Shapes Open the Visio file you want to work on From Shapes Window (left bar) > More Shapes > My Shapes
A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.
22

BPR Template New Flow

If creating a NEW Visio process flow
Make sure you have already imported the BPR Stencil (previous
page) Open Workspace (Nexus Document Management System)

Go to folder /Documentation/Bus Process Reengineering/BPR

Methods/ Download the Visio Template NEXUS BPR Template

Open the template, the file name will default to Drawing1.vsd

Rename Drawing1 to your chosen file name From Shapes Window (left bar) > More Shapes > My Shapes
A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.
23

Shape Attributes
Shape Attribute Function Description The FUNCTION attribute is the name of the swim-lane. When moving a shape to a swim-lane, the shapes Function attribute automatically inherits the name of the swim-lane. BPR Leads will ensure that swim-lane names are standardized across all NEXUS BPR flows Refers to the underlying information system platform that supports the process (Oracle, Salesforce.com, Clarity, LMS, etc.) Refers to the ID used in the Nexus High Level Design > Process Architecture deliverable Future State Process Model (MS-Word) Custom Reports, Interfaces, Conversions & system Extensions Not used yet
24

System

Event ID

RICE Status

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

Process Inputs & Outputs

Arrows indicate information/data flows between

processes
Arrows represent process inputs & outputs Inputs & Outputs are key to enterprise process INTEGRATION Key outputs must be rolled up to parent process

Off-page connectors carry information across functions

BPR Leads will help close all integration gaps
A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.
25

All BPR documentation will be stored and managed in the standard Nexus Document Management System (Workspace)

DOCUMENT MANAGEMENT

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

26

Document Control
All BPR documentation

will be managed via

Workspace BPR has a dedicated folder Access rights will be

assigned as needed

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

27

Folder Structure
Methods folder has

template, stencil, etc.

Future state folder is

structured by Business Cycle

Integrated models are stored

in Integration folders

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

28

Document Updates
BPR documentation will be updated periodically

Always use the latest Nexus BPR Visio Template

Always use the latest Nexus BPR Visio Stencil

Level 1 flows will be added/revised periodically

Executive presentations will be posted after each

offsite session

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

29

Forward questions / concerns / suggestions to:

Farid Guediri, Nexus Program, Operations Team farid.guediri@allscripts.com

QUESTIONS & ANSWERS

A Connected Community of Health | Copyright 2010 Allscripts Healthcare Solutions, Inc.

30