National Cancer Institute Achieving Interoperability: Observations and Recommendations from 20 Years of Mistakes (and Some Learning) Charlie Mead, MD,

Slides:



Advertisements
Similar presentations
| Implications for Health Information Exchange – MetroChicago January 2011.
Advertisements

September, 2005What IHE Delivers 1 Joe Auriemma Siemens Medical Solutions, Health Services Senior Director, Integration Engineering Siemens Medical Solutions.
BRIDG Overview Clinical Observation Interoperability March 18, 2008.
A Model of eHealth Interoperability Craig Kuziemsky, Telfer School of Mgmt, University of Ottawa. James Williams, Community Care Information Management.
e-Framework Components and Responsibilities.
The Future of Formal: Academic, IC, EDA, and Software Perspectives Ziyad Hanna VP of Research and Chief Architect Jasper Design Automation Ziyad Hanna.
Enterprise SOA and Cloud Planning Presentation to Association of Enterprise Architects, Washington DC Chapter John Chi-Zong Wu
Rational Unified Process
What is software engineering?
Mink Spaans What are the problems that need to be solved What is hard.
© 1998 Concept Five Technologies Enterprise Application Integration Capability Maturity Model.
Standardization and Interoperability in healthcare IT Export HIS Shanghai & Guangzhou seminars Juha Mykkänen Health Information Systems R & D Unit University.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Strategic Marketing 1. Imperatives for Market-Driven Strategy
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
B usiness T echnology S olutions AMI – Advanced Metering Infrastructure Consumers Energy Mark Ortiz March 9, 2011.
Building, Maintaining, and Evolving a Model of Shared Semantics -- The BRIDG Project: Lessons Learned and Next Steps Charles Mead MD, MSc Chief Technology.
Software Development Process
Don Von Dollen Senior Program Manager, Data Integration & Communications Grid Interop December 4, 2012 A Utility Standards and Technology Adoption Framework.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Nurjana Technologies Company Presentation. Nurjana Technologies (NT) is a small business enterprise founded in 2012 and operating in Aerospace and Defence.
TDT4252/DT8802 Exam 2013 Guidelines to answers
Visual Modeling – HL7 Challenges, Benefits, and Applications (Is a Picture Worth 1000 Words?) Charlie Mead, MD, MSc Director, Healthcare Information Architecture.
Introduction to UML 1 Quick Tour Why do we model? What is the UML? Foundation elements Unifying concepts Language architecture Relation to other OMG technologies.
Lori Smith Vice President Business Intelligence Universal Technical Institute Chosen by Industry. Ready to Work.™
EHR Stakeholder Workshop: Toward New Interaction Models Two Illustrative Instances and a Suggested Framework “What’s right is what’s left when you’ve done.
What is software? Software is a set of items or objects that form a configuration that includes: –Programs –Documents –Data.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
 BRIDG R3.0.2 was released in August 2010  The BRIDG Model passed the initial ISO Joint Initiative Council ballot as a Draft International Standard (DIS)
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
National Institute of Standards and Technology Technology Administration U.S. Department of Commerce 1 Patient Care Devices Domain Test Effort Integrating.
Toolkit for Planning an EHR-based Surveillance Program | HL7 Clinical Document Architecture An Introduction.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 10: Structure the Use-Case Model.
Dave Iberson-Hurst CDISC VP Technical Strategy
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
1 Introduction to UML. 2 What is UML? UML is an acronym for Unified Modeling Language. Unified –Combines the best from existing object- oriented software.
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Introducing… the Sustainable Energy 4 All Action Accelerator! Adam Cooper Senior Manager, Accenture Sustainability Services United Nations Global Compact.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
Software from Requirements Brent Haines April 12, 2007 Why Methodology Doesn’t Really Matter.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
WSDL in a Healthcare Enterprise Architecture Lorraine Constable, Constable Consulting John Koisch, Guidewire Architecture Jean Henri Duteau, GPI.
EHR Stakeholder Workshop: Toward New Interaction Models The Nuts and Bolts of Patient Recruitment…from a (nearly) non-technical perspective “What’s right.
Daphne Ogle, Fluid Design Lead, University of California, Berkeley Content Management Research.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Requirement Engineering Virtusa Training Group 2004 Trainer: Ojitha Kumanayaka Duration : 1 hour.
Interchange vs Interoperability Main Entry: in·ter·op·er·a·bil·i·ty : ability of a system... to use the parts or equipment of another system Source: Merriam-Webster.
Foundational Program Overview September  2004 Copyright RosettaNet. RosettaNet Foundational Programs Program Overview ProgramPhase InvestigateDesignImplement.
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
Software Engineering Principles Practical Advice and Steps for Managing Your Project.
The Semantic Web. What is the Semantic Web? The Semantic Web is an extension of the current Web in which information is given well-defined meaning, enabling.
Basics of SOA Testing Assurance Services Unit 24 February 2016.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Challenges and issues with information sharing: The four pillars of semantic interoperability Douglas B. Fridsma, MD, PhD, FACP University of Pittsburgh.
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
Canadian SNOMED CT Strategy October 2012 Draft. Content 1 Background Approach Current State Future State Considerations Action Plan.
BRIDG Overview and Ballot Results ISO TC 215 Rio de Janeiro 11 May 2010 Julie Evans Senior Director, Technical Services, CDISC Wendy Ver Hoef Senior Analyst,
XML Interoperability & Convergence ISO XML Working Group (WG 10) XML on Wall Street November 20th, 2001 John Goeller.
Dave Iberson-Hurst CDISC VP Technical Strategy
UNIT 1.
System Development Process
A Case Study on Enterprise Architecture
Clinical Observation Interoperability March 18, 2008
John S. Toussaint, M.D. CEO, ThedaCare Center for Healthcare Value
EHR Stakeholder Workshop: Toward New Interaction Models
Presentation transcript:

