1 / 70

Black Skin Dermatology Online : Contribution to teledermatology

Black Skin Dermatology Online : Contribution to teledermatology Prime Minister's office Federal office for scientific, technical and cultural affairs Multiannual information society support programme 2001-2008. Contents. General objective and partnership Project management

tiger
Télécharger la présentation

Black Skin Dermatology Online : Contribution to teledermatology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Black Skin Dermatology Online : Contribution to teledermatology Prime Minister's office Federal office for scientific, technical and cultural affairs Multiannual information society support programme 2001-2008

  2. Contents • General objective and partnership • Project management • Feasibility study • Content acquisition • Platform Prototype • Demo • Second phase

  3. General objective • To establish an experimental web platform of teledermatology on black skin, multilingual and open, integrating image and voice recognition technologies. • Phase 1 • Development of a prototype • Build a representative corpus in dermatology on black skin • Phase 2 • Development of telematics services related to the database. • Evaluation of the prototype, including its usability

  4. Partnership • Five partners • Contents and medical expertise • Definition of the functionalities of the platform • Guarantee scientific reliability of the database • Testing • Centre hospitalier régional de Kaolack (Sénégal) • Hôpital Erasme • Institut de médecine tropicale Prince Léopold • Universiteit Gent • Universiteit Antwerpen (UIA) • A coordinator • Realize data-processing analysis and developments • Plan partner ’s action in the study of the needs, the functional analysis and the evaluation of the prototype • Université Libre de Bruxelles

  5. Advisory committee • Dermatologists • Expert in voice technology • Expert in information technology • Feedback on various issues

  6. Project management (1) • Successful follow-up of tasks during the project • State of art (months 1-6) • Study of needs (months 1-6) • Feasibility study (months 6-12) • Development of a prototype (months 12-24) • Content acquisition and alpha-tests (months 1-24) • Project management (months 1-24) • Supervision of four activity reports • Creation and regular updates of a Web site (http://www.bib.ulb.ac.be/RDIB/Blackskin/index.htm)

  7. Project management (2) • Organization of twelve working meetings among partners • Organization of two advisory committee meetings • Conclusion of a subcontract with the expert in vocal recognition for a state of the art and a feasibility study

  8. Feasibility study • Covers: • Study of needs • Metadata of the images • Software overview and choices • To efficiently store and retrieve the images • To deliver content to the end-user • Voice recognition

  9. > Feasibility StudyStudy of needs (1) • Phase 1 : • Online image database • Comprehensive description of images • Image submission through Web interface, with appropriate authentication mechanisms • Interoperable • Data protection mechanisms • Integration of voice recognition technologies, if feasible • Content management system • Free and open-source software

  10. > Feasibility StudyStudy of needs (2) • Phase 2 : • Image database • Continuous development of image collections • Possibility to add comments on already existing images • Collection export onto self-contained CD-ROM for offline browsing • Prototype evaluation • Added-value services in the CMS: • Expert’s forum • « Ask a specialist » service • Teaching support (didactic quizzes, integration in e-courses, …) • Technological watch • Collaboration with other existing projects in telemedecine and teledermatology

  11. > Feasibility StudyMetadata of the images (1) • based on other existing atlases • Dermis/DOIA (Dermatology Online atlases) • Dermatology image bank (“Knowledge weavers” University of Utah) • Knowledge Lumen University of Chicago • Dermatlas (Johns Hopkins University) • Atlas Tunisien de Dermatologie online • ULB image library • MS-Access prototype to determine required fields

  12. > Feasibility StudyMetadata of the images (2)

  13. > Feasibility StudyMetadata of the images (3)

  14. > Feasibility StudyMetadata of the images (4) • Thesaurus • Study of MESH, ICD-10, CISP-2, UMLS • Based on ICD-10 (WHO’s International Classification of the Diseases): 10th version of the nomenclature created in 1893. • Descriptive structure of pathologies in 5 levels. • Contains more than 2000 terms coming from all the chapters from the standard. • Translation in NL, FR, EN and DE. • Interoperability with other systems that use PubMed classification (Dermis, Dermatlas, …) and with the CISP-2, UMLS and MESH standards.

  15. > Feasibility StudyMetadata of the images (5)

  16. > Feasibility StudySoftware • Content management system • Digital library software • Characteristics • Open-source • Interoperable • Maintainable

  17. > Feasibility studyContent Management System (1) • Definition “A content management system (CMS) supports the creation, management, distribution, publishing, and discovery of corporate information. It covers the complete lifecycle of the pages on your site, from providing simple tools to create the content, through to publishing, and finally to archiving. It also provides the ability to manage the structure of the site, the appearance of the published pages, and the navigation provided to the users. […]” (http://www.steptwo.com.au/papers/kmc_what/) • Lots of competitors: • 350+ CMS on http://www.cmsreview.com • Requirements • Open-source • Localization  multilingual • Plug in API

  18. > Feasibility studyContent Management System (2) • Comparison of 4 CMS: • Magnolia/OpenCMS/Mambo/Typo3 • Our Choice: Typo3 • Rapid prototyping • Hundreds of available plug-ins • Forum • News management • News letter • Quiz • Active community (+3000 registered sites) • Rich documentation

  19. > Feasibility studyContent Management System (3)

  20. > Feasibility StudyImage Database (1) • Dspace • Java • Workflow Management • Indexed fields are hard-coded • Greenstone 2.52 • lots of desirable features • lack of powerful communication interface for our CMS • building process requires the whole collection to be rebuilt each time • Home-made solution • blackskin specific • cost • seriously investigated before announcement of…

  21. > Feasibility StudyImage Database (2) • Greenstone 3 • complete redesign of Greenstone 2 structured as a network of independent modules that communicate with XML • collections are backward compatible • written in Java → servlet • new incremental collection building process • quicker • more flexible • SOAP interface • still alpha release

  22. > Feasibility StudyImage Database (3) • Interoperability • Major concern • SOAP interface • Open Archives Initiative • Z39.50 • Seamless integration in existing digital library systems

  23. > Feasibility StudyVoice Recognition (1) • Experts recommended to adopt an already existing software solution rather than a home-made one. • Cost • Integration problems • 2 widely available software solutions were benchmarked • IBM ViaVoice vs Dragon Naturally Speaking • Dragon was available in all 3 languages required (FR, NL & EN) • Dragon proved to be the clearest and the most user friendly.

  24. > Feasibility StudyVoice Recognition (2) • Experts’ general conclusions: • Integration of voice recognition techniques in Blackskin not as easy as it first seemed. • Voice recognition is definitely not appropriate to fill in forms such as those requested by Blackskin • Much slower encoding • Discouragement of users • But we wanted to confirm the experts’ conclusions by conducting empirical tests.

  25. > Feasibility Study Legal aspects • No specific Belgian legal directives for image databases but: • Law of 8 december 1992 with respect to “the protection of privacy in processing data of a person”. • Ordre des Médecins: «Recommandations relatives à la tenue de bases de données médicales contenant des données nominatives ou identifiables» http://www.ordomedic.be/web-Fr/fr/a97/a097008f.htm • Blackskin does not contain any personal information of the patients (except for age and gender). • Draft of license agreement in which submitter gives away all his rights over the images to Blackskin

  26. Content acquisition • Scanning of existing slides • 400 slides selected and scanned • from which 300 are completely described and available in the prototype • Picture acquisition in Senegal • 1800 pictures • from which 600 are suitable for inclusion in the prototype • 300 completely described and ready for upload

  27. Prototype Development • Software architecture • Web site structure • Typo3 plugin • Greenstone3 configuration • Backend

  28. > Prototype developmentSoftware Architecture • Open-source components • Typo3 plug-in and GSDL3 backend

  29. > Prototype developmentWeb site structure (1)

  30. > Prototype developmentWeb site structure (2) • Home • Welcome message • Short presentation • # of pictures

  31. > Prototype developmentWeb site structure (3) • Search pages • Browsing tools • ICD10 • Description • Body site • (Homunculus) • (New Images) • Site search

  32. > Prototype developmentWeb site structure (4) • Information about: • Project • ICD10 classification • Staff • Contributors • Disclaimer

  33. > Prototype developmentWeb site structure (5) • Tools • Submit an image • Contact maintainers • Forums • Newsletter subscription • Links page

  34. > Prototype developmentWeb site structure (6) • Teaching • Ask a specialist • Pedagogic cases and quizzes • Bibliography • CD-ROM order

  35. > Prototype developmentWeb site structure (7) • Help • Technical help • FAQ • Sitemap

  36. > Prototype developmentTypo3 plug-in (1) • Handles communication between Typo3 and Greenstone3 through SOAP calls • Fully configurable • Configuration files • TypoScript • Problem • Lack of documentation about available messages and options • Solution: use of tcpTunnelGui and demo collection to analyze messages

  37. > Prototype developmentTypo3 plug-in (2) • GSDL3 can query remote installations

  38. > Prototype developmentTypo3 plug-in (3) • Features: • Search a given index • Browse hierarchical classifiers • Multilingual support • Look and feel can be adjusted using CSS • Flexible but could be more generic

  39. > Prototype developmentGreenstone 3 (1) • Using latest version from CVS • Problem • Lack of up-to-date documentation for installation • Alpha software • Solution: Live with it!

  40. > Prototype developmentGreenstone 3 (2) • Collection configuration • One collection for each partner • Inherent to GSDL building process • One supercollection • Indexes for searching • For each searchable field • Hierarchical classifiers • Body site • Used by homunculus • Contributor • Diagnostic • Description • ICD10

  41. > Prototype developmentGreenstone 3 (3) • 1 supercollection • 1 collection / partner

  42. > Prototype developmentConfiguration files (1) • Used to populate drop down menus and to configure classifiers • Automatically generated from Excel files • Easily maintainable • Depending on their nature, generated by: • Java application • XSLT

  43. > Prototype developmentConfiguration files (2)

  44. > Prototype developmentConfiguration files (3)

  45. > Prototype developmentConfiguration files (4)

  46. > Prototype developmentConfiguration files (5)

  47. > Prototype developmentBackend (1) • New user-friendly GSDL3 backend • J2EE servlets and JSP • Motivation • 2 existing means • Collector • Web-based interface • Too limited • Greenstone Librarian Interface • Java application • Effectively allows users to upload, modify and build collections

  48. > Prototype developmentBackend (2) • GLI screenshot

  49. > Prototype developmentBackend (3) • Motivation • Why? • Must be run on same computer • Solution: applet but... not always available • No preview mechanism • need for a second application • Difficult speech recognition integration • Graphical layout harder to modify than HTML

  50. > Prototype developmentBackend (4)

More Related