Hospital OS

Multi-tenant SaaS platform for hospitals — AI-powered HMS with DICOM, LIS, and clinical workflows

Comprehensive User Documentation

Last updated: April 2026

Introduction

Welcome to Hospital OS, a multi-tenant SaaS platform for hospitals: each facility runs as its own isolated organization while you operate a single shared deployment. The product is a comprehensive hospital management system (HMS) with built-in DICOM and LIS device integration. It combines core modules (patients, appointments, reports, laboratory, inpatient, radiology/imaging, pharmacy, inventory, billing, documents, emergency, telemedicine, ambulance) with direct connectivity to laboratory analyzers and imaging equipment, plus AI-assisted tools to support clinical workflows.

Key Benefits:

  • Hospital-grade tenancy: Per-organization data isolation; staff work from a dedicated hospital subdomain
  • Platform operations: Optional Stripe-backed subscription signup, plans, and hospital self-service billing
  • Streamlined patient management and record keeping
  • Intelligent appointment scheduling and optimization
  • LIS Integration: Connect hematology, biochemistry, and other lab analyzers via HL7/FHIR/ASTM
  • DICOM Integration: Connect CT, MRI, X-ray, ultrasound, and other imaging modalities
  • Documents, emergency, telemedicine, and ambulance modules
  • AI-powered medical assistance and image analysis
  • Comprehensive reporting and analytics
  • Secure data management with role-based access and hashed passwords

Multi-Tenant SaaS for Hospitals

Hospital OS is designed so each hospital (or health system unit) is a tenant: one shared application, many organizations. Patient records, staff, devices, inventory, and settings belong to an organization and are not visible across tenants.

How you access the app

  • Hospital URL (subdomain): Staff and day-to-day HMS use https://<tenant-slug>.hospitalos.net — for example cityhospital.hospitalos.net. The host identifies the hospital; sessions are tied to that organization.
  • Apex / marketing site: The root domain often hosts public pages and self-serve hospital signup (when Stripe and plans are configured).
  • Local development: With NEXT_PUBLIC_ROOT_DOMAIN=localhost, use URLs like http://demo.localhost:3000 for a tenant (many browsers resolve *.localhost automatically).

Roles

  • Platform superadmin: Operates the whole SaaS deployment (plans, tenants, platform-wide tools). Signs in from the apex host, not a hospital subdomain. Hospital staff APIs reject superadmin sessions — use the platform admin console instead.
  • Hospital admin, doctors, staff, nurses, etc.: Sign in on their hospital’s subdomain. The server checks that the signed-in user’s organization matches the tenant on the host.
  • Patients (portal): Use the same hospital subdomain as the organization that holds their record.

Subscriptions (optional): When Stripe is configured, hospitals can subscribe via checkout; plans are managed under Platform → Plans (Stripe products/prices are created for you). If a subscription lapses, non-admin users may be blocked until the hospital administrator renews under Settings → Billing.

Patient-facing clinical billing (invoices and payments inside the HMS) is separate from this platform subscription — see the Billing section.

Migrating an existing single-hospital database to multi-tenant mode is supported via scripts (for example assigning legacy data to a default organization). See project .env.example and deployment notes for NEXTAUTH_URL, AUTH_TRUST_HOST, and cookie domain when using real subdomains in production.

Technology Stack & Dependencies

This application is built with modern, secure, and up-to-date technologies. All dependencies have been updated to meet the latest security requirements and best practices.

Security Status

All packages are up-to-date with security vulnerabilities resolved:

  • ✅ 0 security vulnerabilities
  • ✅ All critical security patches applied
  • ✅ Latest stable versions installed

Core Framework

  • Next.js 15.5.9
  • React 19.2.1
  • React DOM 19.2.1
  • TypeScript ^5

Authentication & Database

  • NextAuth.js ^4.24.13
  • Mongoose ^9.0.0
  • MongoDB ^6.18.0
  • @auth/mongodb-adapter ^3.10.0
  • Optional: Stripe for multi-tenant subscription checkout, webhooks, and hospital billing in Settings (see .env.example).

