Interoperability, A Federal Perspective

Transcription

1 Interoperability, A Federal Perspective Joseph Bodmer, PMP, MPM Director, Division of State and Tribal Systems, OCSE Director, ACF Interoperability Initiative, ACF ERICSA 52nd Annual Training Conference & Exposition April Hershey Lodge Hershey, Pennsylvania

2 What Is Interoperability? Interoperability Is the ability to make systems and organizations work together (inter-operate). Syntactic Interoperability If two or more systems are capable of communicating and exchanging data, they are exhibiting syntactic interoperability. Specified data formats, communication protocols and the like are fundamental. XML or SQL standards are among the tools of syntactic interoperability. Syntactical interoperability is a necessary condition for further interoperability. Semantic Interoperability Beyond the ability of two or more computer systems to exchange information, semantic interoperability is the ability to automatically interpret the information exchanged meaningfully and accurately in order to produce useful results as defined by the end users of both systems. To achieve semantic interoperability, both sides must refer to a common information exchange reference model.

3 Why Interoperability? Common vision, goals, metrics, measures, and outcomes across all stakeholders Reusability, modularity, compatibility, standards-based, common business rules, Client-centric service delivery model Cost savings through reuse, improved maintainability, reduced duplication of services, and improved program integrity

4 Interoperability Tools NIEM NHSIA National Information Exchange Model National Human Services Interoperability Architecture

5 National Information Exchange Model (NIEM) Impactful NIEM Legislation Child Welfare Public Law Child and Family Services Improvement and Innovation Act of 2011 TANF Public Law Middle Class Tax Relief and Job Creation Act of 2012 SNAP Public Law The Agriculture Act of 2014 Child Support Public Law Preventing Sex Trafficking and Strengthening Families Act of 2014

6 NIEM NIEM is not a software program, database, network, or computer system. NIEM is designed to facilitate the creation of automated enterprise-wide information exchanges which can be uniformly developed, centrally maintained, quickly identified and discovered, and efficiently reused. The result is more efficient information sharing between agencies and jurisdictions; more costeffective development and deployment of information systems; improved operations; better quality decision making as a result of more timely, accurate, and complete information. Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

7 How Does NIEM Work? Key Concepts The following key concepts are essential to understanding the purpose, architecture, processes, and other capabilities of NIEM Data Components. The fundamental building block of NIEM is the data component. Data components are the basic business data elements that represent real-world objects and concepts. Information exchanged between agencies can be broken down into individual components for example, information about people, places, material things, and events. Components that are frequently and uniformly used are specified in NIEM. They can then be reused by practitioners for information exchanges, regardless of the nature of their business or the operational context of their exchanges, provided they are semantically consistent. Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

8 How Does NIEM Work? Key Concepts Information Exchange Package Documentation. The information that is commonly or universally exchanged between participating domains can be organized into information exchange packages (IEPs) in the form of XML Schemas. An example of this collection of information is data associated with an arrest. The data includes not only personal identification data regarding the individual arrested but also information about the person's alleged offense, the location of the offense, the arresting officer, etc. The Information Exchange Package Documentation (IEPD), also contains data describing the structure, content, and other artifacts of the information exchange. An IEPD supports a specific set of business requirements in an operational setting. Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

9 How Does NIEM Work? Key Concepts NIEM Core. Data components within an information exchange that are universally shared and understood among all (or almost all) domains are identified as universal components (e.g., person, address, SSN, organization). To become a universal component, consensus by all domains is needed on the semantics and structure of the component. The set of NIEM Core components (a/k/a universal components) is stable and relatively small. Domains. For purposes of NIEM, a domain refers to a business enterprise broadly reflecting the agencies, units of government, operational functions, services, and information systems which are organized or affiliated to meet common objectives. NIEM domains are organized to facilitate governance, and each has some measure of persistence. Each domain traditionally includes a cohesive group of data stewards who are subject matter experts (SMEs), have some level of authority, and participate in harmonizing conflicts and resolving data component ambiguities. Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

