1 caBIG ® Architecture/ VCDE Joint WS F2F Meeting: Semantic Infrastructure MDR Update Oct. 22, 2009

2 Background/Introduction The goal of this session is to provide an update on the MDR portion of the Semantic Infrastructure Motivations, High Level requirements, approach

Current caDSR Tools Stabilization Plan Stabilized Freestyle Search CDE Browser Object Cart 1.0 Sentinel Tool In QA caDSR APIs – fixes to the UML Model Browser API Admin – fixes to Classification Scheme Items Maintenance UML Model Browser – increase results list, display workflows status and version information for projects SIW 4.1 –includes handling of Concept inheritance Curation Tool Bug fix release for Form Builder – Bug Fixes NMDP/cgMDR/Bulk Loader

caDSR Wiki e+Scope+Planning+Index 4

Motivation Factors and Background: Q: “Why do we have to worry about interoperability? Why can't we just build stuff that works? The internet works. The internet is human-to- human interoperability, not machine-to-machine.” A: Future semantic infrastructure: improving human machine interactions providing the ability to “query over open and dynamic collections of heterogeneous and distributed information sources” Help finding reusable stuff  BETTER SEARCHES Reducing/transforming Data into Information, Knowledge Humans will build systems Cost and accuracy dependent on availability of metadata:  Specification, information model, data dictionary, service descriptions, etc. Requires a formalism to enable human machine representation and interpretation ECCF is supposed to help us address the above – the End Result is to Enable discovery of reusable and interoperable services Google search: “Results of about 20,600,000 for lung cancer”lungcancer  More is not better  1 “UML as an Ontology Modelling Language”, Cranefield and Purvis

Motivation (Issues): Why we need to make it faster and easier to use? Developers are frustrated with how long it takes to add semantics to their model: Waterfall model, not iterative Steep ramp up: The learning curve is huge The Tools are not intuitive: Newcomers are usually frustrated that the tools are not easy to use Example Scenarios: Public ID

Motivation (Issues): Why we need to make it faster and easier to use? Developers are frustrated with how long it takes to add semantics to their model: Waterfall model, not iterative Steep ramp up: The learning curve is huge The Tools are not intuitive: Newcomers are usually frustrated that the tools are not easy to use Example Scenarios: Public ID

MDR Suite High Level Non-Functional Objectives Support needs of a Broader Stakeholder Community caBIG BIGHealth  CDISC, HL7 CIC, HITSP, CTMS and Life Sciences, FDA, Pharma Requirements Gathering Wiki: Develop ECCF style Specifications for MDR and Model Repository Develop SOA Services based on Specifications Design and refactor legacy MDR architecture into SOA Develop new SOA Services and Repostiories Implement Open Technologies (open source DB) Migrate data

MDR Suite High Level Non-Functional Objectives Simplify Assessing Conformance Currently hours per reviewer to review models for compliance Potentially - new services to assist reviewers Consolidate/minimize tools that need to be deployed to support federated metadata environment (Portlet approach) Incorporate best practices MDR authoring requirements into service specifications and tools based on caDSR experience Stabilize and reuse existing caDSR infrastructure where possible Create NEW end User Specifications and Applications (Authoring tools) based on SOA architecture

MDR Suite High Level Functional Objectives Support Federated Capabilities Including Submitter/Registrar Support ISO Part 6 Roles: Registration Authorities (RA), Responsible Organizations (RO), Submitting Organizations (SO) Registar (RA) Registar(RA) content retrieval/exchange Coarse grained, role and use case based services design Services to discover and use content from other MDRs caBIG software developers Incorporate Semantic Query Services to locate and reuse related content across registries caB2B, ICR WS Improve ability to find the “best” content Support for ISO Datatypes Develop Model and MDR repository Services to support ISO datatypes (?) Class/Attribute (DEC) Constraints E.g. Standard specifies a “CD” datatype, implementor wants to constrain the “Code System Name” to a particular list of vlaues Model specifies that attributes should be PQ type Value Domain specified using attributes E.g PQ chosen, automatically provide PQ metadata attributes for user specification during curation: validTimeLow, validTimeHigh, controlActRoot, controlActExtension …value, precision, codingRationale, source, unit, translation

MDR Suite High Level Functional Objectives Simplify Creating and Using Semantic Infrastructure (scalable process to harmonize and assert conformance) Easier, faster Relax rules for recording content Provide services to improve discovery and reuse of curated data elements and standard models when creating new applications and services Improved Search algorithms (DICE, etc) Match against existing registered content (not just concepts) Support Creation and Registration of Data Elements from various input formats (DB schema, OWL models, RDF, UML, Excel, CSV, Forms, etc).  MDACC, HL7 CIC Services to Provide Run Time Semantic Artifacts e.g. Value Set retrieval for referenced value domains Handling of Derived Data Elements that are composed of component data elements and rules Data Element and Value Domain Mapping and Transformation Authoring/Registration

MDR Suite High Level Functional Objectives Specification and Support for Model Registry/Repository CIM/PIM for SOA Services for Registration of models and their components Decomposed into ModelComponents and ModelComponentSets SOA Services for finding and reusing models or model components to create Sub-Domains (CTMS, Genzyme) Services - Create, Update, Version, Copy, Delete, Compare, Model Selection Semantic and Regular style Query to find and generate reusable model artifacts that can be reused in customer environments Retrieve related content CTMS: UML modeling such as EA and ArgoUML, OWL modeling tools such as Protégé, Excel Spreadsheets, Forms Authoring, Customize applications etc Validation Services to perform “Model Compare” VCDE, ECCF, Model Owners Authoring Tools for registration of models and selection of existing model components/component sets to create new models (Constrain, Extend) CTMS

NCI Enterprise Architecture Specification and BIG Health EAS Semantic ConOps Initiatives Semantic ConOps Initiatives

Semantic Infrastructure – Conceptual Backbone The logical view of the backbone consists of - terminology component (terminology services and repositories); - a information component (knowledge repository, data type specification and static model repository); - a computational component (interface and collaboration specifications); - and an enterprise /business component (rules and policy repository and role specifications). - An animation shows that except for the rules repository existing CBIIT semantics components address all or some of each backbone component.

Model Repository? COPPA caTISSUE sign component instances domain selection componentSet classifier

MDR and Model Services 16

17

18 What next? 5 RM-ODP Viewpoints—Support different concernsSystem

How do the viewpoints interact?

Requirements 20