UI & Styling

  • Tailwind CSS ^4
  • Lucide React ^0.555.0
  • React Hot Toast ^2.6.0

Additional Libraries

  • next-intl ^4.3.6
  • html2canvas ^1.4.1
  • jspdf ^4.0.0
  • recharts ^3.7.0
  • cookies-next ^6.1.0
  • bcryptjs ^3.0.2

Installation

Downloading from CodeCanyon

This script is available on CodeCanyon. After purchase, you'll receive:

  1. main_files.zip - The initial download package
  2. After extracting main_files.zip, you'll get ai-doctor.zip - This is the actual script file
  3. Extract ai-doctor.zip to begin installation

Prerequisites

1. Install Node.js

Download and install Node.js from the official website:

Download: https://nodejs.org/

Choose the LTS (Long Term Support) version for stability.

Verify installation:

node --version
npm --version

2. Install MongoDB

Choose one of the following options:

Option A: MongoDB Atlas (Cloud - Recommended)
  • Sign up at MongoDB Atlas
  • Create a free cluster (M0 tier available)
  • Get your connection string
Option B: Local MongoDB Installation
  • Download from MongoDB Community Server
  • Install and start MongoDB service
  • Default connection: mongodb://localhost:27017

Installation Steps

Step 1: Download and Extract Files

Download the script from CodeCanyon:

  1. Log in to your CodeCanyon account
  2. Navigate to your downloads section
  3. Download main_files.zip
  4. Extract main_files.zip to get ai-doctor.zip
  5. Extract ai-doctor.zip to your desired location

Note: After extraction, you should have a folder named ai-doctor (or similar) containing all the project files.

Navigate to the extracted folder:

cd ai-doctor

Step 2: Install Dependencies

Navigate to the project directory and install all required packages:

npm install

This will install all dependencies listed in package.json. This process may take a few minutes.

Step 3: Configure Environment Variables

Create a .env.local file in the root directory. At minimum:

MONGODB_URI=mongodb://localhost:27017/ai-doc
NEXTAUTH_URL=http://localhost:3000
NEXTAUTH_SECRET=your-secret-key-here
NEXT_PUBLIC_ROOT_DOMAIN=localhost
AUTH_TRUST_HOST=1

Environment Variables Explained:

  • MONGODB_URI: Your MongoDB connection string. For MongoDB Atlas, use: mongodb+srv://username:password@cluster.mongodb.net/ai-doc
  • NEXTAUTH_URL: Canonical base URL for auth (often the apex). With subdomains, NextAuth still relies on the real Host header — see AUTH_TRUST_HOST in .env.example.
  • NEXTAUTH_SECRET: A random secret key for encrypting JWT tokens. Generate one using: openssl rand -base64 32
  • NEXT_PUBLIC_ROOT_DOMAIN: Apex host only (no protocol), e.g. localhost in development or hospitalos.net in production — used for tenant detection from subdomains.
  • AUTH_TRUST_HOST: Set to 1 for local or self-hosted multi-tenant setups so NextAuth trusts the request host (Vercel sets an equivalent automatically).
  • Stripe (optional SaaS billing): STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, and related keys — enables self-serve hospital signup and subscription management.

Important:

  • Keep your .env.local file secure and never share it
  • GPT-4.1 API key can be configured later through the Settings → AI Settings page

Step 4: Set Up Database

Ensure MongoDB is running and accessible:

For Local MongoDB:
# Start MongoDB service
# Windows: net start MongoDB
# macOS: brew services start mongodb-community
# Linux: sudo systemctl start mongod
For MongoDB Atlas:
  • Ensure your IP address is whitelisted in Atlas Network Access
  • Create a database user with read/write permissions
  • Use the connection string provided by Atlas

Step 5: Seed Database (Optional)

Populate the database with sample data for testing:

npm run seed

This creates a demo hospital tenant (slug demo), sample patients, appointments, reports, and seeded users — see Getting Started for login URLs.

Step 6: Start Development Server