10 How Does NIEM Work? Key Concepts Communities of Interest. Communities of interest (COIs) are collaborative groups of users who exchange information in pursuit of shared goals, interests, missions, or business processes, and who therefore must have a shared vocabulary for the information they exchange. COIs reuse data components and artifacts found in NIEM to document their information exchanges. One or more COIs can coordinate to develop new domain content as they identify gaps in the data components needed for documenting information exchanges. NIEM Conformance. There are NIEM conformance rules that serve as guidelines for agencies utilizing NIEM to implement their information sharing exchanges. Developers building inter-agency XML-based exchanges must comply and follow the associated NIEM implementation guidelines. Conformance is key to the ability of the COI to be able to reuse some or all of an existing IEPD and the data exchange it represents. Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

11 Does NIEM Have Real Products? Availability Completed IEPD s Public Assistance Reporting Information System (PARIS) IEPD National Youth in Transition Database (NYTD) IEPD In-Process IEPD s Child Welfare Data Exchange between the Child and Family Service Review (CFSR) Online Monitoring System (OMS) and Title IV-E Agency Case Management Systems Child Support/Child Welfare Data Sharing North Carolina Families Accessing Services through Technology (NC FAST) IEPD Tribal Case Initiation and Case Transfer (State CSE System to the Model Tribal System) Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

12 Where Do I Get More On NIEM? Human Services Domain at: [email protected] Joseph Bodmer, Steward [email protected] David Tabler, Deputy Steward [email protected] Domains Homeland Security Intelligence Justice Human Services Health Labor Defense Immigration Agriculture Biometrics CBRN Maritime International Trade

13 National Human Services Interoperability Architecture NHSIA The National Human Services Interoperability Architecture (NHSIA) is a framework to facilitate information sharing, improve service delivery, prevent fraud, and provide better outcomes for children and families. NHSIA also brings together pieces from other architecture models such as the Federal Enterprise Architecture (FEA) Defense s Architecture Framework (DoDAF), and of course the Medicaid Information Technology Architecture (MITA) 3.0. NHSIA consists of seven Viewpoints examining the enterprise architecture from different business and technology perspectives. NHSIA offers a foundation for common understanding, interoperability, standards, and reuse. Benefits Common Vocabulary Interoperability Data Exchange Standards Standard Data Structures Reusability Technical Framework Security-Focused Service-Oriented Enterprise Service Bus Enhanced Efficiencies Improved Effectiveness Proven, Real-World Design

14 National Human Services Interoperability Architecture NHSIA Provides a Framework and Roadmap To Achieve Common Goals As-Is NHSIA To-Be Results NHSIA Goals Unique business processes Common business processes Improved processes Fragmented information Standard information exchanges (NIEM) Accessible information Duplicate systems, infrastructure, & development Shared information technology (IT) services & infrastructure Improved efficiency and effectiveness Comprehensive performance management Fraud detection and prevention Improved decisions Better outcomes Limited performance information Improved Human Services Delivery

15 National Human Services Interoperability Architecture NHSIA Incorporates Lessons Learned and Best Practices From a Range of Activities NIEM MITA Montgomery County, MD ONC Health IT NHIN - Nationwide Health Information Network GFIPM Business Viewpoint Systems Viewpoint Infrastructure Viewpoint COTS Services & Environments Project Viewpoint VA MDM Information Viewpoint Overview Viewpoint ISE Information Sharing Environment Capability Viewpoint Montgomery County, PA Wisconsin s Access Program OK MOSAIC NYC Connect GRA Global Reference Architecture START Strategy to Apply Reusable Technology The NHSIA team analyzed existing initiatives and adapted key features to fit in the NHSIA framework.

16 National Human Services Interoperability Architecture NHSIA Provides a Framework for Shared Business Processes Eligibility Determination Common business processes support multiple human services programs. Intake and Enrollment Case Management Identity and Access Management Confidentiality and Privacy Agreement Provider Registry Build Once, Use Many Performance Management Child Support Financial Assistance Food & Nutrition Medicaid... and more! Benefits across states, counties,... Benefit across programs

17 National Human Services Interoperability Architecture NHSIA Benefits Shared Applications Integrated Eligibility Case Management Data Warehouse/Analytics Document Management Rules Engine/Infrastructure Identity Management Common Vocabulary Interoperability Data Exchange Standards Standard Data Structures Reusability Technical Framework Security-Focused Service-Oriented Enterprise Service Bus Enhanced Efficiencies Improved Effectiveness Real-World Design

