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 • 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. 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

11. Tooling Capabilities • Managed in HL7 Project Repository • Developers check in / check out Model artifacts • Available to all as Read-Only with downloadable viewer

12. 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

13. 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

14. Toolboxcustomized ProviderManagement ProviderEnrollment Business Process Model browser Tools Glossary

15. Process Template Provider Enrollment Provider Enrollment

16. Diagram Information Event Sub-process Decision Object (Provider) Activity

17. Sub-process NPI Registry Sub-process

18. HL7 V3 Profile Information Model Act

19. HL7 Tag values

20. HL7 MITA Wiki

21. MITA Project Space

22. MITA Repository