MITA Information Architecture

May 8, 2006

Purpose of the MITA InformationArchitecture

zAlign information requirements with Medicaid enterprise vision and direction zLower overall life-cycle costs zEnable interoperability and data

sharing

2

MITA Information Architecture Neutrality

zTechnology-, organization-, and location-neutral zStates have the flexibility for

their specific implementation

3

Information Architecture in the Context of the MITA Framework

MITA Framework

Business Architecture

State Self-Assessment Business Capability Matrix Business Process Model Maturity Model Concept of Operations

Data StandardsLogical Data Model

Conceptual Data Model

Data Management Strategy

Information Architecture Technical Architecture

TechnologyStandards

Application Architecture Technical Services

Technical Capability Matrix Business Services

Solution Sets

2629-06—012

4

Purpose of the Data ManagementStrategy

zDocument the processes, techniques, and products needed by a Medicaid enterprise to achieve optimal sharing of Medicaid enterprise information both within and with other entities

5

Scope of the MITA Data ManagementStrategy

zCaptures common Medicaid enterprise information at the logical level zLocation and organization neutral zFlexibility to allow State-specific data

and messages zPhysical data model, databases, and

data files are not be part of MITA

6

WSDL TCP IP ebXML

LDA

PSA

ML

BPE

L

Enabling Technologies

Data Landscape

Tools

CHI NHI

I

HL7

HIPAA

X12

EHR

CHCP

MIF

MO

FXM

L

Business Need

EvolvingBusiness

Value

MITA DMS

2629-06—078

Information Architecture

Hubs

Target Data ManagementEnvironment

Partners Hubs

DesignCenter Design

Data Definition Communities

MITA Data Management Approach Environment in Which Medicaid Operates

7

Benefits of Using the MITA DMS

zReduce custom solutions and promote interoperability and data sharing zProvide a common set of processes,

tools, and solutions for the information needs of Medicaid zAllow individual States to benefit

from the information assets of others 8

Parts of the MITA DMS

zData Governance zData Architecture zData Sharing Architecture

For data access mechanisms and services see MITA Technical Architecture. Physical characteristics of the mechanisms used for data sharing are the responsibility of the States and are not addressed by MITA.

9

Information Architecture in the Context of the MITA Framework

MITA Framework

Business Architecture

State Self-Assessment Business Capability Matrix Business Process Model Maturity Model Concept of Operations

Data StandardsLogical Data Model

Conceptual Data Model

Data Management Strategy

Information Architecture Technical Architecture

TechnologyStandards

Application Architecture Technical Services

Technical Capability Matrix Business Services

Solution Sets

2629-06—012

10

MITA Conceptual Data Model zDepicts the major business

information objects (subjects/entities) in their relationships to each other using business terminology. zBasis for development of a Logical

Data Model (LDM).

11

Scope of the MITA CDM

z Evolves in step with the maturing ofbusiness processes, e.g., adds clinicaldata for Maturity Level 4 z Contains all the data needed by the

defined process and services. z Includes all of the data and data

relationships common to States z Does not contain information regarding a

State’s unique processes and data

12

Member

Simple Conceptual Data Model

has

Address

13

Parts of the MITA CDM

zEntities zRelationships zDefinitions zDomains zRelated Standards zEntity-Relationship (E/R) Diagram

14

CDM Development Process z Develop a CDM based on the HL7

Reference Information Model (RIM) and asubset of early-adopter State Medicaidenterprise data models. zWork with States to improve and validate

the CDM z Through a MITA governance process TBD,

obtain all-State consensus zMaintain and update in repository (TBD)

15

Information Architecture in the Context of the MITA Framework

MITA Framework

Business Architecture

State Self-Assessment Business Capability Matrix Business Process Model Maturity Model Concept of Operations

Data StandardsLogical Data Model

Conceptual Data Model

Data Management Strategy

Information Architecture Technical Architecture

TechnologyStandards

Application Architecture Technical Services

Technical Capability Matrix Business Services

Solution Sets

2629-06—012

16

MITA Logical Data Model

zProvides guidance on design ofenterprise service interfaces zUsed to develop State’s physical

data model zBasis for true plug-and-play

capabilities of services andinteroperability among States

17

Scope of the MITA LDM

z Evolves as the processes and services aredefined in detail z Includes all data needed for the entire

Medicaid enterprise regardless of thelocation or systems z Compatible with the electronic health

records z Does not include State’s unique

processes and data z No physical data model

18

Simple Logical Data Model

Member Address

has Street CityState CountryZIP Code

ID SSN First Name Surname Salutation Phone Number

2629-06—037

19

Parts of the MITA LDM

zEntities zAttributes zRelationships zDefinitions zDomains zRelated Standards zEntity-Relationship (E/R) Diagram

20

Uses for the MITA LDM z As a reference document z As a requirements document z As a tool

21

Information Architecture in the Context of the MITA Framework

MITA Framework

Business Architecture

State Self-Assessment Business Capability Matrix Business Process Model Maturity Model Concept of Operations

Data StandardsLogical Data Model

Conceptual Data Model

Data Management Strategy

Information Architecture Technical Architecture

TechnologyStandards

Application Architecture Technical Services

Technical Capability Matrix Business Services

Solution Sets

2629-06—012

22

Purpose of MITA Data Standards

zEnable data sharing and interoperability of Medicaid enterprise information. zSupport both a syntactic and

semantic understanding of this information.

23

Scope of the MITA Data Standards

zMITA adopts DSMO datastandards zMITA facilitates development of

Medicaid-unique data standardsand submits them to a DSMO for adoption zMaintain data standards current

24

What Is a MITA Data Standard

z Represent agreements on the format anddescription of the shared data used by theMedicaid enterprise.

z Two major categories — � structure data standards � vocabulary data standards

z Key parts � data element names � definitions � data types � formatting rules

25

Information Architecture Components

Data Management Strategy

Provides foundation to

Uses

Uses

Data Standards

Conceptual DataModel

Logical DataModel

2629-06—119

26

MITA Business Process and Data Links

•Description of activities performed •Description of input data (Trigger), result data, and stored data used by the process

Trigger Result

Business Process

Business Logic

2629-06—107

27

State Medicaid Agency Use of the IA

z Participate in workgroups defining andmaintaining the MITA IA. z Extend the MITA data models to include their

State-unique information and datarequirements. z IA is used to determine what information is

required by the new processes. z Provides detailed data specifications for

defining the MITA services to implement thebusiness process. z IA details appear as requirements in State

RFPs. 28

CMS Use of the IA

zProvides leadership in establishing the MITA guidelines and promoting them among States. zThe MITA Framework CMS designates

the standards that Medicaid programs will have to meet in the future.

29

Vendor Use of the IA

zAs a reference in planning researchand development activities zAs a source for the syntax, semantics,

definitions, and relationships of allMedicaid data zAs specifications to align their solution

with the MITA Framework and interoperability with other States

30