How adefrutoscasado/recist-app works
Project type & purpose
• Recist-App is a single-page full-stack web application (SPA) for interactive tumor measurement in medical images, following RECIST standards.
• The front end is built with Polymer Web Components and the AMI medical-imaging JS toolkit. The back end is a minimal Node.js/Express server for static file hosting.
File-structure analysis
• Top-level:
• app.js & bin/www – Express HTTP server entrypoint
• public/ – all client assets (HTML, Web Components, Polymer/Bower dependencies, AMI examples)
• package.json – Node and build dependencies
• public/ contains:
• ami-app.html – main SPA shell
• bower_components/ – Polymer library & AMI toolkit & auxiliary components
• components/ – custom Polymer elements (ami-loader2.html, ami-viewer2.html, ami-widget2.html)
Key README insights
• The app imports DICOM images from remote URLs or local storage, processes them client-side with AMI, and overlays lesion measurements in a Polymer-based UI.
• No database or REST API is mentioned, so all image parsing and analysis runs in the browser.
a. Main components
• Client Browser (SPA)
– Polymer Web Components (custom elements)
– AMI Toolkit (DICOM/NIfTI loader, viewer, renderer, measurement widgets)
• Static File Server
– Node.js + Express (app.js)
• External Data Sources
– Remote DICOM servers (HTTP URLs)
– User’s local filesystem (File API)
b. Relationships & interactions
1. User → Browser SPA UI
2. SPA → Express Server (HTTP GET static assets)
3. User action “Import” → Browser fetches DICOM via HTTP from remote URL or reads local file
4. AMI in browser parses & renders DICOM, provides image stacks to viewer components
5. User marks lesions; measurement data flows from viewer components to SPA logic
6. SPA outputs final RECIST evaluation (JSON/report) or displays on UI
c. Architectural patterns & principles
• Client-heavy architecture (thin server)
• Modular component design (Polymer elements + AMI modules)
• Separation of concerns: data parsing/rendering in AMI, UI/interaction in Polymer
d. Key technologies
• Node.js, Express (static hosting)
• Polymer (Web Components)
• AMI JavaScript Toolkit (dicom/nifti loaders, volume rendering, measurement helpers)
• Bower for front-end package management