Run the application in development mode:

npm run dev

The application will start on http://localhost:3000

Success! You should see:

✓ Ready in X seconds
○ Local: http://localhost:3000

AI API Configuration

To use AI features, you need to configure an API key for GPT-4.1 through the Settings page:

Configure GPT-4.1 API Key

  1. Log in to the application
  2. Navigate to Settings → AI Settings
  3. Add your OpenAI API key for GPT-4.1:
  4. Test the connection
  5. Activate GPT-4.1 as your AI model

Production Build

To build the application for production:

# Build the application
npm run build

# Start production server
npm run start

Note: Make sure to:

  • Set NEXTAUTH_URL and NEXT_PUBLIC_ROOT_DOMAIN to match your real apex domain and DNS
  • Configure wildcard DNS (or per-tenant hosts) so hospital subdomains resolve to the app
  • Use a strong NEXTAUTH_SECRET and review cookie-domain settings for subdomain auth (see .env.example)
  • Configure production MongoDB connection string
  • Enable HTTPS for secure connections

Troubleshooting

Common Issues and Solutions

Issue: MongoDB Connection Failed
  • Verify MongoDB is running: mongosh or check service status
  • Check connection string in .env.local
  • For Atlas: Verify IP whitelist and credentials
  • Check firewall settings
Issue: Port 3000 Already in Use
  • Stop other applications using port 3000
  • Or use a different port: PORT=3001 npm run dev
Issue: Module Not Found Errors
  • Delete node_modules folder
  • Delete package-lock.json
  • Run npm install again
Issue: Build Errors
  • Clear Next.js cache: rm -rf .next
  • Check TypeScript errors: npm run lint
  • Ensure all environment variables are set
Issue: AI Features Not Working
  • Verify GPT-4.1 API key is correctly configured
  • Check API key permissions and quotas
  • Test API connection in Settings → AI Settings
  • Check browser console for error messages
