How trifork/fut-web-client works
Main Components
• Web Browser / User: Representing the client devices from where users access the Angular application.
• Angular Web Client: A large component encompassing the “client” folder where all the Angular code is encapsulated. This includes modules for FHIR (e.g., patient, appointment, organization, etc.), user management, notification, context-bar, and other UI elements.
• Web Server - NGINX: As identified in the file tree (the “nginx” folder with config templates), NGINX serves the static files built by Angular and also functions as a reverse proxy to route API requests from the client to the backend FUT services.
• Docker Infrastructure: Encapsulate the Docker components (Dockerfile, docker-compose.yaml, and .dockerignore) which package the Angular app and NGINX configuration into deployable containers.
• External FUT Back-End / HL7 FHIR API: Although not part of this repository, the client is designed to interact with external FUT services (secured HL7 FHIR endpoints) for retrieving and storing patient-related data (appointments, care teams, organizations, etc.).
Relationships & Interactions to Display
• The Angular app communicates with the NGINX server for fetching its static assets.
• API calls originating from the Angular client are forwarded to the external FUT HL7 FHIR API by the NGINX reverse proxy.
Architectural Patterns & Design Principles
• Separation between client-side architecture (Angular, Keycloak JS) and deployment/infrastructure (NGINX, Docker).
• That the design is based on a Single Page Application (SPA) architecture, with modular Angular components for various FHIR data interactions.
• The use of a reverse proxy pattern in NGINX is crucial to address CORS issues – show how all API calls pass through NGINX before reaching the external FUT services.
Technologies & Frameworks to Label
• Angular (client-side framework)
• NGINX (web server and reverse proxy)
• Docker & Docker Compose (containerization and orchestration)
• Keycloak (for authentication/SSO)
• HL7 FHIR API – external telemedicine service backend