Features

Hayati AI Nexus Features: Every Tool Needed to Run a Modern Hospital, Clinic, or Pharmacy

Deep modules for billing, branches, inventory, TPA alignment, offline counters, queue, and governed AI—organized by what operators pilot first, not a flat feature checklist.

Desktop license—activate on your machine after verified payment. Not a cloud trial signup.

Patient flow and front desk

AI Receptionist, Patient Queue Display, and queue management connect calls and walk-ins to tokens staff can see—without claiming to replace clinical systems you have not scoped.

Clinical and pharmacy operations

Doctor Dashboard provides operational context before consult—including doctor payout and settlement views where your consultant contracts are configured. Pharmacy inventory enforces FEFO at dispense with barcode labels, stock journals, dead-stock views, supplier outstanding, and purchase returns. GST billing and offline billing keep counters running when connectivity fails—thermal/A4 print, UPI QR, and shift cash control included where configured.

Finance and scale

TPA billing alignment follows hospital-side workstation language—pre-auth → claims → settlement/ERA → recovery/leakage—without live eligibility or NHCX network claims. Multi-branch governance covers inter-branch stock transfer, device quotas, and HO consolidation when entitled. Accounting Ops and Day Book style collection registers, GSTR-1/2/3B tooling, GSTR-2B reconciliation, e-Invoice IRN where scoped, and dual-control backup restore sit alongside product pillars on /product so hospital, clinic, and pharmacy modules share one spine.

How to evaluate features

Pick three modules that match your pain—usually offline billing, TPA or GST, and queue or reception—then run each on real bills during one walkthrough. Ask for a disconnect test, a GSTR or HSN summary export your CA recognizes, a hardware path (thermal, scanner, cash drawer), and a dual-control restore question—not only a dashboard tour.

Hospital vs clinic vs pharmacy feature paths

Hospitals weight AI Receptionist, queue display, TPA alignment, and offline OPD. Clinics weight compact queue, doctor list handoff, and doctor payouts where contracts apply. Pharmacies weight FEFO inventory, GST billing with sales/purchase registers, barcode labels, and offline counters. The hub links below map to deep dives with FAQs and, for AI modules, HowTo schema.

Modules not yet deep-dived on marketing site

GST billing, offline billing, multi-branch, pharmacy inventory, queue management, and TPA billing have feature pages with operational FAQs—depth varies by module. Supporting capability language also covers GSTR-1/2/3B and GSTR-2B reconciliation, e-Invoice IRN, thermal/A4 and UPI QR hardware paths, Accounting Ops / Day Book collection discipline, doctor payouts, and dual-control backup restore—scoped on walkthrough, not claimed as auto-filing or disaster recovery alone. Book a walkthrough to run your disconnect test and payer sample on the modules you shortlist.

Frequently asked questions

Which feature should hospitals pilot first?
Most hospitals start with AI Receptionist handoff, queue display, and offline OPD billing—then TPA alignment on the pre-auth → claims → settlement path.
Which features matter for pharmacies?
Offline billing, pharmacy inventory (FEFO, barcode labels, dead stock, purchase returns), and GST billing with GSTR-oriented registers—see /pharmacy and /pharmacy-software/india.
Does every feature include AI?
No. GST, offline, multi-branch, and TPA modules are operational—AI modules are optional and governed.
Where are finance and hardware capabilities described?
GST and offline feature pages cover GSTR tooling, HSN summary, UPI QR, thermal/A4, shift cash control, and dual-control backup (sync ≠ backup). Features hub Finance and scale points to Accounting Ops / Day Book and doctor payouts; deep dive pages and walkthroughs fill remaining gaps.
Where are AI feature deep dives?
/features/ai-receptionist, /features/patient-queue-display, /features/doctor-dashboard, /features/ai-retention-agent include HowTo schema.
Can we buy one module only?
Licensing is scoped per contract during discovery—walkthrough defines minimum viable spine for your branches, including device quotas where multi-branch applies.
How do features connect?
Events flow on one OS spine described on /platform—billing does not retype patient context from a separate appointment app.

Evaluating a move from another system? Migration