1. 1 Clinical Interoperability Council January 21, 2010 Phoenix, Arizona Dianne M. Reeves National Cancer Institute Overview: NCI caDSR and Semantic Services

2. Semantic Infrastructure Evolution Semantic Infrastructure Evolution (SI) will Promote data discovery and reuse Use ISO 11179 Ed. 3.0 for repository federation Improve analysis/requirements approach Promote Services Promote interactions between business partners Implement the HL7 SAEAF Move from a 2-part semantic environment to 4-part Metadata Vocabulary Rules Models 2

3. The ECCF Specification Stack Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Business Context, Reference Context Domain Analysis (Information) Model Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities Platform- Independent Business Governance Project-oriented Domain Information Model, Constrained Information Model, Localized Information Model, Hierarchical Message Definition Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Existing Platform models, libraries, etc. Platform- Specific Rules, ProceduresLocalized Information Model,Transforms, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context, Platform Bindings, Deployment Model Technology Viewpoint tests Conformance Statements collected in cells

4. Conceptual view of the various kinds of repositories

5. Initial Elab #1 Elab #2 Const #1 Const #1 Const #2 Const #2 Const #N Const #N Tran #1 Tran #1 Tran #2 Tran #2 9 Disciplines Business Modeling User Experiences Requirements Analysis & Design Implementation Deployment Configuration & Change Mngt Project Management Environment Inception Elaboration Construction Transition Production Phases Test Iterations Software Engineering Lifecycle Overview

6. What is the focus of SI Requirements Development? Project Constraints –Budget, Timeframe, Regulatory, etc Functional and Data Requirements –Deals with direct end users of the system Things the system must do to must meet a business objective or goal in order to satisfy an actor in a use case –What are the services/functionality it must provide? Compare Models Tell me what the rules were for setting this field to Y Find Data that Matches a Service Input or Output Find Service that can be used with my Data Transform my code into an equivalent code acceptable by the other system Extend an enumeration with additional permitted values/choices Etc.

7. What is the focus of SI Requirements Development? Non Functional Requirements –Indirect and Direct end users –Look and Feel Requirements –Usability Requirements – ie making the product usable with relatively low of knowledge –Performance Requirements –Operational and Environmental Requirements –Maintainability and Support Requirements –Security Requirements –Cultural and Political Requirements –Legal Requirements

8. SDOs and other Government Agencies HL7, CDISC, CIC Drug Companies Novatis, Genzyme Sue Dubman Direct Stakeholder Profiles ISO 21090 Datatypes Share/reuse models and behavioral semantics Rules engine/repository Federated 11179 MDR and Terminology Services Ad hoc Service Interoperability Semantic Workflows Leverage semantic web technology in caBIG to support Search and discovery Terminology Authoring and Mapping between vocabularies Semantic Query for Terminologies Clinician friendly search/browse and harmonization support Customizable download Forms Repository CRFs and variables caBIG Life Sciences Juli Klemm, caEHR caBIG Clinical Sciences John Speakman, Hannes Niedner caEHR Cancer Centers MD Anderson, Michael Riben, Emory – Joel Saltz, Todd Parnell CTMS Software Vendors MediData, Velos International Collaborators other MDRs cancerGrid Data Managers & Metadata Curators D. Reeves Federated 11179 MDRCDE and VD Services CRFs NCI Internal Systems CTEP, DCP Christo Andonyadis Information Modelers and Developers John Koish, Paul Boyes, Sal Mungal, Sharon Gaheen, Tajas Dave, Patrick McConnell ?? Streamlining Control/Creating/Sharing /Reusing metadata (Conformance Profiles) to support Tools for searching/browsers LIMS Ontology NLP Searches Enrich Metadata for Services: Ad hoc Service Interoperability (Provenance:/Pre-processing, QoS, Contacts) Discover/Compare/Extend/Constra in existing service components Terminologists Bob Friemuth Patient Advocates An infrastructure that Helps them get personalized care Federated 11179 MDR and Terminology Services Technology Enabled CRFs Structured Authoring Tools Share platform independent data standards Federated 11179 MDR Terminology Services Rules and Workflow Better support for finding collecting and aggregating data on the Grid

9. Etc… Analytic Service 1 Analytic Service 2 Model Validation Service Pre-Processing Service 1 Transformation Service DR 1->2 Data RepositoryA Data RepositoryB Data RepositoryC Data RepositoryD caDSR Registry Static Semantics What is this data? Does it match The Service? Service Registry What is the syntax of the input and output data? Rules Registry Can I make DRA fit AS1? Yes, you need to pre- process it, then use Transformation Service DRA-> AS1 What is this data? Does it fit?