Difference between revisions of "2017 Winter Project Week/SimplePowerfulBeautifulMedicalVisualizerWithAMI"
| (6 intermediate revisions by the same user not shown) | |||
| Line 18: | Line 18: | ||
==== Web components ==== | ==== Web components ==== | ||
| − | A collection of web components [3] (via Polymer [4]) | + | A collection of modular web components [3] (via Polymer [4]) that people can cherry pick to easily build their own web medical visualizer. |
| − | Why Polymer? (and not React [5] or Angular [6]) | + | |
| − | Because | + | ''Why Polymer? (and not React [5] or Angular [6])'' |
| + | |||
| + | Because Polymer is meant to '''disappear'''! | ||
| + | |||
| + | Polymer adds very little 'sugar' on top of the web '''standards'''. It mostly adds support for some features that are not available '''yet''' on some platforms. Once all browser vendors implement the standards, the Polymer library that aims to poly-fill all the gaps will disappear. Accessibility is also very important: one can use web components in its app no matter which framework is used. Using React/Angular-based elements from another framework is not necessarily possible. Low maintenance cost (not tied to a specific version of a specific library). Beautiful ecosystem for development, testing and distribution. | ||
| + | |||
| + | - and it is a Google backed project! | ||
{| class="wikitable" | {| class="wikitable" | ||
Latest revision as of 11:13, 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. The key to the XTK success was its simple interface that lets people just dive in without worrying about the details.
Web components
A collection of modular web components [3] (via Polymer [4]) that people can cherry pick to easily build their own web medical visualizer.
Why Polymer? (and not React [5] or Angular [6])
Because Polymer is meant to disappear!
Polymer adds very little 'sugar' on top of the web standards. It mostly adds support for some features that are not available yet on some platforms. Once all browser vendors implement the standards, the Polymer library that aims to poly-fill all the gaps will disappear. Accessibility is also very important: one can use web components in its app no matter which framework is used. Using React/Angular-based elements from another framework is not necessarily possible. Low maintenance cost (not tied to a specific version of a specific library). Beautiful ecosystem for development, testing and distribution.
- and it is a Google backed project!
| Objective | Approach and Plan | Progress and Next Steps |
|---|---|---|
|
|
|
