Difference between revisions of "2017 Winter Project Week/SimplePowerfulBeautifulMedicalVisualizerWithAMI"
| Line 12: | Line 12: | ||
==Project Description== | ==Project Description== | ||
Many tools and libraries exist to build powerful '''web medical visualizers''' but the learning curve can be steep for new comers. | Many tools and libraries exist to build powerful '''web medical visualizers''' but the learning curve can be steep for new comers. | ||
| − | This project aims to provide simple | + | This project aims to provide simple interfaces for AMI [1]. |
==== Simple JS interface ==== | ==== Simple JS interface ==== | ||
Revision as of 11:01, 9 January 2017
Home < 2017 Winter Project Week < SimplePowerfulBeautifulMedicalVisualizerWithAMI
Key Investigators
- Jorge Luis Bernal Rusiel, Boston Children's Hospital
- Nicolas Rannou, Eunate Technology S.L.
- Rudolph Pienaar, Boston Children's Hospital
Project Description
Many tools and libraries exist to build powerful web medical visualizers but the learning curve can be steep for new comers. This project aims to provide simple interfaces for AMI [1].
Simple JS interface
A simple Javascript XTK-like [2] API
Web components
A collection of web components [3] (via Polymer [4]) will be designed and implemented.
Why Polymer? (and not React [5] or Angular [6]) Because it is meant to disappear! Polymer just add very little 'sugar' on top of the web standards. It mostly adds support for some features that are not available on simple platforms yet. Ultimatly all browser vendors will implement all the standards and the Polymer library that aims to poly-fill all the gaps will disappear. Accessibility is very important too: one can use web components for its app no matter which framework is used. Using React/Angular elements from another framework is not necessarily possible.
| Objective | Approach and Plan | Progress and Next Steps |
|---|---|---|
|
|
|
