Applying Business Process Modeling Notation (BPMN) in Healthcare
BPMN 2.0 - Business Process Model and Notation Innovator for
1
Start Event End Event Intermediate Event Events Start Event Interrupting Boundary Event Connected Non-Interrupting Boundary Event Connected None Message Intermediate Event Caught Timer Interrupting Subprocess- Start Event Non-Interrupting Subprocess- Start Event Intermediate Event Thrown End Event Error Compensation Link Signal Conditional Cancel Terminate Escalation Caught Threw Collaboration: Describes the interaction between participants (in this example: customer, company and supplier). Process: Describes the flow of activities in an organization (in this example: quote creation). Lane: A lane is a sub-partition within a process and will extend the entire length of the pool (in this example: clerk and approver). Process and Collaboration Conditional Flow Sequence Flow Message Flow Default Flow Sequence Flow: Shows the flow in a pro- cess. The sequence flow cannot cross a pool boundary but can switch between lanes. Message Flow: Shows the flow of messages between two participants. It must always connect to separate pools. Default Flow: Flows through gateways if all other outgoing conditional flows are not true at runtime. Conditional Flow: Enables conditions to be defined without using gateways. Text annotation is shown as displayed in the example. dĞdžƚ ĂŶŶŽƚĂƟŽŶƐ ŵĂLJ ĐŽŶƚĂŝŶ ĂĚĚŝƟŽŶĂů ŝŶĨŽƌŵĂƟŽŶ Quote Request Quote Creation A task is an atomic activity within a process flow. It is used when the work in the process cannot be broken down to a finer level of detail. User Task: Is executed by a user with the assis- tance of a software application. Service Task: Is a task that uses some sort of service. Business Rule Task: Provides a mechanism for the process to provide input to a business rules engine. Is expected to be performed without the aid of any business process execution engine or any application. Activities Call Activity Global Task: Identifies a point in the process where a global task is used. Activation of a call activity transfers control to the called task. Call Activity Subprocess: Is an independent pro- cess that can be called from various processes. Event Subprocess: Is started by an external event. It doesn’t have any incoming or outgoing sequence flows. Subprocess: Is a graphical object within a process but it also can be “opened up” to show a lower-level process. Receive Task: Is a simple task that is desig- ned to wait for a message to arrive from an external participant. Send Task: Is a simple task that is designed to send a message to an external partici- pant. Transactions: A transaction is a subprocess that is supported by a special protocol that insures that the activity is completed or canceled. Script Task: Is executed by a business process engine. Ad-Hoc Subprocess: The sequence and number of performances for a set of activities is determined by the performers of the activities. Loop: The attributes of tasks and subprocesses will determine if they are repeated or performed once. Multi-Instance Parallel: Multiple, performed in parallel. Multi-Instance Sequential: Multiple, performed in sequence. Compensation: Undoes steps which have already been successfully completed. Markers for Tasks and Subprocesses www.mid.de © 2010 MID GmbH BPMN 2.0 - Business Process Model and Notation Gateways are used to control how the pro- cess flows through sequence flows as they converge and diverge within a process. Exclusive: Only one of the paths can be taken Inclusive: None, one or more paths can be taken Parallel: Creates parallel paths without checking any conditions Complex: Can be used to model complex synchronization behavior Gateways Exclusive (Either OR) Parallel Inclusive (OR/AND) Event-Based Event-Based - Exclusive Event-Based - Parallel Complex Inclusive: More than one path can be taken Event-Based: Represents a branching point in the process where the alternative paths that follow the gateway are based on events that occur. Innovator for Business Analysts Data Object Data Store Reference Data Output Data Input Provides information about what an activity requires for it to be performed and/or what it produces. If a process or subprocess which can be called requires information for it to be perfor- med, this information is modeled using a data input. The data output is the opposite of the data input. Events or return values which deliver a process are modeled using data outputs. Can be used as the source or target for a data association. Data Data Association Data associations move data between data objects and activities.
Transcript of BPMN 2.0 - Business Process Model and Notation Innovator for
Start Event
EndEvent
Intermediate Event
Events
Star
t Eve
nt
Inte
rrupt
ing
Boun
dary
Ev
ent C
onne
cted
Non
-Inte
rrupt
ing
Boun
dary
Even
t Con
nect
ed
None
Message
Inte
rmed
iate
Eve
ntC
augh
t
Timer
Inte
rrupt
ing
Subp
roce
ss-
Star
t Eve
nt
Non
-Inte
rrupt
ing
Subp
roce
ss-
Star
t Eve
nt
Inte
rmed
iate
Eve
ntTh
row
n
End
Even
t
Error
Compensation
Link
Signal
Conditional
Cancel
Terminate
Escalation
Caught Threw
Collaboration: Describes the interaction between participants (in this example: customer, company and supplier).
Process: Describes the flow of activities in an organization (in this example: quote creation).
Lane: A lane is a sub-partition within a process and will extend the entire length of the pool (in this example: clerk and approver).
Process and Collaboration
Conditional Flow
Sequence Flow Message Flow
Default Flow
Sequence Flow: Shows the flow in a pro-cess. The sequence flow cannot cross a pool boundary but can switch between lanes.
Message Flow: Shows the flow of messages between two participants. It must always connect to separate pools.
Default Flow: Flows through gateways if all other outgoing conditional flows are not true at runtime.
Conditional Flow: Enables conditions to be defined without using gateways.
Text annotation is shown as displayed in the example.
Quote Request
Quote Creation
A task is an atomic activity within a process flow. It is used when the work in the process cannot be broken down to a finer level of detail.
User Task: Is executed by a user with the assis-tance of a software application.
Service Task: Is a task that uses some sort of service.
Business Rule Task: Provides a mechanism for the process to provide input to a business rules engine.
Is expected to be performed without the aid of any business process execution engine or any application.
Activities
Call Activity Global Task: Identifies a point in the process where a global task is used. Activation of a call activity transfers control to the called task.
Call Activity Subprocess: Is an independent pro-cess that can be called from various processes.
Event Subprocess: Is started by an external event. It doesn’t have any incoming or outgoing sequence flows.
Subprocess: Is a graphical object within a process but it also can be “opened up” to show a lower-level process.
Receive Task: Is a simple task that is desig-ned to wait for a message to arrive from an external participant.
Send Task: Is a simple task that is designed to send a message to an external partici-pant.
Transactions: A transaction is a subprocess that is supported by a special protocol that insures that the activity is completed or canceled.
Script Task: Is executed by a business process engine.
Ad-Hoc Subprocess: The sequence and number of performances for a set of activities is determined by the performers of the activities.
Loop: The attributes of tasks and subprocesses will determine if they are repeated or performed once.
Multi-Instance Parallel: Multiple, performed in parallel.
Multi-Instance Sequential: Multiple, performed in sequence.
Compensation: Undoes steps which have already been successfully completed.
Markers for Tasks and Subprocesses
www.mid.de © 2010 MID GmbH
BPMN 2.0 - Business Process Model and Notation
Gateways are used to control how the pro-cess flows through sequence flows as they converge and diverge within a process.
Exclusive: Only one of the paths can be taken Inclusive: None, one or more paths can be takenParallel: Creates parallel paths without checking any conditionsComplex: Can be used to model complex synchronization behavior
Gateways
Exclusive (Either OR) Parallel
Inclusive (OR/AND)
Event-Based
Event-Based -Exclusive
Event-Based -Parallel
Complex
Inclusive: More than one path can be taken
Event-Based: Represents a branching point in the process where the alternative paths that follow the gateway are based on events that occur.
Innovator for Business Analysts
Data Object
Data Store Reference
Data Output
Data Input
Provides information about what an activity requires for it to be performed and/or what it produces.
If a process or subprocess which can be called requires information for it to be perfor-med, this information is modeled using a data input.
The data output is the opposite of the data input. Events or return values which deliver a process are modeled using data outputs.
Can be used as the source or target for a data association.
Data
Data Association
Data associations move data between data objects and activities.
