Overview: NCI caDSR and Semantic Services
Clinical Interoperability Council
January 21, 2010
Phoenix, Arizona
Dianne M. Reeves
National Cancer Institute
1
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
The ECCF Specification Stack
Topic
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-
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.
Rules, Procedures
Localized
Information
Model,Transforms,
Schema
Collaboration scripts,
Orchestrations,
Realized Interfaces
Execution Context,
Platform Bindings,
Deployment Model
Specification
Independent
Platform-
Specific
Technology Viewpoint tests Conformance Statements collected in cells
Conceptual view of the various kinds of repositories
MDR Topology
Metadata
Authoring
UIs
MDR
Local node
Tools &
Sources
Metadata
Management
MDR
Central node
Submission
Harmonization
Review
Registration &
Management
DE
VD
Registry
Model
Services
Transfor
mations
Service Interface
Authors, Curators
Rules
Image
Registry
Repository
Registry
Registry
Repository
Browser (s)
Services
Specification
Service
Discovery
Service
Discovery
CDE Search
CDE Search
Value Domain
Transformation
Value Domain
Transformation
Model Discovery
Service,
Schema,
Model
Validations
Compare
Browser (s)
Repository
Etc…
Terminology
XML…
Enterprise Vocabulary Services
Implementations
Repository
Service Interface
Concept
Submission
Harmonization
Review
Registration &
Management
Service Interface
Service Interface
Form
Common
Services
Metadata
Management
Model Discovery
Service,
Schema,
Model
Validations
Compare
Software Engineering
Lifecycle Overview
Phases
9 Disciplines
Inception
Elaboration
Construction
Transition
Production
Business Modeling
User
Experiences
Requirements
Analysis & Design
Implementation
Test
Deployment
Configuration
& Change Mngt
Project Management
Environment
Initial
Elab #1 Elab #2
Const
#1
Const
#2
Iterations
Const Tran Tran
Production
#N
#1
#2
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.
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
Direct Stakeholder Profiles
Drug Companies
• Novatis, Genzyme
•Sue Dubman
Patient
Advocates
caBIG Clinical
Sciences
•John Speakman,
Hannes Niedner
•
•caEHR
•
•
Cancer Centers
•MD Anderson,
Michael Riben,
•
Emory – Joel Saltz, •
Todd Parnell
•
•
•
•
Forms Repository
CRFs and variables
CTMS Software
Vendors
•MediData, Velos
•
•
Federated 11179 MDR and
Terminology Services
• Technology Enabled CRFs
• An infrastructure that
• Structured Authoring Tools
Helps them get personalized care
ISO 21090 Datatypes
Share/reuse models
and behavioral
semantics
Rules engine/repository
caBIG Life
Sciences
• Juli Klemm,
caEHR
SDOs and other
Government
Agencies
•HL7, CDISC, CIC
Share platform independent
data standards
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
Federated 11179 MDR
• Enrich Metadata for Services: Ad
Terminology Services
hoc Service Interoperability
Rules and Workflow
(Provenance:/Pre-processing, QoS,
Better support for finding
Contacts)
collecting and aggregating data
• Discover/Compare/Extend/Constra
on the Grid
in existing service components
Federated 11179 MDR
International Collaborators
other MDRs
•cancerGrid
•
•
•
•
•
•
•
Federated 11179 MDR
and Terminology Services
Ad hoc Service Interoperability
Semantic Workflows
Leverage semantic web
technology in caBIG to support
Search and discovery
•
Terminologists
•Bob Friemuth
Terminology Authoring
and Mapping between vocabularies
Semantic Query for Terminologies
Data Managers
& Metadata Curators
• D. Reeves
•
•
Clinician friendly search/browse
and harmonization support
Customizable download
CDE and VD Services
NCI Internal
CRFs
Systems
CTEP, DCP
• Christo
Andonyadis
Data RepositoryA
‘caDSR’
Registry
Static Semantics
What is this data?
Does it match
The Service?
Data RepositoryB
Data RepositoryC
Analytic
Service 1
Analytic
Service 2
Transformation
Service DR 1->2
Service
Registry
What is the syntax
of the input and
output data?
Data RepositoryD
Rules
Registry
Model Validation
Service
Pre-Processing
Service 1
Etc…
Descargar

Presentation Title Goes Here