McKenzie - IM Rev

Military Health SystemOffice of the Chief Information OfficerIntegrated Requirements-Design Overview : 

Military Health SystemOffice of the Chief Information OfficerIntegrated Requirements-Design Overview Data Quality Course August 12, 2008 Deputy Director, Integrated Requirements-Design

Purpose : 

2 Purpose Data Quality Course attendees will gain familiarity with: The MHS Integrated Requirements-Design (IRD) Process The MHS Concept of One The IRD Process and Data Quality The IRD Organization MHS IM/IT Governance MHS Related Internet Sites

Integrated Requirements-DesignWhat Problem Are We Solving : 

3 Integrated Requirements-DesignWhat Problem Are We Solving Improve alignment – ability to deliver information systems that Support the business objectives of MHS Leadership and Stakeholders Deliver the value MHS Leadership seeks from their IT investments Improve interoperability – the ability of MHS information systems to Work together as one seamless MHS solution Share information with MHS partners Improve agility – the ability to deliver information systems More quickly At a lower cost Alignment, interoperability and agility are characteristics that lead to improved Cost Schedule Time to market Performance Quality

Integrated Requirements-DesignImproves Alignment, Interoperability & Agility : 

4 Integrated Requirements-DesignImproves Alignment, Interoperability & Agility War Peace Disaster Clinical Decision Support Business Data Software Hardware Functional Systems MHS Vision – Concept of One One MHS One MHS requirement Satisfied by one solution Master Planning IM/IT Strategic Plan MHS Transformation Plan Future State Architecture Governance Individual Projects Direct Fund Monitor MHS IM/IT Initiatives Alignment Individual Projects Are Led By Information Managers Reporting to Governance Integrated Requirements-Design Execute Programs According to Convergence and Quality Plan Program Execution Interoperability and Agility IRD Creates Minimum Essential Information to Ensure Convergence and Quality Alignment Alignment Service Orientation

Important Concepts – Mindset Changes : 

5 Important Concepts – Mindset Changes MHS concept of one - There is one MHS with one set of MHS enterprise requirements which are satisfied by one MHS enterprise solution. This solution is acquired/built as multiple components. Business processes and IT systems are intrinsically related Requirements discussions must include people who understand the technical capabilities available to satisfy the requirements Design discussions must include people who understand the business needs Requirement design discussions are documented using enterprise architecture methodologies Developed to represent the complexities found in the MHS in an unambiguous way Developed to ensure enterprise design integrity Government reclaims it’s responsibility to determine the future of the MHS Government as integrator Government furnished design specifications Transparency - Maintain broad-based (technical and business), external and internal visibility and review throughout the process Reduce the size of functional/system entities that move through the lifecycle

Slide 6: 

6 Perceived Functional Needs, Gaps and Technical Opportunities Develop, Test, Implement, Deploy & Sustain Define Needs, Gaps & Technical Opportunities 1.1 Create Initial Requirements -Design Alternatives 1.2 Refine Selected Requirements -Design Package 1.4 ID Needs to Work On Make Investment Decision 1.3 Make Execution Decision 1.5 Triage Phase Pre-Investment Phase Pre-Execution Phase Execution Phase Receive, document, analyze and prioritize all of the perceived needs, gaps and technical opportunities throughout the MHS and decide which ones to analyze in depth for an investment decision Analyze requirements and associated design alternatives (requirements-design packages) and document MHS leadership investment decisions Complete design specifications for selected requirements-design packages and verify MHS leadership desire to move to execution (acquisition) Acquisition Integrated Requirements-Design Process

Integrated Requirements-Design ProcessConceptual Flow : 

7 Integrated Requirements-Design ProcessConceptual Flow Establish Core Team IM Lead1 Decision to work on a need or Investment Decision Create/ Refine Overarching Description Arrange For SME Participation Create IRD Project Plan Review Relevant Existing Capabilities Create Strawman Artifacts Develop Requirements-Design Content Information Management Lead1 Investment Decision or Execution Decision Acquisition Inform Governance Decision with process results - Concept of Operations (CONOPS)2 Overarching Description Behavioral Description Structural Descriptions Specification Implementation Deployment Business Case Recommendation Cost Analysis Alternatives/Options Shall Statements Use best practices to accomplish this step DASD sponsored SME workgroups Pilots Prototyping Joint (SMEs and technologists) development Technology demonstrations Integrated research teams New approaches not thought of yet Notes: The IRD core teams and the process to develop the requirements-design content are lead by Information Managers who work for the MHS functional owners (DASDs, Deputy Director TRICARE & CIO) 2. The output of the IRD process is a requirements-design package or CONOPS which contains all of the information necessary to guide and constrain system development or COTS purchase

Integrated Requirements-DesignFacilitates Data Quality : 

8 Integrated Requirements-DesignFacilitates Data Quality MHS Requirements-Design – identifies, and obtains agreement on specific standards and terminologies Data Standardization - at the structure, code set, input, and interchange level Data Management Plans – for all standard message transactions, data sets, code & value sets exchanged by more the one system MHS Contract Language – enforces usage of Data Standards MHS Data Standards Configuration Management Board – oversees data issues and facilitates solutions IT Data Quality IPT - EIDS

Slide 9: 

9 IRD Organization

Military Health System Governance (draft) : 

10 Military Health System Governance (draft) Senior Military Medical Advisory Council (SMMAC) *CIO Integrating Council would need to be established DASD Arbitration Group (PMOC) TFWG BPMB CPMB IPWG RMSC Integrated Requirements-Design Portfolio Management Joint Medical Information Systems – Program Executive Officer and Program Managers

Points of Contact : 

11 Points of Contact Information Managers supporting the DASD, Health Budgets & Financial Policy IRD Data Standards Lead Chief of Integration Chair of Data Standards Configuration Management Board

Related Internet Sites : 

12 Related Internet Sites MHS Enterprise Architecture: Apply for password https://xnet.tricare.osd.mil DoD Metadata Repository and Clearinghouse: https://metadata.dod.mil/mdr/homepage/htm Unified Biostatistical Utility (UBU): http://www.tricare.mil/ocfo/bea/ubu/index.cfm Uniform Business Office (UBO): http://www.tricare.mil/ocfo/mcfs/ubo/index.cfm DoD Business Transformation Agency: http://www.defenselink.mil/dbt/ TRICARE Health Insurance Portability & Accountability Act (HIPAA): http://www.tricare.mil/hipaa/

Backup? : 

Backup?

Slide 14: 

14 MHS IM/IT Repository Master Plan View IM/IT Strategic Plan Future State Vision Enterprise Transformation Plan Future State Architectural Analysis External Architectures and Stakeholders Business Mission Area Functional Analysis IRD Prioritization IRD Process IM/IT Strategic Planning Enterprise Transformation Planning Review Validation Approval Collect Submissions & Validate Requirements Review Validation Approval Gap Analysis Gap = Master Plan - (Current State + Completed RD Sets + Planned RD Sets) Enterprise Architecture View Current State (As Needed) Future State Vision Transition Plan Model & Text Based Information Supports Multiple Purposes & Views War Fighter and Integrated Requirements-Design Cycle Master Planning Cycle MHS IM/IT Planning and Execution Cycle