Agenda Terminology Tooling Proposal Information modelling tooling requirements options and selection process if time Tooling framework and other tooling requirements if time Terminology Tooling ID: 421118
Download Presentation The PPT/PDF document "CIMI “Terminology” Meeting" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
CIMI “Terminology” MeetingSlide2
Agenda
Terminology Tooling Proposal
Information
modelling
tooling (requirements, options and selection process
) (if time)
Tooling
framework and other tooling
requirements (if time)Slide3
Terminology ToolingSlide4
Terminology Tooling Puzzle
Query and Browsing
Programmatic API
Collaborative Authoring
Issue TrackingSlide5
Terminology Tooling Puzzle
Query and Browsing
– Concepts, Value Sets, Maps, etc
.
Web Browser
Snow OWL Lite
CTS2 Clients and Widgets
itServer
(?)
(other)
Web
ProtegeSlide6
Terminology Tooling Puzzle
Programmatic API (REST or SOAP?)
Snow OWL Server
Ocean’s terminology server
Apelon
DTS
CTS2
SPARQL
SQL
(other?)
(SNOMED Query Specification)Slide7
Terminology Tooling Puzzle
Collaborative Authoring
IHTSDO Workbench / Kaiser Extensions
(hosting?)
SVN
Snow Owl
Refset
Creation
Snow OWL
IHTSDO
refset
creation tool (for SNOMED
refsets
)
IHTSDO Workbench / Kaiser Extensions
(others)Slide8
Remembering our Vision…
. . .
Service
Interface
Data
ApplicationSlide9
What Is Needed to Create a New Paradigm?
Standard set of detailed clinical data models coupled with…
Standard coded terminology
Standard API
’
s (Application Programmer Interfaces) for healthcare related services
Open sharing of models, coded terms, and API
’
s
Sharing of decision logic and applicationsSlide10
Information Model Ideas
#
10
Repository of Shared
Models in
a Single Formalism
DCMs
CDA
Templates
openEHR
Archetypes
CEN
Archetypes
LRA
ModelsCMETs, HMDsRMIMsCEMsStandardTerminologiesInitial Loading of RepositoryRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsV2 “|”HTMLUMLADLV2 XMLV3 XMLV3 NextCEN ArchetypeCDASOAPayloadCEMLRAOWLCDISC SHARETranslatorsTranslatorsTranslatorsSlide11
Information Model Ideas
#
11
Repository of Shared
Models in
a Single Formalism
DCMs
CDA
Templates
openEHR
Archetypes
CEN
Archetypes
LRA
ModelsCMETs, HMDsRMIMsCEMsStandardTerminologiesInitial Loading of RepositoryRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsV2 “|”HTMLUMLADLV2 XMLV3 XMLV3 NextCEN ArchetypeCDASOAPayloadCEMLRAOWLCDISC SHARETranslatorsTranslatorsTranslatorsSlide12
Proposal
Core RF2 Tables
RF2
TablesSlide13
Proposal
Add
Refset
Editor Extensions
RF2
Tables
Refset
Editor
Extension
Workflow management extensions installed via editorSlide14
Proposal
Add CIMI Specific Extensions
RF2
Tables
Refset
Editor
Extension
CIMI
Specific
Extensions
Where possible, would be RF2
Refset
Format
Would include non-SCT value sets and content linksSlide15
Proposal
Host on internet service
RF2
Tables
Refset
Editor
Extension
CIMI
Specific
Extensions
Could be hosting organization, Amazon Cloud, Mayo (via Amazon Cloud)
Basic security and backup
Mirrors would be possible (or even desirable?)Slide16
Refset Editor
RF2
Tables
Refset
Editor
Extension
CIMI
Specific
Extensions
RefsetEditor
RefsetEditor
RefsetEditor
Issues:
RefsetEditor
doesn’t actually (directly) create RF2 Content! RefsetEditor takes RF2 Tables as input Still a tad on the buggy side but… (Both issues are fixable but will take time)Slide17
Terminology Services
RF2
Tables
Refset
Editor
Extension
CIMI
Specific
Extensions
CTS2 Server
CTS2 Server
Other Server
MySQL Client
Servers could be:
centrally hostedclient basedSlide18
Authoring Tools
RF2
Tables
Refset
Editor
Extension
CIMI
Specific
Extensions
IHTSDO
Workbench
IHTSDO
Workbench
Snow Owl
QA Subsumption, ToolingWB Backing StoreIM ToolingMechanisms of InterchangeDirect SQL QueriesCTS2 or other API’sDelta import and exportComplete file import and exportSlide19
Proposal
(Shorter Term)
Terminology “model” and backing store is enhanced RF2
Exchange can be one of:
Direct update to RF2 data base (trusted apps)
RF2 Delta Imports (and Exports)
CTS2 Update Packages
Multiple authoring tools can be used depending on environment
Authoring tools are responsible for synchronization w/ backing store
May involve scripting and work in some casesSlide20
Proposal
(Shorter Term)
Clients may
Access SQL tables directly
We may augment with
Lucene
and other helpers
Use CTS2 API
Use any other API that works against backing storeSlide21
Possible Enhancement?
RF2
Tables
Refset
Editor
Extension
CIMI
Specific
Extensions
Triple
StoreSlide22
Snow Owl
B2i could provide:
Terminology
server to meet the REST and web browsing requirement and export CIMI data
Second
server to support collaborative authoring & issue tracking
Snow
Owl authoring license restricted to CIMI’s namespace, and
Support
and maintenance for the above.Slide23
Topic 2
Information Modeling
Logical Model Designer (Snow Owl)
and/
or
Subset of AOM (LOM) w/ additional constructs
Serialization
Ecore
Classes (LOM XMI file)
Need LOM transformation tools
MDHT
UML tooling and/
or
Needs significant work to produce ADL 1.5
Ocean ADL workbench and/orNeeds significant work to edit ADL 1.5Excel + duct-tape and/orMindmaps + duct-tape and/orOthers?Slide24
Set of “big ticket” (must have) requirements for modeling tools in order to get started
Separate the capabilities of the tools from the underlying storage formatsSlide25
Topic 2
Information Modeling
Question: Can we take an approach similar to that proposed for Terminology?Slide26
Information Model Ideas
#
26
Repository of Shared
Models in
a Single Formalism
DCMs
CDA
Templates
openEHR
Archetypes
CEN
Archetypes
LRA
ModelsCMETs, HMDsRMIMsCEMsStandardTerminologiesInitial Loading of RepositoryRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsRealm Specific SpecializationsV2 “|”HTMLUMLADLV2 XMLV3 XMLV3 NextCEN ArchetypeCDASOAPayloadCEMLRAOWLCDISC SHARETranslatorsTranslatorsTranslatorsSlide27
Information Modeling
What would be the “store” and medium of interchange?