SkelML and KAMLs The thigh bone’s connected to the hip bone: SKELML and the development of KAMLs Rachel Ellaway and David Topps Northern Ontario School of Medicine

SkelML and KAMLs Basic Science Education is Changing From ‘know what’ to ‘know how’ –From linear didactics to matrix knowledgebases –From objects to connections - knowledge networks - nodes and vertices - both important –From specifics to abstractions - structure, pattern, models, metadata –From abstractions to specifics - instantiation, service, mashup, hybrids The function of knowledge, its creation, acquisition and representation - all in flux We need better understanding of this changing ecosystem

SkelML and KAMLs The Environment is Changing Ambient use of technology Educational informatics underpinning it all Monolithic ‘do-it-all’ systems still predominate but SOAs are growing: –Interoperability: ability of two or more systems to exchange data meaningfully –Integration: ability of two or more systems to exchange services meaningfully –Based on standards and specs - MedBiquitous, eFramework Experiments in discrete knowledge services …

SkelML and KAMLs Experiment: Knowledge Application Markup Languages (KAMLs) Simple Discrete topic area Can represent: –Content –Geography –Properties Dimensions Weight Tissue –Functions –Interactions –Dependencies

SkelML and KAMLs SkelML ulna the word ulna is a derivation of the Greek word for elbow, parallel with the radius it is the longer of the two bones, arm,forearm radius lesser sigmoid cavity styloid process humerus greater sigmoid cavity

SkelML and KAMLs Issues 3D properties difficult to model in XML without a 3D model - e.g. attachments, joints Normal variations in human anatomy - cf normal values Variations of pathology and abnormality Age/developmental issues Semantic or simply unique IDs Whether to have a single common model for all systems or separate per system models

SkelML and KAMLs Others Nerves Muscles Organs Body systems Landmarks Drugs Pathologies - ICD-9 Diagnostic models Therapeutic models Roles Processes Services

SkelML and KAMLs Joining them together … Multi-dimensional matrices Tightly coupled: –cross referenced IDs - Xpath, Xquery, Xpointer –IDs must match across models Loosely coupled: –cross referenced semantic matching –Descriptors must match (probabilistically) across models Instantiation: –Service-Oriented Clinical Knowledgebases (SOCKs) with high levels of abstraction –Rich semantic searching –Edge services

SkelML and KAMLs HSVO Edge Services HSVO: NOSM, McGill, CRC, NRC, Stanford, IDEAL,IiL CANARIE funding - NEP - UCLPs Platform Services – IaaS (Infrastructure as a Service) CCaaS (Collaboration Control as a Service) Edge devices and services: –Mannequin –Virtual patient –Physiome –GIS –Evidence –3D models Common query and exchange (?standards-based) –Using SkelML, NerveML, MuscML, OrganML …

SkelML and KAMLs HSVO Use Cases Use Case 1: Simulated Human Aggregate Patient Environment Students working with a virtual patient, data moves to and from mannequins and physionomic models, query services against knowledge and evidence Use Case 2: Virtual Dissection Room Students working with a lightfield array, communicating and collaborating, overlaying 2D and 3D images and models, bookmarking and clipping for viewing and sharing

SkelML and KAMLs HSVO Architecture

SkelML and KAMLs

Experiments Educational experiments: Completeness and representation Utility and efficacy Fluidity of knowledge access and manipulation Technical experiments: Designs, models and frameworks for SOCKs Repositioning knowledge services in a ubiquitous environment Middleware and service models

SkelML and KAMLs

KAMLs and SOCKs Simple, granular, single-subject Knowledgebase research Different levels and forms of integration Enabling other R&D Scholarship and engineering Watch this space …

SkelML and KAMLs The thigh bone’s connected to the hip bone: SKELML and the development of KAMLs Rachel Ellaway and David Topps Northern Ontario School of Medicine