Cross Initiative – S&I Simplification – “Core” Values Introduction Use Cases resolve to standardized Core Components in the S&I Simplification Core Matrix. This permits: –Drilling down to Event/Action and Data Concepts and their representations –Re-Use of Components Components can be compared across Use Cases –New Use Cases can borrow Components from existing Use Cases –Existing Use Cases can harmonize their Components, if desired 4 September 2012 (b)DRAFT - S&I Simplification - "Core" Values1

Cross Initiative – S&I Simplification – “Core” Values Core Matrix Compiles and Distills Components from All S&I Initiatives –For easy reference, organization, comparison –11 Use Cases with 30 Multi-Step Scenarios –Initiatives: TOC, LCC, LRI, LOI, PD, esMD, QH, DS4P, PHRI Conveys Uniform and Integrated Patterns of: –Patient Flow – with Patient as Actor –Provider (Work/Process) Flow – with Provider as Actor –Information Flow – including System as an Actor Shows: –Event Steps with Actions taken – by Actors in Roles – to support individual health and provide healthcare –Health record entries resulting from Actions taken Shows Patterns of Repetition/Re-Use –Both Current and Potential 4 September 2012 (b)DRAFT - S&I Simplification - "Core" Values2

4 September 2012 (b)DRAFT - S&I Simplification - "Core" Values3 S&I Initiatives S&I Simplification + AHRQ S&I Core, SDOs, MDHT, Others Implementers End Users Specify/Assert… Compile/Organize/ Curate… Make Implementable… Assemble/Actu alize… Use/A ct… Use Case Requirements In Base Use Case: In Core Matrix then USHIK Repository: As Components and Building Blocks Tailoring for local use: Actors, Roles, Steps/Flow… Utilizing Automated Implementation Tool (future) WHO – Actors, Roles Individuals/Organizations/Systems Actors, Roles WHY – Requirements Incl. Assumptions, Pre/Post Conds Common Requirements Fulfilling Applicable Requirements WHAT/HOW – Process – Scenarios Stepwise Events, Actions Common Events, Actions Software “Services” Components for Security, Transport… Applicable Events, Actions Software Components WHAT – Information – Data Objects/Elements Scenario Inputs/Outputs Common Data Objects/Elements [w/CEDD] Data Components : Messages, Documents, Content, Structure, Vocabulary, Value Sets Applicable Data Objects/Elements Data Components UC Harm Standards, Implementation Guides Following Applicable Standards, Implementation Guides Input/Feedback Guidance and Solutions for Industry

Cross Initiative – S&I Simplification – “Core” Values Collaboration Accomplishments 4 September 2012 (b)DRAFT - S&I Simplification - "Core" Values4 Key Objectives = Coordinate, Leverage, Re-use Cross S&I Initiativesw/AHRQw/NIST w/HL7 EHR Interop WG, DOD MHS Found existing Re-Use instances Identified Core Candidates – for Re-Use Restated requirements to make fulfillment explicit: who, when Propagated Components among Initiatives, as examples: Identity, consent/permissions, access, data/record management and exchange, query, audit, signature… Populated (ISO based) AHRQ-USHIK Repository with Artifacts from S&I Initiatives and Core Matrix Explored Cross Industry Examples of Use Case Development Approaches and Tooling Linked Actions to functions of EHR/PHR System Functional Models (ISO/HL , 16527) Explored Simplification constructs in emerging HL7 EHR Functional and Information Model Explored Requirements for Use Case Development Toolkit XXX Explored Drill Down to Computable/Implementable Components for Data, Actions XXX