National Cancer Institute Achieving Interoperability: Observations and Recommendations from 20 Years of Mistakes (and Some Learning) Charlie Mead, MD, MSc Senior Associate Booz Allen Hamilton “What’s right is what’s left when you’ve done everything else wrong.” – Robin Williams

National Cancer Institute The Starting Point (circa 1985) 10 years experience building ambulatory ECG analysis application –Single stakeholder role (cardiologists) –Isolated, well-defined problem –Primitive tools –Minimal UI requirements –Minimal data sharing requirements Stable data structures –Interoperability not a driving force

National Cancer Institute The Next Step (circa 1995) Founded a company to bring ‘point-of-care’ computing to Home Healthcare –Multiple stakeholders (nurses, CFOs, payors, regulatory) –Complex, somewhat ill-defined (shifting) problem –Variety of tools (DBs, tablet computers, multiple target systems) –Considerable UI requirements Type I vs Type II systems (“All the simple systems have been built” – Grady Booch) –Extensive data sharing requirements Evolving data structures –Interoperability (clinical/administrative/financial) as a key requirement

National Cancer Institute Interchange vs Interoperability Main Entry: in·ter·op·er·a·bil·i·ty : ability of a system... to use the parts or equipment of another system Source: Merriam-Webster web site interoperability : ability of two or more systems or components to exchange information and to predictably use the information that has been exchanged. Source: IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries, IEEE, 1990] Semantic interoperability Syntactic interoperability (interchange) Syntax  Structure Semantics  Meaning

National Cancer Institute “Protocol” and the Semiotic Triangle Symbol “ Protocol ” “We need to sign off on the protocol by Friday” Concept 1 Thing 1 Document Study “Protocol XYZ has enrolled 73 patients” Thing 2 Concept 2 “Per the protocol, you must be at least 18 to be enrolled” Concept 3 Thing 3 Plan Source: John Speakman

National Cancer Institute Semantic Interoperability – Different Perspectives Exchanging meaning (not just structure) –Human-to-Human semantic interoperability –Hybrid/stepwise semantic interoperability –Computer-to-Computer semantic interoperability The critical role of context –Where does it live? Sharing semantics is not just about sharing static structures; definitions of dynamic behavior are also equally critical