18 Confidentiality Toolkit The Confidentiality Toolkit Covers Individual chapters addressing confidentiality and privacy through the lens of particular areas of service provision: Child Welfare (including Foster Care), Child Care, Temporary Assistance for Needy Families (TANF), Child Support, Low Income Home Energy Assistance Program (LIHEAP) Supplemental Nutrition Assistance Program (SNAP)

19 Confidentiality Toolkit The Confidentiality Toolkit Covers Each Chapter contains reviews of federal laws and regulations regarding: For each law, the Toolkit provides a basic, understandable description of the confidentiality issues. Highlights the law s specific language permitting information sharing.

20 Confidentiality Toolkit The Confidentiality Toolkit Covers 1. An appendix with matrices, by program, of applicable federal laws and regulations for easy reference; and, 2. A second appendix with memorandums of understanding addressing data sharing from: Kentucky, New York, Colorado, OCSE Montgomery County, MD

21 Interoperability, The Perfect Project Sean Pearson Deputy Cabinet Secretary New Mexico Human Services Department ERICSA 52nd Annual Training Conference & Exposition April Hershey Lodge Hershey, Pennsylvania

22 Background on New Mexico Population million Fifth largest state (urban, rural, and frontier areas) Other Programs, 14,000 Child Support, 63,000 SNAP, 481,000 Medicaid, 780,000 TANF, 35,800

23 Background on New Mexico Implemented an Integrated Eligibility System in 2014 Medicaid, TANF, SNAP, and Other Programs Apply for Benefits Online, Over the Phone, or In Person Paperless Offices with Electronic Case Files Modernized the Medicaid Program in 2014 Consolidated Managed Care Contracts Combined Physical, Behavioral, and Long Term Care Services Expanded Medicaid to Include Childless Adults to 138% FPL

24 Unintended Consequences Obligated Case Percentage Dropped by 5% Timeliness Dropped by 30% 50% Increase in Applications

25 Unintended Consequences

26 Unintended Consequences

27 Unintended Consequences

28 Our Vision HHS 2020 Citizen Centric Improve Outcomes Reduce, Reuse, Recycle Health and Human Services Enterprise

29 HHS 2020 Citizen Centric Consumer (Citizen/Provider) Single Access Layer Providing Consumer Focused Functions Account Creation Community Level Applications/Services Single HHS Consumer Portal Reporting Web Services Security WIC Document Management Medicaid Enrollment Child Support UI/UCB Eligibility Agency Applications NIEM standard based information exchange

30 HHS Citizen Centric

31 HHS 2020 Enterprise

32 Federal Guidance NHSIA MITA

33 A-87 Cost Allocation Exception Qualifying Services and Components Client Portals User Interfaces Master Client Index Business Rules Engine Enterprise Service Bus Data Warehouse Privacy and Security Controls Workflow Management Business Intelligence/Analytics Notices Electronic Document Management Telecommunications Infrastructure Business Process Redesign Interactive Voice Response Case Management Buy it once and leverage it across the enterprise.

34 Alternatives Analysis+

35 How Do We Get There?

36 CSES and MMIS Projects

37 Governance is Key Federal Partners (CMS & OCSE) Executive Steering Committee IV&V Executive Sponsor Executive Business Owners MAD Director Executive Technology Owner (ITD CIO) CSED Director PMO Project Director See next slide for PMO Organization

38 Shared Project Team

39 HHS 2020 Enterprise HHS 2020 Enterprise Architecture Applications Citizen Engagement Services Analytics Service Access Layer Enterprise Data Warehouse Service Components HHS 2020

40 Where Are We At? Planning Phase for Both Projects Approved PAPD from OCSE Approved IAPD from CMS Obtained CMS Approval on HHS2020 Enterprise Approach IAPD to OCSE Later This Year for HHS2020 Enterprise Approach HHS2020 Enterprise Architecture Completed NHSIA and MITA Assessments Are In Process Feasibility Study and Analyses Are In Process

41 Contact Information Sean Pearson Deputy Cabinet Secretary New Mexico Human Services Department