Issue: Login Loop, Wrong Tenant, or “Open from your hospital subdomain”
  • Staff must use the hospital URL (e.g. https://your-slug.hospitalos.net), not another tenant’s host
  • Ensure NEXT_PUBLIC_ROOT_DOMAIN matches the apex you deploy (and AUTH_TRUST_HOST=1 locally or self-hosted)
  • Avoid mixing production cookie domain with localhost — see comments in .env.example

Available Scripts

npm run dev

Start development server with hot reload on http://localhost:3000

npm run build

Build the application for production using Turbopack

npm run start

Start the production server (requires build first)

npm run lint

Run ESLint to check code quality and find errors

npm run seed

Populate database with sample data for testing

npm run test:ai-results

Test AI results functionality

Getting Started

1. Login to Your Account

Hospitals use the tenant login URL for staff and patients — typically https://<slug>.hospitalos.net/login. The platform operator signs in as superadmin on the apex site (not on a hospital subdomain).

Demo / seed credentials (npm run seed):

  • Platform superadmin (apex): http://localhost:3000/login — superadmin@aidoc.com / password123
  • Hospital staff & admin (tenant demo): http://demo.localhost:3000/login — admin@aidoc.com, doctor@aidoc.com, or staff@aidoc.com / password123
  • Patient portal (same tenant): patient@aidoc.com / password123 on the demo host

Seeded users belong to the demo organization (slug demo). Authentication uses bcrypt-hashed passwords; there are no mock credentials in the login logic.

2. Navigate the Dashboard

After logging in, you'll be taken to the main dashboard where you can see:

  • Practice statistics and key metrics
  • Recent activities and appointments
  • Quick access to common tasks

3. Explore Features

Use the left sidebar navigation to access all features of the system, including patient management, appointments, reports, and AI-powered tools.

Dashboard

The dashboard is your central command center, providing an overview of your practice at a glance.

Statistics Cards

View key metrics including:

  • Total Patients
  • Appointments Today
  • Reports Generated
  • AI Insights

Click on any card to navigate to the related section.

Recent Activity

Track your recent actions including:

  • New patient registrations
  • Appointment bookings
  • Report generations
  • System updates

Upcoming Appointments

Quick view of your next appointments with:

  • Patient names
  • Appointment times
  • Status indicators

Quick Actions

Fast access to common tasks:

  • Add New Patient
  • Schedule Appointment
  • Generate Report

Patient Management

Manage your patient records efficiently with comprehensive patient management features.

Patient List

View all your patients in an organized list with search and filter capabilities.

  • Search patients by name, ID, or contact information
  • Filter by status, date, or other criteria
  • Quick access to patient details
  • Delete patient records from the actions menu (with confirmation)

Add New Patient

Create new patient records with comprehensive information:

  • Personal information (name, DOB, contact details)
  • Medical history and allergies
  • Insurance information
  • Emergency contacts

Patient Details

Access comprehensive patient information:

  • Complete medical history
  • Past appointments and visits
  • Prescriptions and medications
  • Test results and reports
  • Case notes and documentation

Edit Patient Information

Update patient records as needed, with full audit trail of changes.

Appointment Management

Efficiently manage your appointment schedule with advanced scheduling features.

Schedule New Appointment

  • Select patient from your database
  • Select a doctor (admin/staff can choose via searchable doctor select; doctors auto-fill to themselves)
  • Choose date and time slot
  • Set appointment type and duration
  • Add notes and reminders

View Appointments

  • Daily, weekly, or monthly views
  • Filter by status or doctor
  • Role-based visibility: doctors see only their assigned appointments; patients see only their own
  • Quick status updates
  • Patient information at a glance

Edit Appointments

  • Modify appointment details
  • Change time or date
  • Update status
  • Add or modify notes

Reschedule Appointments

  • Quick rescheduling options
  • Automatic patient notifications
  • Conflict detection
  • History tracking

Medical Reports

Create, manage, and track medical reports and test results efficiently.

Create New Report

Generate comprehensive medical reports with:

  • Patient information and test results
  • Diagnosis and findings
  • Recommendations and follow-up
  • Attachments and images

Report Management

  • View all reports in organized list
  • Filter by patient, date, or type
  • Search functionality
  • Status tracking (draft, completed, reviewed)
  • Priority-based organization

Report Actions

  • Edit existing reports
  • Download as PDF
  • Share with patients
  • Print reports

Doctors & Staff

Administrators can manage user accounts for doctors and staff. The Doctors list shows only users with the doctor role, and staff are managed via a dedicated Staff module.

Doctor Profile Fields

  • Phone, specialization, department
  • License number, qualifications
  • Years of experience, bio
  • Address, date of birth, gender

Doctor edit uses a dedicated page (not a modal).

Permissions & Safety

  • Role-based access control (admin/doctor/staff/patient)
  • Role is protected during edit to prevent accidental changes
  • Passwords are stored as bcrypt hashes (no plaintext fallback)

Inpatient Management

Manage wards, beds, and admissions. Editing is handled via dedicated pages to ensure a reliable, full-page experience.

  • Wards: list/create/edit
  • Beds: list/edit (ward assignment, type/status, notes/features)
  • Admissions: create/edit and patient assignment

Laboratory Management with LIS Integration

Complete laboratory information system with built-in LIS integration for direct connectivity to laboratory analyzers. Connect hematology, biochemistry, immunoassay, coagulation, and urinalysis analyzers for automated, bi-directional result flow. Supports industry-standard protocols including HL7 v2, FHIR R4, ASTM E1381, and REST API.

Lab Tests & Orders

  • Create new test orders and assign to patients
  • View and filter tests by status (pending, in progress, completed)
  • Enter and manage test results with normal ranges
  • View completed results and link to patient records

LIS Device Integration

Enterprise-grade Laboratory Information System connectivity:

  • Multi-Protocol Support: HL7 v2, FHIR R4, ASTM E1381/LIS2-A2, and REST API
  • Device Registration: Register analyzers with device code, manufacturer, model, serial number, and location
  • Supported Analyzers: Hematology, biochemistry, immunoassay, coagulation, urinalysis, blood gas, and more
  • Vendor Compatible: Works with Roche, Abbott, Siemens, Beckman Coulter, Sysmex, Mindray, and others
  • Secure API Keys: Generate per-device API keys for authenticated result transmission
  • Incoming Results Queue: Review, validate, and accept results with automatic patient/order mapping
  • Auto-Flagging: Critical and abnormal values automatically highlighted
  • Real-time Monitoring: Connection status, last communication, and result counts per device

LIS Device Integration Guide

Enterprise LIS Connectivity

Connect your laboratory analyzers directly to the HMS for automated, bi-directional result flow. Eliminate manual data entry, reduce transcription errors, and accelerate turnaround times.

Step-by-step instructions for connecting lab analyzers to the HMS using industry-standard communication protocols. Our LIS integration supports equipment from all major manufacturers.

Supported Communication Protocols

REST API

HTTP JSON API for modern middleware and custom integrations. Requires API key authentication.

FHIR R4

HL7 FHIR standard for modern LIS systems. Accepts DiagnosticReport, Observation, and Bundle resources.

HL7 v2

Industry standard messaging via MLLP (TCP port 2575). Supports ORU^R01 observation result messages.

ASTM E1381

Direct analyzer connection via TCP port 5000. Also known as LIS2-A2 protocol.

1 Register Device in HMS

  1. Navigate to Lab → Devices
  2. Click Add Device
  3. Select your device profile (manufacturer + model) from the dropdown - this auto-configures parameter mappings
  4. Enter a unique Device Code (e.g., HEM-001)
    • For HL7: Use the same value as your analyzer's MSH-3 (Sending Application)
    • For ASTM: Use the same value as your analyzer's Header sender name
  5. Enter a display name and location
  6. Click Add Device - an API key will be generated and displayed once
  7. Important: Copy and save the API key securely - it cannot be retrieved later

Protocol-Specific Setup

REST API Integration

Best for: Modern middleware, custom software integrations

  1. Configure your middleware/LIS to send HTTP POST requests to: POST https://your-hms-server/api/lab/device-results
  2. Add the API key header: X-Device-API-Key: dk_your_api_key_here
  3. Send results as JSON:
    {
      "sampleId": "LAB-240215-001",
      "analyzedAt": "2024-02-15T10:30:00Z",
      "results": [
        { "code": "WBC", "value": "7.5", "unit": "10^9/L", "flag": "N" },
        { "code": "RBC", "value": "4.8", "unit": "10^12/L", "flag": "N" }
      ]
    }
  4. Verify results appear in Lab → Incoming Results

FHIR R4 Integration

Best for: Modern LIS systems, cloud-connected devices

  1. Configure your LIS to send FHIR resources to: POST https://your-hms-server/api/fhir/Bundle Or use /api/fhir/DiagnosticReport or /api/fhir/Observation
  2. Add the API key header: X-Device-API-Key: dk_your_api_key_here
  3. Set Content-Type: Content-Type: application/fhir+json
  4. Send FHIR Bundle with DiagnosticReport and Observations
  5. Verify results appear in Lab → Incoming Results

HL7 v2 Integration (MLLP)

Best for: Most hospital analyzers (Sysmex, Beckman, Roche, Siemens, etc.)

  1. Network Setup: Ensure the HMS server port 2575 is accessible from your analyzer network
  2. Device Registration: Set the Device Code to match your analyzer's Sending Application (MSH-3 field)
    Example: If analyzer sends MSH|...|SYSMEX|LAB|..., use Device Code: SYSMEX
  3. Analyzer Configuration:
    • Host/IP: Your HMS server IP address
    • Port: 2575
    • Protocol: HL7 v2.x with MLLP framing
    • Message Type: ORU^R01 (Observation Results)
  4. Test Connection: Run a test sample and verify results appear in Incoming Results
Note: No API key needed - device is identified by the Sending Application in the HL7 message header.

ASTM E1381/E1394 Integration

Best for: Older analyzers, point-of-care devices, direct serial/TCP connections

  1. Network Setup: Ensure the HMS server port 5000 is accessible from your analyzer network
  2. Device Registration: Set the Device Code to match your analyzer's Sender Name (from Header record)
    Example: If analyzer sends H|\^&|||ANALYZER1|||..., use Device Code: ANALYZER1
  3. Analyzer Configuration:
    • Host/IP: Your HMS server IP address
    • Port: 5000
    • Protocol: ASTM E1381 / LIS2-A2
  4. Test Connection: Run a test sample and verify results appear in Incoming Results
Note: No API key needed - device is identified by the sender name in the ASTM Header record.

2 Configure Parameter Mappings

Parameter mappings convert device-specific codes to standardized test names displayed in the HMS.

  1. Go to Lab → Devices and click the View/Edit icon on your device
  2. Navigate to the Parameter Mappings tab
  3. For each parameter your device sends:
    • Device Code: The code your analyzer sends (e.g., WBC, RBC, HGB)
    • Test Name: Display name in HMS (e.g., White Blood Cell Count)
    • Unit: Measurement unit (e.g., 10^9/L)
    • Normal Range: Reference range (e.g., 4.0-11.0)
    • Critical Low/High: Values that trigger critical alerts
  4. Click Save Changes
Tip: If you selected a device profile when registering, common mappings are pre-configured. Edit as needed for your lab's preferences.

Troubleshooting

Results not appearing

  • Check firewall allows ports 2575 (HL7), 5000 (ASTM), or 3000 (HTTP)
  • Verify the Device Code matches the analyzer's sending identifier
  • Check the protocol servers are running (npm run servers)
  • Review server logs for connection or parsing errors

Parameter names show raw codes

  • Device was not matched (check Device Code matches)
  • Parameter mapping not configured for this code
  • Edit device and add the missing parameter mapping

Auto-match fails (Unmatched status)

  • Sample ID from device doesn't match any Lab Test number
  • Ensure barcode/sample ID on specimen matches the HMS test number
  • Manually match in Incoming Results if needed

Device shows "Offline"

  • No data received in last 5 minutes
  • Check network connectivity between analyzer and HMS server
  • Verify analyzer is configured and sending data

Radiology & Imaging with DICOM Integration

Complete radiology information system with built-in DICOM integration for direct connectivity to imaging equipment. Connect CT, MRI, X-ray, ultrasound, mammography, and other DICOM-compliant modalities for automated image acquisition. Supports DICOM 3.0, DICOM STOW-RS, and Modality Worklist (MWL) for seamless workflow integration.

Enterprise DICOM Connectivity

Connect your imaging equipment directly to the HMS. Receive images automatically, eliminate film/CD handling, and integrate with PACS for enterprise-wide image access.

Studies & Reports

  • Create new radiology studies and link to patients
  • View study list with modality, date, and status
  • Attach images and generate radiology reports
  • Referring doctor and comparison with prior studies
  • AI-assisted image analysis with GPT-4.1 Vision

DICOM Device Integration

Enterprise-grade DICOM connectivity for all imaging modalities:

  • Full DICOM 3.0 Compliance: Industry-standard medical imaging integration
  • Multi-Modality Support: CR, DR, CT, MRI, US, Mammography, PET-CT, C-Arm, and more
  • AE Title Configuration: Configure Application Entity titles for DICOM network routing
  • DICOM STOW-RS: Receive images via web-based STOW protocol from modern equipment
  • Modality Worklist (MWL): Push scheduled exams to imaging devices automatically
  • Vendor Compatible: Works with Siemens, GE, Philips, Canon, Fujifilm, and others
  • Incoming Images Queue: Review and assign images with DICOM tag parsing
  • PACS-Ready: Designed for integration with Picture Archiving and Communication Systems

Pharmacy

Manage medicines and pharmacy inventory. Medicine view and edit pages provide a full details screen (including stock and expiry info).

Inventory

Manage suppliers, items, and purchase orders. Supplier view/edit and purchase-order view screens are available as dedicated pages.

  • Suppliers: view and edit
  • Items: create and manage medical supplies/equipment
  • Purchase Orders: view details, items, totals, and status

Billing & Invoices

Inside the HMS, billing covers patient invoices and payments for care. Create and manage invoices; invoice edit uses a dedicated edit page for a stable, full-form workflow.

SaaS subscription (hospital ↔ platform)

Separately, as a multi-tenant SaaS product, each hospital may have a platform subscription (Stripe). Hospital administrators manage this under Settings → Billing; operators define plans under Platform → Plans and can offer self-serve signup on the apex domain when Stripe is configured. If the platform subscription is inactive, non-admin users may be blocked until an admin renews — patient invoicing inside the HMS is unrelated to that status.

Document Management

Store and manage documents (consent forms, certificates, referrals, and other files) linked to patients or general use.

  • Upload documents with title, category, and optional patient link
  • List and search documents; filter by category or patient
  • View document details and download files
  • Edit metadata or delete documents as needed

Emergency Department

Manage emergency cases with triage, quick patient lookup, and case tracking. Uses the same patient registration; no separate ER registration required.

Emergency Cases

  • Create new emergency case and link to existing patient
  • Triage priority (e.g. critical, urgent, non-urgent)
  • Chief complaint, vital signs, and triage notes
  • Attending doctor assignment

Case Management

  • List and filter cases by status and priority
  • View case details, update status and notes
  • Track disposition and follow-up

Telemedicine

Conduct virtual consultations via video, audio, or chat. Schedule sessions, use a waiting room, and issue prescriptions from within the session.

Sessions

  • Create new session: select patient, doctor, consultation type (video, audio, chat), and schedule
  • View all sessions with status (scheduled, waiting, in-progress, completed, cancelled)
  • Join consultation room with video, audio, or chat as per type
  • In-session chat and clinical notes

Waiting Room & Prescriptions

  • Waiting room: see patients waiting to join; start consultation when ready
  • Create e-prescriptions during or after session (medications, diagnosis, follow-up)
  • Session linked to appointment and billing where applicable

Ambulance Services

Manage ambulance bookings and fleet. Book ambulances for patients, track assignments, and maintain vehicle and driver information.

Bookings

  • Create new booking: patient, pickup/destination, date and time, priority
  • List and filter bookings by status
  • View booking details and update status
  • Service charges and notes

Fleet Management

  • Register ambulances (vehicle number, type, status)
  • Driver assignment and availability
  • Track fleet for booking assignment

Analytical Reports

Analytical Reports pull real data from your database (not static demo values). Charts are rendered using Recharts, with CSV export available on each report screen.

Available Dashboards

  • Financial
  • Clinical
  • Operational
  • Performance
  • Patient Analytics
  • Appointment Analytics

Filters & Export

  • Date range selector (today/week/month/quarter/year)
  • Filter toggles (status/type views depending on report)
  • Export button downloads CSV for the current view

Language (i18n)

The UI supports multiple languages (English, Spanish, French). Translations are stored in JSON files under messages/.

  • Change language from Settings
  • If any text looks stale after switching, reload the page

AI-Powered Features

Hospital OS includes a comprehensive suite of AI-powered tools designed to enhance clinical workflows. These tools support diagnosis, treatment planning, risk assessment, and more.

All AI features are powered by GPT-4.1:

  • GPT-4.1 for text-based AI features
  • GPT-4.1 Vision for image analysis

AI Assistant

Your intelligent medical assistant that can help with various medical queries, patient information, and clinical decision support.

Key Features:

  • Medical Queries: Ask questions about symptoms, treatments, or medical conditions
  • Patient Information: Query patient data, medical history, and prescriptions
  • Treatment Suggestions: Get AI-powered treatment recommendations
  • Drug Information: Access medication details and interactions
  • Clinical Guidelines: Reference latest medical research and guidelines

Example Queries:

  • "What are the symptoms of diabetes?"
  • "Show me patient John Smith's medical history"
  • "What medications is patient Jane Doe currently taking?"
  • "Recommend treatment for hypertension"

AI Treatment Plans

Generate comprehensive, evidence-based treatment plans tailored to your patients' specific conditions.

Features:

  • Personalized treatment recommendations based on patient data
  • Evidence-based medicine integration
  • Medication suggestions with dosages
  • Follow-up care plans
  • Lifestyle recommendations

AI Drug Interaction Checker

Safely check for potential drug interactions before prescribing medications.

Features:

  • Check interactions between multiple medications
  • Patient-specific interaction analysis
  • Severity ratings (mild, moderate, severe)
  • Alternative medication suggestions
  • Food and supplement interaction warnings

AI Medical Image Analysis

Analyze medical images using GPT-4.1 Vision to assist in diagnosis.

Supported Image Types:

  • X-rays and radiographs
  • CT scans and MRIs
  • Ultrasound images
  • Dermatology photos
  • Pathology slides

Note: AI analysis is for assistance only and should not replace professional medical judgment.

AI Voice Input

Use voice commands to interact with the system and create medical notes hands-free.

Features:

  • Voice-to-text transcription for notes
  • Hands-free patient data entry
  • Voice commands for navigation
  • Real-time transcription
  • Multi-language support

AI Appointment Optimizer

Optimize your appointment schedule using AI to maximize efficiency and patient satisfaction.

Features:

  • Optimal time slot suggestions
  • Patient preference learning
  • Resource allocation optimization
  • Reduced wait times
  • Schedule conflict prevention

AI Risk Assessment

Assess patient risk factors and potential complications using AI-powered analysis.

Features:

  • Comprehensive risk factor analysis
  • Disease progression prediction
  • Complication risk scoring
  • Preventive care recommendations
  • Risk stratification

AI Health Analytics

Advanced analytics and insights powered by AI to improve practice outcomes.

Features:

  • Practice performance metrics
  • Patient outcome analysis
  • Treatment effectiveness tracking
  • Resource utilization insights
  • Customizable reports and dashboards

AI Symptom Analyzer

Analyze patient symptoms to assist in diagnosis and treatment planning.

Features:

  • Symptom pattern recognition
  • Differential diagnosis suggestions
  • Severity assessment
  • Recommended tests and examinations
  • Treatment pathway suggestions

AI Report Generator

Automatically generate comprehensive medical reports using AI assistance.

Features:

  • Automated report generation from patient data
  • Structured medical documentation
  • Customizable report templates
  • Multi-format export (PDF, DOCX)
  • Quality assurance checks

Settings & Profile

Profile Management

  • Update personal information
  • Change password
  • Manage contact details
  • Profile picture upload

System Settings

  • GPT-4.1 configuration
  • Notification settings
  • Language preferences
  • Display preferences
  • Data export options

AI Settings

  • Configure GPT-4.1 API key
  • Test API connection
  • Adjust AI response parameters
  • Manage AI feature preferences

Tips & Best Practices

General Tips

  • Keep patient information up-to-date for accurate AI recommendations
  • Use the search functionality to quickly find patients, appointments, or reports
  • Regularly review and update appointment statuses
  • Export important reports for backup purposes
  • Use AI features as decision support tools, not replacements for clinical judgment

AI Features Best Practices

  • Always verify AI-generated recommendations with your medical expertise
  • Use drug interaction checker before prescribing new medications
  • Review AI-generated reports before finalizing them
  • Ensure your GPT-4.1 API key is valid and has sufficient credits
  • Use voice input in quiet environments for better accuracy

Security & Privacy

  • Bookmark and use only your hospital’s official URL (correct tenant subdomain)
  • Always log out when finished, especially on shared computers
  • Keep your password secure and change it regularly
  • Be mindful of patient privacy and applicable regulations when using AI features
  • Review patient data access logs regularly
  • Ensure secure network connections when accessing the system

Efficiency Tips

  • Use keyboard shortcuts for faster navigation
  • Set up quick actions for frequently performed tasks
  • Use filters and search to quickly locate information
  • Take advantage of bulk actions where available
  • Customize your dashboard to show most relevant information

Hospital OS