Module Walkthrough: Advanced & Admin

February 2026 · 18 min

Telemedicine Module

The Telemedicine module enables remote consultations via video, chat, and asynchronous messaging. It integrates with the clinical workflow so that prescriptions, lab orders, and billing work identically to in-person visits.

Key screens and fields:

FC configuration tasks:

1. Enable telemedicine module in organization settings
2. Configure video provider credentials (Twilio / Daily.co)
3. Set up teleconsult appointment types and fee schedules
4. Map teleconsult encounters to the correct billing category
5. Train doctors on the side-panel clinical documentation workflow

BI & Analytics Module

The BI module provides dashboards and drill-down reports for hospital management. It pulls data from all transactional modules and presents KPIs in visual charts.

Dashboard categories:

• Clinical Analytics -- OPD footfall trends, diagnosis frequency, average consultation time, readmission rates
• Financial Analytics -- daily/monthly revenue, collection efficiency, outstanding receivables, department-wise profitability
• Operational Analytics -- bed occupancy, average length of stay, OT utilization, lab TAT, radiology TAT
• Quality Indicators -- infection rates, medication error rates, patient satisfaction scores, NABH quality indicators

FC tasks:

• Configure which dashboards are visible per role (doctors see clinical, management sees financial)
• Set up scheduled report emails (daily revenue summary to CFO, weekly quality report to QI team)
• Define KPI thresholds and alert rules (e.g., bed occupancy > 90% triggers alert to nursing director)
• Train management on drill-down navigation: chart → filter → individual records

Workflow Engine

The Workflow Engine allows FCs to configure rule-based automations without writing code. Workflows trigger on events (e.g., patient admitted, bill generated) and execute actions (e.g., send notification, create task, update status).

Workflow components:

Common hospital workflows to configure:

1. Critical lab result alert -- Trigger: result value outside normal range → Action: notify ordering doctor via push notification
2. Discharge delay alert -- Trigger: doctor marks 'Fit for discharge' → Delay: 4 hours → Condition: patient still admitted → Action: notify nursing supervisor
3. Insurance pre-auth reminder -- Trigger: IPD admission with insurance → Delay: 2 hours → Condition: pre-auth not submitted → Action: alert billing team
4. Medication due reminder -- Trigger: scheduled medication time → Action: alert assigned nurse

Command Center

The Command Center is a real-time operational dashboard designed for display on large screens in the hospital's administrative area. It shows live data that updates via Supabase real-time subscriptions.

Command Center panels:

• Bed Board -- visual grid showing every bed in the hospital, color-coded by status (occupied/vacant/reserved/under-cleaning)
• ER Status -- current patients in emergency, triage levels, waiting times
• OT Schedule -- today's surgeries with real-time status (pre-op, in-surgery, recovery)
• Queue Monitor -- OPD token queues per doctor with average wait times
• Critical Alerts -- scrolling ticker of P1/P2 alerts from the workflow engine

FC setup tasks:

1. Configure which panels appear on the command center (hospital-specific)
2. Map bed IDs to physical locations (wing, floor, room, bed number)
3. Define color-coding rules for bed statuses
4. Set refresh intervals (default: real-time via WebSocket, fallback: 30-second polling)
5. Configure large-screen display mode (auto-rotate panels, font sizing for wall-mounted TVs)

Bio Ecko Studio

Studio is the low-code customization layer for FCs to extend the platform without developer intervention.

Studio capabilities:

• Custom Fields -- add fields to any form (patient registration, encounter, billing) with validation rules
• Custom Forms -- build entirely new data collection forms (e.g., specialized assessment checklists)
• Custom Reports -- drag-and-drop report builder with filters, grouping, and export
• Print Templates -- design custom print layouts for discharge summaries, prescriptions, bills, and certificates
• Dashboard Widgets -- create custom KPI widgets for role-specific dashboards

Print template variables commonly used:

Multi-Branch Administration

For hospital chains, Bio Ecko's multi-branch architecture allows centralized administration with branch-level data isolation.

Admin tasks for multi-branch:

1. Branch setup -- create branch entity with address, license details, NABH certificate
2. User assignment -- assign staff to specific branches (a user can belong to multiple branches)
3. Shared master data -- drug formulary, diagnosis codes, and tariff templates can be shared across branches or overridden per branch
4. Branch-level settings -- each branch can have its own appointment slots, bed configuration, department structure, and print templates
5. Consolidated reporting -- management dashboards aggregate data across all branches with drill-down to individual branch

Data isolation rules:

• Patients are global (can visit any branch)
• Encounters, billing, and orders are branch-specific
• Inventory is branch-specific (each branch has its own stock)
• Staff schedules are branch-specific
• Financial reports can be branch-level or consolidated

Audit Trail & Compliance Tools

Every action in Bio Ecko is logged in the audit trail. FCs must understand this system for NABH compliance and dispute resolution.

Audit trail captures:

• Who -- user ID, name, role
• What -- action performed (create, update, delete, view, print, export)
• When -- timestamp (server time, IST)
• Where -- module, screen, record ID
• Before/After -- for updates, both the old and new values are stored

Compliance tools:

• Access log report -- who accessed which patient record and when (DPDPA compliance)
• Break-the-glass log -- when emergency access overrides normal permissions, it's logged separately
• Data retention policies -- configurable per record type (e.g., patient records retained for 3 years post last visit per MCI guidelines)
• Consent management -- patient consent records for data sharing, ABDM linkage, research participation

Integration Hub

The Integration Hub manages all external system connections. FCs configure integrations without code using the hub's admin interface.

Common integrations:

Notes

Related topics