How theimperialone/setu_x works
Project type and purpose
• This is a mobile-client–server application: an Android app (“Setu_X”) for patients and hospital staff to securely store and retrieve medical history.
• The backend is Firebase (Authentication, Realtime Database or Firestore, Storage), accessed via REST/SDK calls (VolleyMultipartRequest).
File structure
• Top-level: one Gradle module (app) containing all Android code and resources.
• Package breakdown under com.imperial.setux:
• root activities (MainActivity, UserActivity, DummyActivity)
• hospital subpackage – hospital login, registration, dashboard, patient verification, add diagnosis, view history
• patient subpackage – patient login, registration, dashboard, view notifications, medical history
• medicalRecord subpackage – adapter and model for medical record list
• Network helper: VolleyMultipartRequest
• Configuration: google-services.json (Firebase), network_security_config.xml, ProGuard rules
README
• Confirms use of Android Studio and Firebase
• Unique patient identifier: Aadhaar Number
• Security: encryption, authentication
• Future integrations: Blockchain, Digilocker
Components
a. Main components
• Android App (Client)
– UI Layer (Activities & Fragments)
– Domain/Feature Modules (hospital, patient, medicalRecord)
– Network Layer (VolleyMultipartRequest, Firebase SDK)
– Local config & security (network_security_config.xml, encryption helpers)
• Backend Services (Firebase)
– Authentication Service (login/register hospital & patient)
– Database (Firestore or Realtime Database storing patient records keyed by Aadhaar)
– Storage (prescriptions, attachments)
– (Optionally) Cloud Functions for server-side logic/encryption
• External Services (future/facilitators)
– Aadhaar validation API
– Digilocker API
– Blockchain network (future)
b. Relationships & data flow
• User taps button → Activity calls domain controller → Network Layer issues request via Firebase SDK or Volley → Firebase Authentication verifies → DB read/write → Response returns → UI updates
• Secure channel layer (HTTPS/TLS) between App and Firebase
c. Architectural patterns & design principles
• Feature-based packaging: separate hospital & patient flows
• MVC/MVVM-ish: Activities as controllers, Adapters/ViewModels for lists, Models for data (Patient, MedicalRecord)
• Single‐responsibility: each Activity focuses on one screen
• Secure by design: network_security_config enforces TLS, ProGuard for obfuscation
d. Key technologies/frameworks
• Android SDK & AndroidX
• Firebase Auth, Firebase Database, Firebase Storage
• Volley (multipart requests)
• ProGuard/R8 (code shrinking)
• Gradle (build system)