mita uml training n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
MITA UML Training PowerPoint Presentation
Download Presentation
MITA UML Training

Loading in 2 Seconds...

play fullscreen
1 / 85

MITA UML Training - PowerPoint PPT Presentation


  • 324 Views
  • Uploaded on

MITA UML Training. Leveraging best-practices, industry standards, and architecture principles to improve business performance, efficiency, and to reduce cost. 8:30 – 10:00 UML fundamentals What is a model? UML Notation UML Diagrams Model reports + UML vs. BPMN 10:15 – 12:00

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'MITA UML Training' - chambray


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
mita uml training

MITA UML Training

Leveraging best-practices, industry standards, and architecture principles to improve business performance, efficiency, and to reduce cost

mita uml training day 1 overview and deliverables
8:30 – 10:00

UML fundamentals

What is a model?

UML Notation

UML Diagrams

Model reports +

UML vs. BPMN

10:15 – 12:00

From MITA documents to Model

MITA process  UML model

Model driven architecture and design

Mapping MITA concepts to UML

Extending UML with Profiles

UML Project Deliverables

13:00 – 14:30

Tooling Overview

IBM Rational Software Architect/Modeler

Websphere Business Modeler

Rational Tools Summary

Free tools (hyperModel, HL7 MIF, HL7 UML Profile) +

14:45 – 16:00

SOA Revisited

Capability-based architecture

SOA Principles

SOA support for business process model

SOA Governance

MITA UML Training – Day 1Overview and Deliverables
what is modeling
What is modeling?
  • Capture the intricacies of real-world situations, to describe the characteristics of real-world objects, their relationships, and the way objects communicate
    • abstractions and concepts
    • essential characteristics of real-world objects
  • An abstraction is a mental process of taking a thing, material (mobile phone) or immaterial (electromagnetic wave), real (person) or abstract (his emotional state), pruning all details that are not relevant for a particular purpose, naming it, giving it a short description to be able to manipulate and work with the abstraction (as a result) issued from this complexity reduction process
unified modeling language uml models
Language to express abstractions of reality in a coherent way

Standardized language instead of ad-hoc language

Graphical language used to design software and web services

Related model elements and views

Standardized to improve communication

Unified Modeling Language (UML) Models
activity diagrams
Activity Diagrams

Describe workflows

Processes

Conditions

Failures

Information flow

Process flow

Timing

TriggerEvent

Control flow[condition]

Decision

Failures

Actions

Reused Process

Object flow[condition]

Result

Activity Diagrams
use case diagram
Identifies the various ways in which a user interacts with a system or other users

Actors, use cases, associations, inclusion

Enroll Provider Information relies on

Add

Update

Inquire

System

Actor

Actor

Business Use case

Infrastructure Use case

Use Case Diagram
state transitions with state machine diagrams
State is changed when a condition is met

Allowed states for a specific business object

Useful analysis device to define the behavior of business objects controlled by services

Transitions are triggers for other processes or operations

Initial state

Transition [condition]

Object’s state

Final state(no further changes are possible)

State Transitions with State Machine Diagrams
state transition diagram provider s application

Invalid request

New providerapplication

Validrequest

Approved request

State Transition Diagram: Provider’s Application
sequence diagram
Sequence Diagram

User role : Actor Type

Message/Request

System : Business Process

System : Service type

Return

Asynchronous Notification

collaboration diagram
Sequence of messages

Options and alternate flows

Two equivalent views

View of system behavior

Collaboration Diagram
class diagrams messages
To view information and operations

Represents types of information and associations between classes of business objects

Edges do not represent data or control flowing

Arrows show the direction of navigation

This is used to generate XML from a model

Class Diagrams - Messages

Class of business object

Property/Attribute

Composition

Association

(direction)

Cardinality/Multiplicity

component diagrams behavior process
Interfaces show how the capabilities of a systems are expressed formally

Operation

Parameter/messages

Return types/response

Component Diagrams: Behavior/Process

Interface

Operation (parameter: parameter type…):Response type

Stereotype

