Hospital information system with pharmacy and ambulance

The challenge

Hospitals often run outpatient, inpatient, pharmacy, blood bank and emergency transport on disconnected tools. Staff re-enter data, and stock, bed and ambulance status is hard to see in one place.

What we built

A NestJS and PostgreSQL backend models hospitals, doctors, receptionists, patients, OPD visits, IPD beds and admissions, prescriptions, pharmacy batches and billing, blood bags and issues, and ambulance calls with route history and SOP checklists. Role-based screens in a Next.js frontend serve provider, hospital, receptionist and admin users. Ambulance location updates and video consultation events run over WebSocket gateways, and routing uses a maps API. Health-device and lab-biomarker data from other services can be attached to patient records.

Key capabilities

• OPD visits, follow-ups, IPD bed management and admissions
• Pharmacy catalogue with batches, suppliers, purchases and billing
• Blood bank inventory, donors and issue tracking
• Ambulance dispatch with live location history, routes and SOP checklists
• Telemedicine sessions with participants, chat, recordings and call quality events
• Role-specific dashboards for hospital, provider, receptionist and admin users

What it delivers

• Brings outpatient, inpatient, pharmacy, blood bank and emergency transport into a single data model
• Gives different hospital roles purpose-built dashboards over the same records
• Supports real-time operational views for ambulances and video consultations
• Backed by automated tests and process-manager deployment configuration, with a documented path to higher frontend coverage