Upload
juniper-wade
View
215
Download
0
Tags:
Embed Size (px)
Citation preview
SAIF and VCDEEvolving VCDE Roles with SAIF
Sherri de Coronado MS, MBANCI VCDE lead
Center for Biomedical Informatics & Information Technology
2
Where we’ve been today– CBIIT Roadmap (for multiple programs)
– Technology Strategy (Vision of Interoperability with SAIF and ECCF)
– Semantic Infrastructure Roadmap and Static Semantics
– Technology and Security Roadmap Next up: caEHR sessions
Tomorrow, SAIF Effects & VCDE contributions to ECCF Implementation Guide
What’s next for VCDE?
Context
3
NCI/ NCP Mission: Reduce the Burden of Cancer
CBIIT Mission: Interconnect the biomedical enterprise with an interoperable, standards-based framework that bridges research and care, driving and enabling 21st century medicine in support of eliminating the burden of cancer.
Mission is the Same!
4
Silver Compatibility – VCDE spent 5 years of building and managing processes and artifacts for interoperability of applications – Great work, new challenges
New paradigm = services, sSOA - to facilitate Enterprise level interoperability, where the enterprise is the larger clinical and research community, operating under SAIF and ECCF
caBIG not the only CBIIT program – merge/ reuse experiences/ processes/ tools/ standards where possible
How Does VCDE Change to Meet the New Needs?
5
Preview/Press Release
Evolution, not Revolution– Architecture must support business
Problem Statement: CBIIT needs to…– define, design, develop, and deploy software
components defined as business capabilities rather than “monolithic applications;”
– certify software components at a more granular level than the current “metal level” approach;
– enable automated/semi-automated certification; and– provide technology-independent specifications that
enable organizations to build software components that will interoperate with CBIIT components.
5From: Charlie Mead presentation
6
The LEGO® Analogy
NCI Enterprise Services
Applications
From: Juli Klemm presentation
7
Toward the goal of …
ca-AERS PSC C3PR C3D
caBIG® Clinical Trials Suite
caGrid
RRegistration
AeAdverse
Event
PtProtocol
Etc.
“BU
SIN
ESS”
“CO
RE”
“CAP
ABIL
ITY”
SSpecimen
ScScheduling
TxTranslation
AuAudit
RaReferral and
Authorization
HxHx and Physical
VaValidation
EvEnterpriseVocabulary
OOrganization
PPerson
AAgent
DDisease
CCorrelation
PaProtocol
Abstraction
DnDischarge
Note
CqClinical
Research Qry
TpTreatment
Plan
DsDecisionSupport
IImage
LLab
RxPrescription
“Inf
ra /
U
TILI
TY”
CmContract
Management
MpMaster
Problem List
AyAllergy
SdSDTM
EEligibility
KmKnowledge
Management
CrCredentialing
OcStudy
Outcomes
QrData
Query
IdId
Management
TrTrust
Management
AaAuthorization Authentication
PyPolicy
OoOrders
Observations
ca-Tissue
ca-Array caInt2 NBIA
caBIG® Life Sciences Bundle
8
VCDE KSAs
Terminology/ ontology principles, reviews Models and Binding Terminology to models
– UML, Conceptual, PIM, PSM– Some understanding of importance of value
sets Developing and implementing review and
governance processes and standards Pool of people training up in ECCF Experience in mentoring Requirements gathering
8
9
Applying those strengths during 2010
Primary efforts over past months:– SAIF Effects on VCDE – • Working groups report/ discuss tomorrow, • Overview of existing/ developing / needed caBIG
processes (Brian)
Workgroup products feeding into urgent need, implementation guide for ECCF
Requirements elicitation
9
10
The ECCF Specification Stack
11
The CBIIT ECCF Implementation Guide (IG)
What it is: CBIIT’s implementation details of the HL7 “SAIF Book” (referred to as “Implementation Guide(s)” (IGs))– Information Framework– Behavior Framework– Governance Framework (reuse of standards)– Enterprise Conformance and Compliance Framework
When– ECCF IG is first
• Draft available ~May 15• Full operationalization by Fall 2010
– Semantic Infrastructure (v2) will include IF and BG IGs– Enterprise architecture governance SAIF GF IG
11
From Charlie Mead
12
Applying those strengths cont’d
For remainder of 2010 will continue to:– Work on implementation guide for ECCF– Contribute to operationalization (e.g. caBio
pilot)– Identify and merge processes/ standards with
caEHR (likely)– Contribute to Informational and Governance
Framework guides (likely)– Support translations among terminologies,
models (possible)
13
While we discuss how to define caBIG/VCDE in the future?
More problem oriented focus Convene smaller working meetings around a
problem/ issue Identify ways to get broader representation of the
“community” (clinical medicine, cancer centers, academic research)
Engage with caEHR, converge on standards Re: Domain models, should VCDE role continue to
be only guidance? Additional non-terminology ontology building
capabilities/ testing LexEVS for translation management?
Should the name VCDE be changed? 13
14
End
Thanks in advance for lending your expertise over the next months. There are still many questions. Maybe more questions than answers. Let’s work together to fill in the gaps.