CIMI “Terminology” Meeting

CIMI “Terminology” Meeting

Agenda

• Terminology Tooling Proposal• Information modelling tooling (requirements,

options and selection process) (if time)• Tooling framework and other tooling

requirements (if time)

Terminology Tooling

Terminology Tooling Puzzle

Query and BrowsingProgrammatic APICollaborative AuthoringIssue Tracking


Query and Browsing– Concepts, Value Sets, Maps, etc.

Web BrowserSnow OWL LiteCTS2 Clients and WidgetsitServer (?)(other)Web Protege


Programmatic API (REST or SOAP?)• Snow OWL Server• Ocean’s terminology server• Apelon DTS• CTS2• SPARQL• SQL• (other?)• (SNOMED Query Specification)


Collaborative Authoring• IHTSDO Workbench / Kaiser Extensions

– (hosting?)– SVN

• Snow OwlRefset Creation• Snow OWL• IHTSDO refset creation tool (for SNOMED refsets)• IHTSDO Workbench / Kaiser Extensions• (others)

Remembering our Vision…

. . .

Service

Interface

Data

Application

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 applications

Information Model Ideas

# 10

Repository of SharedModels in

a Single Formalism

DCMs

CDA Templates

openEHRArchetypes

CENArchetypes

LRA Models

CMETs, HMDsRMIMs

CEMs

StandardTerminologies

Initial Loading of Repository

Realm Specific

SpecializationsRealm

Specific Specializations

Realm Specific



Realm Specific

Specializations

V2 “|”

HTML

UML

ADL

V2 XML

V3 XMLV3 Next

CEN Archetype

CDA

SOAPayload

CEMLRA

OWLCDISC SHARE

TranslatorsTranslatorsTranslators


# 11


a Single Formalism

DCMs

CDA Templates

openEHRArchetypes

CENArchetypes

LRA Models

CMETs, HMDsRMIMs

CEMs



Realm Specific



Realm Specific



Realm Specific

Specializations

V2 “|”

HTML

UML

ADL

V2 XML

V3 XMLV3 Next

CEN Archetype

CDA

SOAPayload

CEMLRA

OWLCDISC SHARE


ProposalCore RF2 Tables

RF2Tables

ProposalAdd Refset Editor Extensions

RF2Tables

RefsetEditor

Extension

Workflow management extensions installed via editor

ProposalAdd CIMI Specific Extensions

RF2Tables

RefsetEditor

Extension

CIMISpecific

Extensions

Where possible, would be RF2 Refset FormatWould include non-SCT value sets and content links

ProposalHost on internet service

RF2Tables

RefsetEditor

Extension

CIMISpecific

Extensions

Could be hosting organization, Amazon Cloud, Mayo (via Amazon Cloud)Basic security and backupMirrors would be possible (or even desirable?)

Refset Editor

RF2Table

s

Refset

Editor

Extensio

n

CIMISpeci

ficExtensions

RefsetEditorRefsetEditor

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)

Terminology Services

RF2Table

s

Refset

Editor

Extensio

n

CIMISpeci

ficExtensions

CTS2 Server CTS2 Server

Other Server

MySQL ClientServers could be:• centrally hosted• client based

Authoring Tools

RF2Table

s

Refset

Editor

Extensio

n

CIMISpeci

ficExtensions

IHTSDOWorkbench

IHTSDOWorkbench

Snow Owl

QA Subsumption

, Tooling

WB Backing

Store

IM ToolingMechanisms of Interchange• Direct SQL Queries• CTS2 or other API’s• Delta import and export• Complete file import and export

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 cases

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 store

Possible Enhancement?

RF2Tables

RefsetEditor

Extension

CIMISpecific

Extensions

TripleStore

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.

Topic 2Information 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/or– Needs significant work to edit ADL 1.5

• Excel + duct-tape and/or• Mindmaps + duct-tape and/or• Others?

• 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 formats

Topic 2Information Modeling

• Question: Can we take an approach similar to that proposed for Terminology?


# 26


a Single Formalism

DCMs

CDA Templates

openEHRArchetypes

CENArchetypes

LRA Models

CMETs, HMDsRMIMs

CEMs



Realm Specific



Realm Specific



Realm Specific

Specializations

V2 “|”

HTML

UML

ADL

V2 XML

V3 XMLV3 Next

CEN Archetype

CDA

SOAPayload

CEMLRA

OWLCDISC SHARE


Information Modeling

• What would be the “store” and medium of interchange?

Documents

CIMI “Terminology” Meeting