This wiki has undergone a migration to Confluence found Here
OO Behavioral Model
ContentsProject Objectives & IntroductionThe objective of the OO Dynamic Model project is to initially focus on common set of rules on how to deal with order management state transitions after the creation of an order. This will cover Lab, Rx, Rad, PT, Dietary, NRS, Procedures, etc. Subsequently we will focus on:
|
O&O Wiki Content
|
Approach
- This wiki page will be used to focus our discussions.
- We agreed to use the Publishing Database directly to maintain the necessary ballot components (Storyboards, Interactions, Trigger Events, Application Roles, State Transitions) and Visio for the Activity Diagrams. The Activity Diagrams form the core of the new Communication Process Model concept which has yet to be formally approved.
- Creating ballotable artifacts will be the main driver, while the decisions and notes from the minutes will be input into the documentation
- For the state machine we will start with the currently defined general state machine and then specialize the definitions and descriptions for Orders & Observations.
Michael van Campen and Garry Cruickshank will drive populating the Publishing Database based on our input, while Wendell Ocasio will put the initial Activity Diagrams into Visio based on our input.
Story Boards
Tom de Jong and Rob Hallowell will provide the 2 storyboards that will get us started.
Activity Diagrams
Interactions
Trigger Events
Application Roles
State Transition Definitions
Dynamic Model Minutes
To get access to just the Dynamic Model related minutes from past O&O meetings, please click here.