MITA Style Guide - PowerPoint PPT Presentation

Loading...

PPT – MITA Style Guide PowerPoint presentation | free to download - id: 4d238e-NzY5M



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

MITA Style Guide

Description:

MITA Style Guide Draft presentation What Is the MITA Information Architecture Purpose of the MITA Information Architecture Align information requirements with ... – PowerPoint PPT presentation

Number of Views:195
Avg rating:3.0/5.0
Slides: 32
Provided by: is6
Learn more at: http://mita.wikispaces.com
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: MITA Style Guide


1
MITA Style Guide
  • Draft presentation

2
What Is the MITA Information Architecture
Information Architecture
Business Architecture
Technical Architecture
3
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

4
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

5
MITA Style Guide
  • Organizes the Development of the MITA Information
    Architecture (IA)
  • Enforces MITA IA Development Methodology for
    consistency
  • Cookbook for Development and Use of the MITA IA
  • Enables MITA IA Project Management
  • MITA Governance Platform
  • MITA Glossary

6
Style Guide Functions
  • Explains in terms appropriate for different
    users
  • IA Goals and Objectives
  • MITA IA Modeling Methodology
  • Role of the Business Architecture (BA)
  • Relation of BA to IA and traceability to business
    requirements
  • Steps to developing and using IA
  • Types of models and their relationships
  • How to document modeling artifacts, e.g., how to
    describe a trigger event, an actor, a use case,
    or a WSDL
  • Versioning controls repurposing and evolution

7
MITA IA Tooling
  • MITA customized modeling tool
  • Exposes only MITA modeling features
  • Preloaded with MITA Business Architecture
  • Supports MITA Governance
  • Project Management Methodology
  • Modeling Methodology
  • Version Control
  • Repository
  • Collaboration Tools
  • Based on HL7 Development Framework

8
Enterprise Architect
  • 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

9
MITA IA Models
  • Support for MITA required Models
  • Business Models
  • Use Case
  • Business Process
  • Information Models
  • Conceptual Model
  • Data Model
  • Activity Diagram
  • Logical Model
  • Static Model
  • State Model
  • Interaction Model
  • Service Definition

10
Supports MITA Technical Architecture
  • Can capture Technical Capabilities
  • Security
  • Tolerance
  • Other
  • Can be used to generate code in a number of
    languages, including C, java, and xml

11
Toolboxcustomized
ProviderManagement
ProviderEnrollment
Business Process Model browser
Tools
Glossary
12
Process Template
Provider Enrollment
Provider Enrollment
13
Diagram Information
Event
Sub-process
Decision
Object (Provider)
Activity
14
Sub-process
NPI Registry
Sub-process
15
HL7 V3 Profile
Information Model
Act
16
HL7 Tag values
17
Tooling Capabilities
  • Managed in HL7 Project Repository
  • Developers check in / check out Model artifacts
  • Available to all as Read-Only with downloadable
    viewer
  • Supports Multiple Concurrent Projects
  • Supports Project Collaboration

18
MITA Repository Requirements
19
MITA Project Management Space
20
MITA Information Architecture Repository
21
MITA IA Versioning
  • Develop MITA Base Model
  • Adopt Normative Editions (versions of the base
    model that are frozen)
  • 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 Provider Enrollment
  • State versions may be harmonized
  • Governance may adopt for next MITA Normative
    Edition

22
Example of Repository Management
23
MITA Reporting Capabilities
  • Generates MITA Reports
  • Executive Level for Visioning and States MITA
    Self-Assessment Findings
  • Business Level for performing Self-Assessment,
    APD, RFP, JADs
  • Technical Level for DDI, IVV, Certification, and
    Standards Development

24
Example of a Technical Report
  • Conduct Clinical Trial
  • Type Activity
  • Status Proposed. Version 1.0. Phase 1.0.
  • Package Conduct Clinical Trial
  • Details Created on 9/27/2005 13950 PM.
    Modified on 3/22/2006 100933 AM. Author
    Fridsma
  • The study is planned by a principal investigator
    at a cancer center. The proposal is submitted
    by the cooperative group on behalf of the PI to
    NCI/CTEP, and once approved, the principal
    investigator will set up the operational aspects
    of conducting the study through the cooperative
    group that the cancer center is affiliated with.
    Once the operational aspects are completed, the
    cancer centers responsible for executing the
    study will begin to enroll patients and execute
    the study according to the protocol plan. At
    periodic intervals, cooperative groups, and PI
    will report back to the NCI the results of the
    study.

25
When to use the MITA Tool?
  • States must complete their self assessment
  • Visioning
  • As Is Assessment
  • To Be Selection
  • States select the MITA IA artifacts needed to
    develop their selected To Be Business
    Capabilities
  • The MITA Tool supports
  • Logical information requirements
  • Conformance criteria
  • Technical capabilities / enablers

26
Using the MITA Information Architecture
  • Locate the MITA Information Model within the MITA
    Repository
  • Find States selected To Be business process,
    e.g., Enroll Provider
  • Select the Enroll Provider conceptual and
    logical information artifacts that are applicable
    to meeting the business capability level
    attributes

27
Enroll Provider - Level 2 Capability
  • Example State decides to implement an online
    application form, which meets Level 2 capability
    attributes, then the artifacts selected could
    include
  • The Enroll Provider Conceptual Information Model
    for a standard MITA electronic application form
  • The Enroll Provider Activity Diagram for the
    Receive and Validate Provider Application, which
    would include Sub-processes for
  • Receiving, inbound transaction processing (store,
    translate, syntax/semantic checks, check for
    duplicates, and routing)
  • Validating application information by queries to
    the provider registry, NPPES, licensing and
    sanctioning entities, etc.

28
Enroll Provider - Level 3 Capability
  • If implementing Enroll Provider at Level 3 using
    services, then the artifacts could include all of
    the above and The logical information artifacts
    for
  • Messages and services to enable query/response
    and notification
  • Services for validate information by queries to
    the provider registry, NPPES, licensing and
    sanctioning entities, etc
  • These artifacts will include static, dynamic, and
    state models

29
State MITA Modeling Project
  • Check out the selected MITA Information Model
    artifacts from the MITA Repository
  • Create a state Enroll Provider Project within the
    MITA Project Management Tool
  • Upload the MITA Enroll Provider artifacts
  • Following the MITA IA Methodology, constrain or
    extend the MITA artifact to meet the state
    business requirements, e.g., select only a subset
    of the interactions for NPPES services, or add
    state specific provider taxonomy codes to the
    provider registry model
  • After adapting the MITA IA artifacts, the state
    would generate reports from the tool as needed

30
Upon Completion of State MITA Project
  • Submit proposed extensions or other gaps, e.g.,
    need for a new class, attribute, or code to MITA
    Governance to consider for adoption in a new
    Normative Edition of the MITA IA
  • E.g., if 2 states have different approaches, the
    MITA Governance Board may ask them to harmonize
    them and submit for balloting in the appropriate
    standards organization
  • If new codes are needed, the Board may facilitate
    the submission of the code request to the
    appropriate code maintenance organization

31
HL7 MITA Collaborative Wiki
About PowerShow.com