S&I Simplification Use Case Authoring Tool (UCAT) Introduction In collaboration with NIST and AHRQ 25 March 2013.

Slides:



Advertisements
Similar presentations
LRI Validation Suite Meeting August 16, Agenda Review of LRI Validation Suite Charter/Overview Acquiring test data update Review of proposed test.
Advertisements

S&I Framework Testing HL7 V2 Lab Results Interface and RI Pilot Robert Snelick National Institute of Standards and Technology June 23 rd, 2011 Contact:
US Office of National Coordinator (ONC) Standards and Interoperability (S&I) Framework Cross Initiative – S&I Simplification Work Group Simplification.
HP Quality Center Overview.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Security Controls – What Works
ONC Standards and Interoperability Framework Use Case Simplification Key Steps Forward 3 November 2011.
ONC Standards and Interoperability Framework Use Case Simplification Key Steps Forward 27 October 2011.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
UI Standards & Tools Khushroo Shaikh.
Interoperability Framework Overview March 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting Director, Office of Interoperability & Standards ONC HIT.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
S&I Framework Doug Fridsma, MD, PhD Director, Office of Standards and Interoperability, ONC Fall 2011 Face-to-Face.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Enterprise Architecture
The chapter will address the following questions:
Tools to Automate the S&I Platform A S&I Simplification Proposal in Collaboration with NIST and AHRQ March 29, 2013.
US Office of National Coordinator Standards and Interoperability (S&I) Framework S&I Simplification Work Group End-to-End Demo HL7 Working Group Meeting.
Tools Supporting ISO TC215 – ISO Re-Usable Component Strategy for Use Case Development Presented to HSPC DC Meeting, June 2015 Presented by.
Query Health Business Working Group Kick-Off September 8, 2011.
What is Business Analysis Planning & Monitoring?
Complete and Integrated Lifecycle Management. Challenges 1.
S&I Framework Operating Metrics Timing Outputs Participation & Process Framework Launch DateJan 7, 2011 First Initiative Launch DateJan 31, 2011 Elapsed.
Initial slides for Layered Service Architecture
S New Security Developments in DICOM Lawrence Tarbox, Ph.D Chair, DICOM WG 14 (Security) Siemens Corporate Research.
Managing Software Quality
Model Bank Testing Accelerators “Ready-to-use” test scenarios to reduce effort, time and money.
US Office of National Coordinator Standards and Interoperability (S&I) Framework S&I Simplification Work Group End-to-End Demo HL7 Working Group Meeting.
S&I Simplification WG Briefing for the HIT Standards Committee S&I Task Force Submitted: 5 February 2015.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
Tools to Automate the S&I Platform A Proposal March 29, 2013 DRAFT.
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
EHR System (EHR-S) Functional Requirements Implementation Guide: Laboratory Results Interface (LRI) Kickoff March 3 rd,
Public Health Reporting Initiative: Stage 2 Draft Roadmap.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
S&I Simplification Use Case Authoring Tool (UCAT) Introduction In collaboration with NIST and AHRQ 24 March 2013.
Interoperability Framework Overview Health Information Technology (HIT) Standards Committee June 24, 2010 Presented by: Douglas Fridsma, MD, PhD Acting.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
CIS 112 Exam Review. Exam Content 100 questions valued at 1 point each 100 questions valued at 1 point each 100 points total 100 points total 10 each.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
S&I PUBLIC HEALTH REPORTING INITIATIVE: DEVELOPING OF A TEAMING APPROACH S&I Public Health Reporting Initiative Nikolay Lipskiy, MD, DrPH, Co-Lead September,
S&I Simplification Initiative and UCAT Priorities In collaboration with NIST and AHRQ 18 April 2013.
Cross Initiative – S&I Simplification – “Core” Values Introduction Use Cases resolve to standardized Core Components in the S&I Simplification Core Matrix.
Lab Results Interface Validation Suite WG July 28, 2011.
OST Update Health IT Policy Committee March 14, 2013 Doug Fridsma, MD, PhD, FACP, FACMI Chief Science Officer & Director, Office of Science & Technology.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Electronic Submission of Medical Documentation (esMD)
S&I Simplification Use Case Authoring Tool (UCAT) Introduction In collaboration with NIST and AHRQ 19 March 2013.
Patterns in caBIG Baris E. Suzek 12/21/2009. What is a Pattern? Design pattern “A general reusable solution to a commonly occurring problem in software.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 30, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
US Office of National Coordinator Standards and Interoperability (S&I) Framework S&I Simplification Work Group End-to-End Demo HL7 Working Group Meeting.
Lab Results Interface Validation Suite Workgroup and Pilots Workgroup Vision, Charter, NIST Collaboration, July 8,
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.
Patricia Alafaireet Patricia E. Alafaireet, PhD Director of Applied Health Informatics University of Missouri-School of Medicine Department of Health.
Standards and Interoperability Framework esMD Primer of S&I Phases, Procedures, and Functions S&I F2F Thursday, April 12 th, :00 AM.
AHRQ’s US Health Information Knowledgebase Health Information Technology Standards Panel J. Michael Fitzmaurice, Ph.D. Agency for Healthcare Research and.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
An Overview of Requirements Engineering Tools and Methodologies*
Tools of Software Development
, editor October 8, 2011 DRAFT-D
EHR System Function and Information Model (EHR-S FIM) Release 2
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Presentation transcript:

S&I Simplification Use Case Authoring Tool (UCAT) Introduction In collaboration with NIST and AHRQ 25 March 2013

S&I Simplification Cross Initiative Effort to… Compile and Distill Components from All S&I Initiatives –For easy reference, organization, comparison –13 Use Cases with 33 Multi-Step Scenarios –Initiatives: TOC, LCC, LRI, LOI, PD, esMD, QH, DS4P, PHRI, HeD Convey 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 Show: –Event Steps with Actions taken – by Actors in Roles – to support individual health and provide healthcare –Health record entries resulting from Actions taken Show Commonalties, Patterns of Repetition/Re-Use –Both Current and Potential 24 March 2013S&I Simplification/UCAT Intro2

Components selected from S&I Initiative Use Cases Is it…Potentially Computable for… In Common? Re-Usable? Computable? Identity Accountability Permission, Consent Access, Data Use Performance/ Fulfillment Capture, Provenance Content: Struct/Unstruct Coding, Classification Completeness Signature Audit RequirementsYYY Actors, RolesYYY Events, ActionsYYY  As standards-based software services Data Objects, Elements YYY  As standards-based data objects, messages, documents… S&I Simplification Component Selection 24 March 2013S&I Simplification/UCAT Intro3

24 March 2013S&I Simplification/UCAT Intro4

(LINK to Core Matrix Spreadsheet v2.4) Status – of S&I Initiative Analysis Key – Contents of All Tabs Assertions – Basis for Initial Requirements *Common Requirements *Common Actors *Scenarios, Events – w/Action examples *Common Actions *Common Data Objects * Re-usable Components 24 March 2013S&I Simplification/UCAT Intro5 S&I Simplification Core Matrix

24 March 2013S&I Simplification/UCAT Intro6

(LINK to Progression Spreadsheet) To Date –S&I Simplification + AHRQ –Core Matrix + USHIK Registry Future –S&I Use Case Requirements Phase with Use Case Authoring Tool (UCAT) –S&I Use Case Harmonization Phase with NIST Tools Standards Selection Implementation Guide (Tools) Testing (Tools) 24 March 2013S&I Simplification/UCAT Intro7 S&I Simplification Progression

SourceContribution Use Case Authoring Tool (UCAT) Prototype Developed by: Art Griesser Prometheus Computing NIST Cross Industry Perspective, SmartGrid Project (2010) S&I Simplification Consensus Approved Core Simplification Matrix (.xlsx) S&I Use Case Requirements Template (.docx) S&I Lab Results Initiative (LRI) Consensus Approved LRI Use Case Requirements Template (.docx) HL7 EHR WG ISO/HL /16527, EHR/PHR System Functional Models AHRQ ISO USHIK Registry of S&I Simplification Components 24 March 2013S&I Simplification/UCAT Intro8 S&I Simplification Ingredients – UCAT Prototype

