⚙️ Administration

User Management

The User Management module (available to users with ROLE_ADMIN) lets you create, edit, and manage all users in your organization.

Creating a New User

1. Navigate to User Management from the sidebar
2. Click Add User
3. Enter username, email, and password
4. Select the user's role: Admin, Doctor, Lab, Display, or HealthCIP Admin
5. Assign the user to an organization
6. Save — the user can now log in with their credentials

User Roles Reference

Role	Database Value	Capabilities
Admin	ROLE_ADMIN	User management, org settings, master data, full system access
Doctor	ROLE_DOCTOR	Consultations, prescriptions, appointments, queue, AI features
Lab Technician	ROLE_LAB	Investigation entry, lab report management
Display	ROLE_DISPLAY	View-only queue display for waiting areas
HealthCIP Admin	ROLE_HEALTHREPO_ADMIN	Multi-org management, system-wide master data, super admin functions

Editing Users

You can update user information, reset passwords, and change roles from the User Management screen. The system uses JWT-based authentication with refresh token support for secure sessions.

Forgot Password Flow

Users who forget their password can use the Forgot password? link on the login page. This triggers an email via AWS SES with a reset link. The flow is:

1. User enters their registered email on the forgot password page
2. System sends a password reset link via AWS SES
3. User clicks the link and enters a new password
4. Password is hashed and updated — user can log in with the new password

Organization Settings

Each organization can configure its own settings. Access this from Organization > Settings.

Configurable Settings

• Organization Name — Display name for the hospital/clinic
• Contact Information — Address, phone, email
• Branding — Logo and color scheme (Enterprise plan)
• Master Data Defaults — Pre-selected medicines, symptoms, etc.
• Consultation Fee Defaults — Default fee structures for new doctors
• Notification Settings — Email notification preferences

Multi-Organization Management

The Enterprise plan supports multiple organizations under a single HealthCIP installation. This is ideal for hospital chains or for SaaS providers hosting multiple clinics.

How Multi-Org Works

• Each organization has its own isolated data (patients, doctors, appointments)
• Master data can be shared system-wide or customized per organization
• Users are assigned to specific organizations
• ROLE_HEALTHREPO_ADMIN can view and manage all organizations
• Regular admins see only their own organization's data

Adding an Organization

1. Log in as a HealthCIP Admin
2. Navigate to Organizations
3. Click Add Organization
4. Enter organization name, address, and contact details
5. Configure initial settings and master data
6. Save — the organization is ready for user creation

Master Data Administration

Master data can be managed at two levels:

System-Level Master Data (HealthCIP Admin)

Changes made at the system level apply to all organizations. This includes medicines, drug families, symptoms, and other clinical reference data. Access from System Master Data in the sidebar.

Organization-Level Master Data (Admin)

Each organization can override or extend the system master data. For example, you can add medicines specific to your hospital's pharmacy while keeping the system-wide medicine list as a base. Access from the Master menu.

Pre-Loaded Seed Data

HealthCIP comes with comprehensive seed data that is loaded during initial setup:

Seed File	Contents
drug_family.json	Drug family classifications
medicine.json	500+ medicine entries with drug family associations
symptom.json	200+ common symptoms
department.json	30+ hospital departments
dosage.json	Standard dosage strengths
interval.json	Dosing frequency intervals
duration.json	Treatment durations

System Initialization

On first startup, HealthCIP automatically initializes:

• Default admin user (MasterUserInitializer)
• Seed master data from JSON files
• Default organization configuration

Security Configuration

HealthCIP uses Spring Security for authentication and authorization:

• Authentication: JWT-based with access and refresh tokens
• Authorization: Role-based access control (RBAC) at the API level
• Password Storage: BCrypt password hashing
• CORS: Configurable cross-origin policy
• API Security: Endpoints are protected by role; Swagger UI can be toggled

File Storage

HealthCIP uses AWS S3 for document and file storage. This includes:

• Lab report uploads (PDF, images)
• Patient document attachments
• X-Ray and imaging files

AWS client configuration is managed via the AWSClientConfig class and can be customized in the application properties.