How vishal343012/medicare-project works
Medical Portal POC is a synthetic-patient demo with an authenticated browser UI and a PostgreSQL-backed API. The documented request path runs through NGINX: OAuth2 Proxy delegates sign-in to Microsoft Entra ID, while the React UI calls Node.js endpoints for the user identity and patient records. The backend queries PostgreSQL for records. Edges reflect README-described routing or calls visible in the frontend/backend excerpts; NGINX and OAuth2 Proxy internals are represented from documentation/config paths, not inspected implementation.
Main entry points: medical-poc.conf NGINX routing · server.js Node.js API · oauth2-proxy.cfg.example OAuth2 Proxy · main.jsx React portal
Components 7
Access and authentication
- NGINX routing
nginx/medical-poc.conf - OAuth2 Proxy
oauth2-proxy/oauth2-proxy.cfg.example
Portal application
- React portal
frontend/src/main.jsx - Node.js API
backend/src/server.js
Patient data
- PostgreSQL records
database/schema.sql
Other components
- Browser user
- Microsoft Entra ID
Connections 8
- Browser user → NGINX routing: requests portal
README.md - NGINX routing → OAuth2 Proxy: routes auth
README.md - OAuth2 Proxy → Microsoft Entra ID: delegates sign-in
README.md - NGINX routing → React portal: serves UI
README.md - Browser user → NGINX routing: requests API
README.md - React portal → Node.js API: fetches user and patients
frontend/src/main.jsx - NGINX routing → Node.js API: routes API
README.md - Node.js API → PostgreSQL records: queries patients
backend/src/server.js