1 / 9

Clinical Interoperability Council January 21, 2010 Phoenix, Arizona Dianne M. Reeves

Overview: NCI caDSR and Semantic Services. Clinical Interoperability Council January 21, 2010 Phoenix, Arizona Dianne M. Reeves National Cancer Institute. Semantic Infrastructure Evolution. Semantic Infrastructure Evolution (SI) will Promote data discovery and reuse

shaquille-charles
Download Presentation

Clinical Interoperability Council January 21, 2010 Phoenix, Arizona Dianne M. Reeves

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  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

  3. The ECCF Specification Stack Technology Viewpoint tests Conformance Statements collected in cells

  4. Conceptual view of the various kinds of repositories

  5. Phases Inception Elaboration Construction Transition Production 9 Disciplines Business Modeling User Experiences Requirements Analysis & Design Implementation Deployment Test Configuration & Change Mngt Environment Project Management Initial Elab #1 Elab #2 Const #1 Const #2 Const #N Tran #1 Tran #2 Production Iterations Software EngineeringLifecycle 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. Direct Stakeholder Profiles • caBIG Life Sciences • Juli Klemm, caEHR • SDOs and other • Government Agencies • HL7, CDISC, CIC • Drug Companies • Novatis, Genzyme • Sue Dubman Patient Advocates • Federated 11179 MDR • and Terminology Services • Ad hoc Service Interoperability • Semantic Workflows • Leverage semantic web technology in caBIG to support • Search and discovery • Share platform independent • data standards • Federated 11179 MDR and Terminology Services • Technology Enabled CRFs • Structured Authoring Tools • An infrastructure that • Helps them get personalized care • Information Modelers and Developers • John Koish, Paul Boyes, Sal Mungal, Sharon Gaheen, Tajas Dave, Patrick McConnell • ?? • caBIG Clinical Sciences • John Speakman, Hannes Niedner • caEHR • Terminologists • Bob Friemuth • ISO 21090 Datatypes • Share/reuse models and behavioral semantics • Rules engine/repository • 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/Constrain existing service components • Terminology Authoring • and Mapping between vocabularies • Semantic Query for Terminologies • Cancer Centers • MD Anderson, Michael Riben, Emory – Joel Saltz, Todd Parnell • DataManagers • & Metadata Curators • D. Reeves • Federated 11179 MDR • Terminology Services • Rules and Workflow • Better support for finding collecting and aggregating data on the Grid • Clinician friendly search/browse and harmonization support • Customizable download • Forms Repository • CRFs and variables • CTMS Software • Vendors • MediData, Velos Federated 11179 MDR • CDE and VD Services • CRFs • International Collaborators • other MDRs • cancerGrid • NCI Internal • Systems • CTEP, DCP • Christo Andonyadis

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

More Related