National Cancer Institute ` The Communication Pyramid Communication Implementation-Independent Implementation-Specific Abstraction

National Cancer Institute Climbing the Communications Pyramid Recognizing the features of complex systems –Multi-level vertical organizational structure (“the org chart”/silos of vertical isolation) –Horizontal processes for producing the system’s Products of Value Healthcare is the epitome of a complex system Cross-disciplinary project teams –Domain Experts / Requirements / Design / Development / Testing / Documentation and Training / Maintenance

National Cancer Institute Climbing the Communications Pyramid Think architecturally –Uses and Users –Static structure –Dynamic behavior –Structural Walls / Partitions / Furniture –Dog houses vs Skyscrapers

National Cancer Institute Climbing the Communications Pyramid Recognize the importance of Organizational Maturity in an integrated development/user community –Level 1: Heroism and Passion –Level 2: A Set of Directions –Level 3: A Map –Level 4: Gathering Process Variance –Level 5: Using Process Variance data to drive Process Improvement Everyone wants to be Level 5 –Progression is stepwise Level 1 does not mean incompetence!

National Cancer Institute Climbing the Communications Pyramid Adopt a organization-wide process framework –The Waterfall Process works when… The problem is isolated, well-defined, and stable Requirements are stable –The Unified Process (framework) has evolved over 20+ years of feet-on-the-ground experience with failed projects, frustrated users, overworked developers, and angry customers Iterative/Incremental (model human problem solving) Risk-focused (“do the hard stuff first”) Architecture-centric (“functional requirements vs quality requirements”) Driven by visual models (“a picture is worth 1000 words”)

National Cancer Institute ` The Communication Pyramid Communication Free-text Documents Structured Documents ad hoc Drawings Non-standard Graphics Discussions Standardized Models (UML) Implementation-Independent Implementation-Specific Abstraction

National Cancer Institute Climbing the Communications Pyramid Utilize standards whenever possible –Value sets –Messages –Documentation –Process frameworks Standards facilitate interoperability Standards leverage experience Standards decrease maintenance/evolution costs

National Cancer Institute The Present (for now) (circa 2006) This is a HARD PROBLEM! –Comprehensive Semantic Interoperability – i.e. human, computer, and/or hybrid/incremental in nature and meaningful to all stakeholders – in the context of complex systems is – and will always be – a huge challenge –Evolving technologies will make it incrementally easier….but it will always remain a complex, difficult, and challenging problem...the Semantic Web will not solve all of our problems –Consider the cost of not achieving semantic interoperability Monetary Social/Ethical

National Cancer Institute Top-Down Commitment (Not Micromanagement – Level 5 organization) Willingness to commit management $$s Willingness to provide management oversight –Willingness (and ability) to define standards-for-use Process frameworks Data exchange standards Standards for Milestones/Deliverables Management understanding of the short-term difficulties and the long-term rewards –Avoid the allure of simple solutions to complex problems –Avoid the pitfalls of schedule-based project management

National Cancer Institute Bottom-Up Passion and Dedication Communication Collaboration Cooperation Insatiable appetite for learning –Understanding must cross-domain boundaries Indomitable spirit and vision: “Eyes on the prize.” –(Semantic) interoperability is still hard work –Some legacy data may not be computationally interoperable Process frameworks and standards are your friend… –“This is more about sociology than technology” (George Komatsoulis)

National Cancer Institute Less “Informational” Systems Highly “Informational” Systems Stepwise Computational Interoperability * *HL7 Clinical Document Architecture: Single standard for computer processable and computer manageable data * (Wes Rishel, Gartner Group)

National Cancer Institute Final Comments CTWG initiatives –“Harmonize existing NCI IT systems” –Build a Clinical Trial database/data warehouse Dr. Carmona’s call for “ending the silos” “Healthcare is the only business where information sharing is the norm rather than the exception. Those of us who build systems are not used to this framework. However, if we are to provide the healthcare system with the tools they need, we must embrace this paradigm completely, committing ourselves to defining, designing, and building fundamentally different types of system than those with which we have our predominate historical experience.”

National Cancer Institute A Q & Q U E S T I O N S A N S W E R S