S&I Simplification Use Case Hierarchy GenerallyUCAT Prototype – Example An Initiative…Lab Results Interface (LRI) Initiative Has one or more Use Cases… 1) Lab Results Interface With one or more Scenarios… 1) Send/Receive/View Test Results With one or more Events (Steps)… 1) Send2) Receive3) View With one or more Actions. (Simplification Examples) Identify Patient, Provider, Lab System Originate/Attest/Retain - Lab Results Report Verify - Lab Results Report Set Data Access Permissions  Transmit - Lab Results Report Identify (EHR) System  Receive/Retain - Lab Results Report Identify, Authenticate Provider Check User Data Access Permissions Access/View - Lab Results Report 24 March 2013S&I Simplification/UCAT Intro9

S&I Simplification – Demonstration of Concept Use Case Tool Status Current Capabilities Imported Core Matrix Captured use case template structure –Populated completely for LRI Can construct new use cases from reusable components Can create human readable use cases (in UC template) Can curate underlying UC information Can use underlying info programmatically –SQL query Import: CSV –UCAT Native –Simplification Core Matrix –ISO/HL /16527 EHR/PHR System Functional Models Export: JSON, CSV Ability to clone Additional Capabilities and Refinements Ability to track status of information –Component Lifecycle Management Agreement to Productize UCAT Next Steps Add remaining 14 S&I Use Cases –One-time manual entry –Resolving differences from template Refine existing master template USHIK integration CEDD integration Evaluate handoff to downstream tools –Implementation Guide, Testing… 24 March 2013S&I Simplification/UCAT Intro10

Capture Once, Re-Use Many Times –Component + Standard + Imp Guide + Testing –Each Re-Use Instance: x 2 Savings –Facilitates Cross Agency –Facilitates S&I Cross Initiative –Unlocks Value of S&I (maximizing re-use, return) Experience Shows: –AHIC/HITSP: 5 Years, 17 Use Cases (3+/yr) –S&I: 2 Years, 13 Use Cases (6+/yr) –Now w/UCAT: ? 24 March 2013S&I Simplification/UCAT Intro11 S&I Simplification Benefits

Tools to Automate the S&I Platform A Proposal March 29, 2013 DRAF T

Growing Portfolio of Module Based Initiatives But this has led to growing complexity and diverse designs, models and solutions Doug Fridsma to HITPC – 3/14/13 13DRAFT

S&I Core Matrix Has Captured and Standardized S&I Initiatives as Shared, Reusable and Computable Components... Now we need a tool to use the Core Matrix 14DRAFT

Tools to Automate the S&I Platform USHIK Registry Reposito ry Link to NLM NIST Test Methods S&I Core Matrix UCAT IGAT Business Requirements and SMEs Implementable Solutions CEDD/FHIM/CIMI Data Models and Mapping Standards Developers and Stewards 15DRAFT

Why UCAT First? Foundational to all downstream automation and tools Highest leverage is at the beginning analysis and design of an initiative – COnstructive COst Model – Overall effort is doubled if analysis is shortchanged – Correct is hard... but easier than later fix – Ounce of prevention – Measure twice, cut once – “By failing to prepare, you are preparing to fail” Ben Franklin Use Cases – Study how users get value from system – Define how users interact with system – Help subsequent efforts deliver value – Are contracts between users & developers Refer to Art Griesser Presentation in Appendix DRAFT16

Use Case Authoring Tool 17DRAFT