Operation (parameter: parameter type…

model report
Model Report

Model Report, Presentation

UML Model

WSDL, XSD

wsdl and bpel
WSDL and BPEL
  • UML can be used to design web services
    • UML-to-WSDL
  • UML Profiles may be used to extend the language to support BPMN
    • UML can be extended
  • Where does BPEL fit in?
    • BPEL allows you to write programs that use web services, and to write programs that are web services
    • Modelling applications with BPMN
      • workflow
      • service orchestration
    • Transforming BPMN into BPEL
      • flow
      • data
      • services
    • There are some known issues BPMN mapping BPMN to BPEL(1)
  • UML can be extended with profiles to map and generate BPEL
    • BPEL4WS
representing business processes in uml
Representing Business Processes in UML
  • UML 2 Activity diagram includes all the elements needed to model business processes with two exceptions:
    • Goals
    • Measures
  • UML profiles are used to extend the language using profiles
    • <<stereotypes>>
    • Actions, Control, Faults
mita in the context of soa
MITA in the context of SOA

Information Architecture

Business Architecture

Technical Architecture

purpose of the mita information architecture
Purpose of the MITA Information Architecture
  • Align information requirements with Medicaid enterprise vision and direction
  • Improve system effectiveness
  • Facilitate growth and innovation
  • Lower overall life-cycle costs
  • Enable interoperability and data sharing
mita information architecture neutrality
MITA Information Architecture Neutrality

Technology-, organization-, and location-neutral

States have the flexibility for their specific implementation

Mechanisms to extend MITA to accommodate individual State needs

MITA can be extended to support other programs, e.g., behavioral health and waiver programs

style guide
Style Guide
  • Organizes the Development of the MITA Information Architecture (IA)
  • Enforces MITA IA Development Methodology for consistency
  • Enables MITA IA Project Management
  • MITA Governance Platform
  • MITA Glossary
  • Automates the development of future MITA framework extensions
mita technical architecture
MITA Technical Architecture
  • Can capture Technical Capabilities
    • Security
    • Tolerance
  • Can be used to generate code in a number of languages, including C#, java, and XML
approach for service design
Approach for Service Design
  • Analyze business process
  • Identify system boundaries
  • Define business triggers for each operation
  • Identify systems and refine integration use cases for specific interactions
  • Refine HL7 information models
    • Message payloads
    • Terminology
  • Generate computable Service Descriptions (WSDL, XSD)
uml project objectives
UML Project Objectives
  • Applying the MITA business processes
    • Maturity level 3
  • Using Standards (HL7, UML) for information modeling
    • Model-driven architecture
      • Manage the model and generate both documents and implementation artifacts from the single model
  • Developing implementable specifications
    • WSDL
    • XSD
  • Common information and terminology
    • HL7 Version 3 (www.hl7.org)
    • Reference Information Model
using mita for interoperability
Using MITA for interoperability
  • To fulfill the business process several systems must interact
    • Invoke behavior
      • Request/response
      • Query/response
    • Exchange information
  • Using a common specification
    • Semantic interoperability
    • Common terminology
    • Common structure
  • The following slides are views of a single UML model
    • Class diagrams (information, interactions, structure)
    • Sequence diagrams (behavior, service use scenarios)
evolution of mita from doc

Narrative business process

PM Enroll Provider

Tier 3: Enroll Provider

Item

Details

Links

Description

Trigger Event

Result

Business Process Steps

Shared Data

Predecessor

Successor

Constraints

Failures

Performance Measures

Word/PDF document

Evolution of MITA from doc …
to a complete model

Narrative business process

PM Enroll Provider

Tier 3: Enroll Provider

Item

Details

Links

Description

Trigger Event

Result

Business Process Steps

Shared Data

Predecessor

Successor

Constraints

Failures

Performance Measures

Word/PDF document

… to a complete model
using uml tools

Toolboxcustomized

ProviderManagement

ProviderEnrollment

Business

Process

Model

browser

Tools

Glossary

… using UML tools
how to
How to…
  • Use the narrative to populate UML business process
    • Business Process
    • Details
    • Dependencies
  • Import HL7 Version 3.0 information models
    • shared data/information detail
    • terminology
  • Use UML to document the system interfaces
    • Common interfaces for interoperability
    • Services based on MITA
    • By implementing these services the state is aligned with MITA
mita business process
MITA Business Process

Enroll Provider

slide35

Narrative

PM Enroll Provider

Tier 3: Enroll Provider

Item

Details

Links

Description

Trigger Event

Result

Business Process Steps

Shared Data

Predecessor

Successor

Constraints

Failures

Performance Measures

Evolution … Refinement

slide38

Inquire Provider

CheckRules

Validation

ReceiveRequest

Add Provider

hl7 standard message structure
HL7 Standard Message Structure
  • Imported from HL7 approved standards
hl7 data types
Re-usable

Allows us to avoid platform compatibility issues

HL7 Data Types

Address

Identifier

hl7 terminology

Code Sets

HL7 Terminology

Validation of messages

value sets vocabulary
Value Sets/Vocabulary

Coded concept

Value Set

Value Set

benefits revisited
Benefits… revisited
  • Common specification
    • Maximize the reuse of business process and services (Enterprise Business Capability in the context of Service Oriented Architecture)
  • Interoperability between components developed by different projects or vendors
    • “plug-and-play” interoperability
    • TAC Enroll Provider demonstration
summary of project artifacts
Summary of Project Artifacts
  • Business Process (Activity diagram)
    • MITA “to be”
    • Minnesota specific business rules
    • Business Triggers, system boundaries
  • Information Model (Class Diagram
    • HL7-based, standardized vocabulary
  • Interactions ( Sequence Diagram)
    • Operations expose business capabilities
  • Service Specifications
    • Ports, interfaces, business rules
  • Used documentation and runtime artifacts
    • WSDL
    • XSD
uml modeling tools
UML Modeling Tools
  • Multi-purpose, standard-based tool
    • OMG (Object Management Group) UML
    • Business Process Analysis  Software Engineering
  • Can be customized for MITA requirements
  • License may be free for MITA development – under negotiations
  • Can import and export to other UML tools
  • Can link to Common Terminology Services to bind code sets to MITA vocabulary
  • Can generate HL7 artifacts
  • Focus on IBM’s tools selected by the state
ibm s tools to support business process integration

Run-time Statistics

Business Measures

Rational RequisitePro

WebSphere Business Modeler

Rational Portfolio

Manager

WebSphere Integration

Developer

Create, Simulate & Analyze As-Is Business Model

Choreograph services using BPEL, WSDL, etc.

Create Observation Model with KPIs & export to Monitor

Understand Risk, Project Costs, and ROI

Integration Developer

Create, Simulate, Analyze and Optimize To-Be Business Model

CIO

Assemble Solution

(BPEL, Human Task Manager, Business Rules, etc)

Configure Human Task Manager (including Ad-Hoc) & Client

Identify and Manage Projects and Resources

BPEL

WSDL

Create FinancialReports & ROIEstimates

BusinessAnalyst

Project

Manager

WSDL

EAR

UML

Runtime

  • WebSphere Process Server
  • WebSphere Portal
  • WebSphere Business Monitor

Rational Functional & Performance Tester

Rational Data

Architect (4Q05)

Test

Create & Manage SystemRequirements

Tester

Model

Relational

Database

Schemas

Deploy/Run

Develop

Portlets

(App UI and Monitor)

Trace Requirements & Create System Use Case Realizations

Model & Implement Services, & expose as Web Services

WSDL

EAR

Business

Operations

Analyst

RDB Mapping

Monitor

Rational

Software

Architect

Data

Architect

DBA

DBA

Java

Developer

Portal

Developer

Architect

IBM Rational Team Unifying Platform

IBM’s Tools to support Business Process Integration
integration with ibm rational software architect rsa
Integration with IBM Rational Software Architect (RSA):

In Rational Software Architect, use the business model from WebSphere Business Modeleras a UML2 Business Contract specification

Drag-and-drop modeling artifacts to create UML analysis diagrams

business contract specification from websphere business modeler to rational software architect rsa

process

business item

role

<<Interface>>

<<Business Worker>>

Eligibility System

<<BusinessActor>>

Eligibility System

<<BusinessUseCase>>

Account Verification

<<BusinessEntity>>

Customer Application

Business Contract Specification: - From WebSphere Business Modeler to Rational Software Architect (RSA)

Account Verification Process

ibm rational requisite pro integration with
IBM Rational Requisite Pro Integration with :
  • Create requirements in the Requirement Explorer
integration with ibm rational requisite pro cont d
Integration with IBM Rational Requisite Pro – cont'd
  • Open Requirements View in WBM and Link local WBM element with requirement
    • Link a local task to the requirement
team support integration with ibm rational clearcase
Team Support: Integration with IBM Rational ClearCase:
  • Multi-User support for sharing projects/files via a repository (e.g., ClearCase)
  • Comparison view showing differences between two versions a same process
  • Audit trail report showing changes done on an element over multiple versions (history)
  • View a list of all revisions of an element in the repository features such as Share, Update, Commit, Synchronization
ibm tools supporting service oriented architecture

Service

Service

Service

Service 2

Generate Decline

Service

Service

Service

Service

Service

Service

Service

IBM Tools supporting Service Oriented Architecture

Enabling complete life cycle of business process

WebSphere Integration Developer

Constructs for dynamic and adaptive business processes based on an integration platform

Clean hand-off from IT with Business Models, Metrics

WebSphere Process Server

WebSphere Business Modeler

Enterprise Service Bus

WebSphere Business Monitor

Real time management of business processes

Feedback for continuous improvement

mita ia versioning rules
MITA IA Versioning Rules
  • Adopt Normative Editions of the MITA Framework
  • Create state-specific Project Versions
    • State A and State B can both check out MITA base model for Provider Enrollment
    • Each constrains or proposes extensions to the base process (e.g. Enroll Provider extended for a certain state)
    • State versions may be harmonized
    • Governance  Change Control and Configuration Management
mita reporting capabilities
MITA Reporting Capabilities
  • Generates MITA Reports
    • Executive Level for Visioning and State’s MITA Self-Assessment Findings
    • Business Level for performing Self-Assessment, APD, RFP, & JADs
    • Technical Level for DDI, IV&V, Certification, and Standards Development
model driven approach
Model-driven Approach
  • As requirements change, we change the UML model
    • re-generate user documentation
    • re-generated WSDL
  • Diagrams provide views on the model
    • an element change is automatically reflected in all the diagram that use the element
benefits of using hl7
Benefits of Using HL7
  • Leading SDO in healthcare domain in classification of data attributes and semantic interoperability
  • Provides ‘sandbox’ and tools for developing strawman LIM
  • Most evolved and widely used models in healthcare industry
  • Aligns with national healthcare initiatives
benefits of using hl71
Benefits of Using HL7
  • Includes both clinical and administrative models
  • X12N and HL7 harmonization under way
  • Learn from and share with other government and industry healthcare information specialists
  • Used by Veterans Administration, CDC, DOD, SAMHSA to develop their models
benefits of using hl72
Benefits of Using HL7
  • Do not reinvent the wheel – begin with robust model
  • Process for promoting domain-specific vocabulary
  • Methodology and tools for developing messages and services
  • Open participation
  • HL7 is home to the Electronic Health Record Functional Model
tooling capabilities
Tooling Capabilities
  • Modeling
    • Includes WSDL and XSD generation
  • Managed in HL7 Project Repository
    • Configuration management portal
    • Developers check in / check out Model artifacts
    • Available to all as Read-Only with downloadable viewer
  • Wiki for brainstorming, co-editing documentations, collaboration
mita collaboration wiki
Collaborative documentation

Brain-storming

Meeting Minutes

http://mita.wikispaces.com/

MITA Collaboration Wiki
eclipse based tools
Eclipse-based tools
  • hyperModel 3.0
    • Generates XML schema from the visible content of a diagram
    • Provides XSD generation options to ensure optimal XML payloads
  • Subversion client plugin
    • Connects to version control server (HL7)
    • Version control integrated
  • SOA Tools Platform project:
    • http://eclipse.org/stp/bpmn
    • http://bpms.intalio.com
service oriented architecture soa
Service Oriented Architecture (SOA)
  • The enterprise is a market place of capabilities
    • Capabilities are materialized as services
    • Systems provide capabilities that other systems need in order to support enterprise processes
      • Clinical order fulfillment, pharmacy dispense, order/perform/report procedure
  • Architectural principles
    • Reuse, encapsulation, componentization
slide74

Clinician

Administrator

Register Patient

Physical Exam

Identity Verification

Order Lab Tests

Eligibility Verification

Order Medication

Billing

Review Results

Schedule Follow-up

Discharge Note

End Encounter

Emergency Encounter

Retail Pharmacy

Rx Dispensing

Workflow

Optional flow

slide75

Business Objects

Encounter

Appointment

Eligibility Criteria

Lab Result

Rx Dispense Event

Identifiers

Lab Order

Person

Clinical Document

Billing Item

Rx Order

slide76

Capabilities

Eligibility Verification

Diet Ordering

Encounter Management

Schedule visit or procedure

Lab Ordering

Lab Results

Report Management

Rx Dispensing

Billing

Rx Ordering

Identity Management

Identity Lookup

slide77

Systems and their boundaries

Encounter Management

Schedule visit or procedure

Lab Ordering

Lab Results

Report Management

Rx Dispensing

Billing

Rx Ordering

Identity Lookup

Identity Management

Eligibility Verification

slide78

Retail Pharmacy

Administrator

Clinician

Register Patient

Physical Exam

Identity Verification

Emergency Encounter

Order Lab Tests

Eligibility Verification

Order Medication

Billing

Review Results

Rx Dispensing

Schedule Follow-up

Discharge Note

End Encounter

Systems support business

Emergency Encounter

Place Medication Order

Business Process

Prescription

ManagementInterface

Order Medication

ERSystem

Pharmacy System

Collaboration

Use Case

what is a service
What is a Service?
  • Manages the business information on behalf of the other systems in the enterprise
    • Today each interfaces reflects how a system uses the data
      • If there are multiple consumers of the data, each of them may have a different “trading partner” agreement with the producer of that data
    • System requires “trading partner” agreements with other systems
      • E.g. Lab and Retail Pharmacy have separate agreements with the Eligibility system
  • A mechanism to provide access to one or more capabilities
    • As long as the capabilities are available it does not matter what system provides them
  • A service is accessed by means of a service interface
  • Its implementation is typically hidden from the service consumer except fortheinformation and behavioral models exposed through the service interface
slide80

Appointment Management

Schedule

Service

Eligibility Lookup

ESR

Service

Appointment

Consult

Appointment Lookup

Eligibility

Enrollment

Enrollment Lookup

Laboratory

Service

Order Management

Identity Management

Person

Service

Order

Demographics Management

Identifiers

Result

Result Lookup

Person

Person Lookup

APPLICATION FRONT-END

Legacy

Service Registry

it governance and soa governance
IT Governance and SOA Governance
  • IT governance required to track information, capabilities, and the specifics of service implementation.
    • Portfolio management of enterprise systems including enterprise wide coordination of project and contract management
    • Enterprise-wide Information Architecture and Integration Solutions (ESB)
    • Change and configuration control, Development Lifecycle Process, IV&V
  • SOA governance to manage the evolution service contracts, service capabilities (e.g. registries and repositories)
soa governance

Service Coordination and Orchestration

Active Certified Registry Services

External Network or ESB

Gateway to External Services

Enterprise Service Bus

Business Object

Capability

Message Payload

Portal to Web Users such as Providers

Service

Repositories of Authenticated Information

HIVE Support above line

Data Warehouse

Legacy Applications (MMIS, MAXIS, SSIS, MinnesotaCare)

Within Network or Application

SOA Compliant Applications (e.g. SMI)

Within DHS SOA

SOA Governance
how we collaborate
How we collaborate…
  • MN Point-of-contact staff
    • Business analyst
    • Project Manager
  • Peer reviews of artifacts
    • Walkthrough of artifact with the reviewers
    • Peer Review Period
      • Comments questions, minor, major
    • Peer Review Comment Resolutions
      • Preliminary dispositions: accepted, accepted with mod, rejected, clarification required
    • Final comment resolution
      • Conference calls
references
References
  • Chun Ouyang, Wil M.P. van der Aalst, Marlon Dumas, and Arthur H.M. ter Hofstede, Translating BPMN to BPEL?
    • http://is.tm.tue.nl/staff/wvdaalst/BPMcenter/reports/2006/BPM-06-02.pdf