CIMI “Terminology” Meeting

1. CIMI “Terminology” Meeting

2. Agenda • Terminology Tooling Proposal • Information modelling tooling (requirements, options and selection process) (if time) • Tooling framework and other tooling requirements (if time)

3. Terminology Tooling

4. Terminology Tooling Puzzle Query and Browsing Programmatic API Collaborative Authoring Issue Tracking

5. Terminology Tooling Puzzle Query and Browsing – Concepts, Value Sets, Maps, etc. Web Browser Snow OWL Lite CTS2 Clients and Widgets itServer (?) (other) Web Protege

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

7. 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)

8. Remembering our Vision… . . . Application Interface Service Data

9. 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

10. Information Model Ideas V2 “|” CEM Standard Terminologies LRA V2 XML HTML CEMs V3 XML V3 Next DCMs Repository of Shared Models in a Single Formalism Realm Specific Specializations UML Realm Specific Specializations CDA Templates Realm Specific Specializations Translators Realm Specific Specializations Translators Realm Specific Specializations Translators ADL openEHR Archetypes CDA OWL CEN Archetypes SOA Payload LRA Models CDISC SHARE CMETs, HMDs RMIMs CEN Archetype Initial Loading of Repository

11. Information Model Ideas V2 “|” CEM Standard Terminologies LRA V2 XML HTML CEMs V3 XML V3 Next DCMs Repository of Shared Models in a Single Formalism Realm Specific Specializations UML Realm Specific Specializations CDA Templates Realm Specific Specializations Translators Realm Specific Specializations Translators Realm Specific Specializations Translators ADL openEHR Archetypes CDA OWL CEN Archetypes SOA Payload LRA Models CDISC SHARE CMETs, HMDs RMIMs CEN Archetype Initial Loading of Repository

12. ProposalCore RF2 Tables RF2 Tables

13. ProposalAdd Refset Editor Extensions RF2 Tables Refset Editor Extension Workflow management extensions installed via editor

14. ProposalAdd 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 links

15. ProposalHost 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?)

16. Refset Editor RefsetEditor RefsetEditor RF2 Tables Refset Editor Extension CIMI Specific Extensions 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)

17. Terminology Services CTS2 Server RF2 Tables Refset Editor Extension CIMI Specific Extensions CTS2 Server Other Server MySQL Client • Servers could be: • centrally hosted • client based

18. Authoring Tools IHTSDO Workbench IHTSDO Workbench Snow Owl WB Backing Store RF2 Tables Refset Editor Extension CIMI Specific Extensions QA Subsumption, Tooling IM Tooling • Mechanisms of Interchange • Direct SQL Queries • CTS2 or other API’s • Delta import and export • Complete file import and export

19. 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

20. 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

21. Possible Enhancement? Triple Store RF2 Tables Refset Editor Extension CIMI Specific Extensions

22. 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.

23. 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?

24. 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

25. Topic 2Information Modeling • Question: Can we take an approach similar to that proposed for Terminology?

26. Information Model Ideas V2 “|” CEM Standard Terminologies LRA V2 XML HTML CEMs V3 XML V3 Next DCMs Repository of Shared Models in a Single Formalism Realm Specific Specializations UML Realm Specific Specializations CDA Templates Realm Specific Specializations Translators Realm Specific Specializations Translators Realm Specific Specializations Translators ADL openEHR Archetypes CDA OWL CEN Archetypes SOA Payload LRA Models CDISC SHARE CMETs, HMDs RMIMs CEN Archetype Initial Loading of Repository

27. Information Modeling • What would be the “store” and medium of interchange?