How jit-1836/medical-report-ai works
This is a small Express/EJS medical-report UI prototype. A user opens the report-upload page, loads or enters report text, and submits it; the browser checks for a minimum length, stores the text in localStorage, then attempts to navigate to patient context, where chips can be toggled. The server also renders a home page and serves frontend assets. The README is empty, and template contents were not sampled; the context navigation target in the client does not match the server’s registered route, so that transition is shown as attempted rather than verified.
Main entry points: app.js Express routes · upload.js Report entry · patient-context.ejs Context page · patient-context.js Context chips
Components 8
Web server
- Express routes
app.js - Home page
frontend/main.ejs
Report intake
- Upload page
frontend/upload.ejs - Report entry
public/upload.js - Browser storage
Patient context
- Context page
frontend/patient-context.ejs - Context chips
public/patient-context.js
Other components
- User
Connections 10
- User → Express routes: requests pages
- Express routes → Home page: renders /home
app.js - Express routes → Upload page: renders /upload
app.js - Express routes → Context page: renders /patient-context
app.js - Express routes → Report entry: serves static files
app.js - Express routes → Context chips: serves static files
app.js - User → Report entry: enters report
public/upload.js - Report entry → Browser storage: stores report text
public/upload.js - Report entry → Context page: attempts redirect
public/upload.js - User → Context chips: clicks chips
public/patient-context.js