Healthcare Integrated Product Team (IPT) NCOIC Brussels Plenary Session

1. Healthcare Integrated Product Team (IPT)NCOICBrussels Plenary Session Supriya Ghosh

2. NCOIC Healthcare IPT Work Session Agenda for Brussels Plenary Session • Define and propose definition of “Net-Centric Healthcare” • Evaluate stages of Semantic Interoperability within Healthcare Domain • Evaluate next steps for NCOIC Healthcare IPT

3. Net-Centric Healthcare Net-Centric Healthcare Definition Net-centric: (adj.) Participating as a part of a continuously-evolving, complex community of people, devices, information and services interconnected by a communications network to achieve optimal benefit of resources and better synchronization of events and their consequences. - The doctrine of network-centric healthcare operations that assures unimpeded flow and dissemination of fully compatible, high quality, and operation-relevant healthcare information and knowledge within the Worldwide Healthcare Information Grid. - Health data interoperability strategy is needed for achieving an interoperable environment in which health data is recorded, stored, managed and exchanged in accordance with standards that allow the data to be used appropriately by both internal and external end users.

4. Information Interoperability "the ability of two or more systems or components to exchange information and for each receiving party to recognize and use this information that has been exchanged.” Achieving Higher Levels of Maturity Enabling Activities: Interoperable Network, Communications, Data Proper Storage and Transfer of Data Application Sharing within Internet Cloud Effective Analysis and Reporting

5. Semantic Interoperability Level Semantic Interoperability Definitions from EU Healthcare • Level 0: no interoperability at all • Level 1: technical and syntactical interoperability (no semantic interoperability) • Level 2: two orthogonal levels of partial semantic interoperability • Level 2a: unidirectional semantic interoperability • Level 2b: bidirectional semantic interoperability of meaningful fragments • Level 3: full semantic interoperability, sharable context, seamless co-operability

6. NCOIC Healthcare IPT Semantic Interoperability Definitions from EU Healthcare • The European Union (EU) Semantic HEALTH study applies the following overall interoperability definition: • Health system semantic interoperability is the ability, facilitated by information technology applications and systems, • • to exchange, understand and act on citizens/patients and other health-related information and knowledge • • among linguistically and culturally disparate health professionals, patients and other actors and organizations • • within and across health system jurisdictions in a collaborative manner.

7. Information Paradigm Parse knowledge thread based on information sequence Government Data Growing Exponentially Intelligence Categorize information into specific knowledge domains Knowledge Thread based on Sequence Knowledge Parse data to recognize useful information Domains of Aggregated Information Information Is always useful Data How Do We Get There? - Automate the process based on Semantics Is both useful and useless Applying Semantic Context Common Information Model Enterprise Meta Data Inference Engine Information • Structured Data (databases, web services, flat files) • Unstructured Content (e-mail, Office documents, Multimedia) • Complex, real-world relationships, schema • Automated, machine-driven • Supports automated query, SPARQL and data discovery • Business Rules Engine • RDF-based Data Store • OWL-based Ontology • Semantic Indexing • Distributed Storage Management • Semantic Context necessary for multiple information domains • Adoption of common model for correlation of data • Use of Coding/Terminology Services - 7 -

8. Next Steps Seeking Support for Next Steps: • Healthcare Interoperability IPT plans to develop and collaborate on an innovative set of deliverables that can be offered to government healthcare customers as frameworks and patterns. Use the healthcare domain to formulate semantic relationships and models. • Work on Semantic Interoperability Services as it pertains to Healthcare customers • Work on setting up Technology Reference Levels for Healthcare Interoperability • Engage NCOIC members and foster relationships with appropriate standards organizations

9. TRLs Technology Readiness Level Definition: TRL 1 Basic principles observed and reported: Transition from scientific research to applied research. Essential characteristics and behaviors of systems and architectures. Descriptive tools are mathematical formulations or algorithms. TRL 2 Technology concept and/or application formulated: Applied research. Theory and scientific principles are focused on specific application area to define the concept. Characteristics of the application are described. Analytical tools are developed for simulation or analysis of the application. TRL 3 Analytical and experimental critical function and/or characteristic proof-of-concept: Proof of concept validation. Active Research and Development (R&D) is initiated with analytical and laboratory studies. Demonstration of technical feasibility using breadboard or brassboardimplementations that are exercised with representative data. TRL 4 Component/subsystem validation in laboratory environment: Standalone prototyping implementation and test. Integration of technology elements. Experiments with full-scale problems or data sets. TRL 5 System/subsystem/component validation in relevant environment: Thorough testing of prototyping in representative environment. Basic technology elements integrated with reasonably realistic supporting elements. Prototyping implementations conform to target environment and interfaces. TRL 6 System/subsystem model or prototyping demonstration in a relevant end-to-end environment (ground or space): Prototyping implementations on full-scale realistic problems. Partially integrated with existing systems. Limited documentation available. Engineering feasibility fully demonstrated in actual system application. TRL 7 System prototyping demonstration in an operational environment (ground or space): System prototyping demonstration in operational environment. System is at or near scale of the operational system, with most functions available for demonstration and test. Well integrated with collateral and ancillary systems. Limited documentation available. TRL 8 Actual system completed and "mission qualified" through test and demonstration in an operational environment (ground or space): End of system development. Fully integrated with operational hardware and software systems. Most user documentation, training documentation, and maintenance documentation completed. All functionality tested in simulated and operational scenarios. Verification and Validation (V&V) completed. TRL 9 Actual system "mission proven" through successful mission operations: Fully integrated with operational hardware/software systems. Actual system has been thoroughly demonstrated and tested in its operational environment. All documentation completed. Successful operational experience. Sustaining engineering support in place.