NIST Role (Kevin – maybe quotes from Frederick Experience with Use Case Authoring through Smart Grid Developed automated test procedures, methods and tools for CEHRT and Mod Specs UCAT is based on NIST platform with further specialization for the S&I Core Matrix by Art Greisser DRAFT18

DRAFT19 Brief Overview of Process Flow

UCAT Demonstration NEED OUTLINE FROM ART Show how to create a human readable, machine computable UC example from Core Matrix and UCAT DRAFT20

S&I Simplification – Demonstration of Concept Use Case Tool Status Current Capabilities Imported Core Matrix Captured use case template structure –Populated completely for LRI Can construct new use cases from reusable components Can create human readable use cases (in UC template) Can curate underlying UC information Can use underlying info programmatically –SQL query Import: CSV –UCAT Native –Simplification Core Matrix –ISO/HL /16527 EHR/PHR System Functional Models Export: JSON, CSV Ability to clone Additional Capabilities Ability to track status of information –Component Lifecycle Management Next Steps Add remaining 14 S&I Use Cases to UCAT –One-time manual entry –Resolving differences from template Refine Core Matrix master template USHIK Integration S&I Data Integration –CEDD, FHIM, or CIMI... Evaluate and design handoff to downstream tools –Implementation Guide Authoring –Testing Tools, MDHT, V2 … DRAFT

Capture Once, Re-Use Many Times –Each Re-Use Instance = x 1 Savings –Facilitate Cross S&I Initiative Coordination –Facilitate Cross Agency/Domain Coordination –Unlocking Value of S&I (maximizes re-use, return) Experience Shows: –AHIC/HITSP: 4 Years, 17 Use Cases/Initiatives (4+/yr) –S&I: 2 Years, 13 Use Cases/Initiatives (6+/yr) –With UCAT: ? With IGAT, With Test Methods? Simplification – Automating the S&I Platform Benefits UC Requirements Implementation Guides Test Methods Faster, real world adoption S&I Platform Automated Tools DRAFT22

Appendices Gary Dickinson Presentation - DRAFT Use Case Authoring Tool - Simplification Introduction Art Greisser Presentation - "Use Cases" Slide Set Frederick’s Presentation - ? Link to USHIK S&I Pilot Site Link UCAT Portal TBD DRAFT23

Use Cases Arthur Griesser, PhD Prometheus Computing, LLC

What reduces development time the most? Better tools for developers? More training for developers? More experience in domain? Better understanding of requirements?

What reduces development time the most? Better tools for developers? More training for developers? More experience in domain? Better understanding of requirements? ✓

COnstructive COst MOdel Effort is Doubled if analysis is shortchanged

Why Is Analysis So Important? Correct is hard... but easier than later fix Ounce of prevention Measure twice, cut once By failing to prepare, you are preparing to fail Ben Franklin

Police in Gumperda, Germany, arrested a 64-year-old retired do-it- yourselfer in November after he drilled through a neighbor's wall in their duplex home. The man had spent two days trapped in his own basement, where he had laid bricks and mortar for a room but apparently forgot to leave himself an exit. [BBC News, ] Chuck Shepherd’s News of the Weird, week of Dec 12, 2010

Use cases... Study how users get value from system Define how users interact with system Help subsequent efforts deliver value Are contracts between users & developers

UML? Suitable for parts of a use case: Use case diagram Activity diagram Communication diagram Usually a small fraction of a use case UML does not define use case structure

Beware Analysis Paralysis Duplication Conflicting Requirements Excessive Complexity

The Next Level

What if... We could just “run” use cases as tests? Traceability guaranteed Tests & use cases always in synch Less effort, expense Tests are as complete as use cases

Today

Better Executable Verify >

Use cases Specify how user gets value from system Describe interaction of user & system Abstractly

Use cases Specify how user gets value from system Describe interaction of user & system Abstractly Ensure Verify Tests Concretely (specific test data)

S&I Simplification General High Level Goals [G1] Decrease | limit waste –Time spent working on artifacts –Unused or unreachable artifacts [G2] Increase domain penetration –The more use cases and scenarios, the more fully the domain issues can be understood and addressed [G3] Centralize information –Create a network of specialized information that can be shared [G4] Increase | facilitate collaboration –Manage centralized information so it stimulates collaboration (i.e. online services) [G5] Facilitate integration of information in process –Information generated at a point in the process should flow and be easily usable by underlying processes [G6] Reuse of existing infrastructure 21 March 2013Simplification/UCAT Intro39

S&I Simplification Use Case Authoring Tool Facilitates use case components capture (G1-2) Facilitates use case components reuse (G1-2) Creates a repository of use case components (G3) Is accessible online (G4) Allows for developed use cases to be electronically handled by underlying processes (i.e. implementation guides) (G5) Helps the developed use cases to stay consistent (G1-3- 5) Allows full access of the underlying data to trusted members for integration with the existing infrastructure (G6) 21 March 2013Simplification/UCAT Intro40