Hospital management software for multi-department hospitals in Bangladesh
Private hospitals in Bangladesh run several departments at once: an outpatient floor, wards, an operating theatre, a laboratory and a pharmacy, each with its own counter and its own register. Shafa HMS is hospital software, in effect a hospital ERP, that puts those departments on one patient record and one billing structure, and Shafa EHR keeps the clinical history that follows the patient between them. This page is for administrators and owners weighing whether the suite matches the way their hospital works, which modules they would start with, and how the day's figures reach the finance office and the DGHS return without being compiled by hand at month end.
- One patient record across OPD, IPD, OT, lab and pharmacy
- Bed and theatre occupancy visible from the admin desk
- Department charges settle on a single bill
- Roll out module by module
Challenges
What multi-department hospitals struggle with
These are the problems administrators describe when they first speak to us. Most of them are not caused by carelessness; they are what separate registers produce.
Departments keep separate registers
OPD has a register, the ward has another, the lab and the pharmacy each keep their own, and the same patient appears in all of them under slightly different names. When a question comes to the administrator's desk, answering it means walking to four counters and reconciling four books.
Revenue leaks between counters
A test ordered on the ward is done but never charged. Medicines issued to an inpatient are missing from the discharge bill. Discounts are given verbally and remembered differently by the cashier and the patient. None of this is fraud; it is what happens when charges are written in one place and billed in another.
Nobody can say which beds and theatres are free
Admissions are decided by phoning the ward sister, and the theatre list lives on a whiteboard that only the OT in-charge can read. The administrator learns about a bed shortage when a patient is already waiting in the corridor, and about a theatre clash when a surgeon arrives to find the room occupied.
Monthly returns are a compilation exercise
The DGHS return, the owner's monthly summary and the auditor's questions all draw on the same admissions, deaths, tests and collections, yet each is assembled separately by a clerk with a calculator. Figures are late, occasionally disagree with each other, and are impossible to trace back to the visits they came from.
Rosters, attendance and pay live in different files
Nursing duty rosters are drawn up on paper, attendance is taken from a machine export, and payroll is calculated in a spreadsheet that only one person understands. Overtime, night allowances and leave balances are argued over every month because the three sources were never designed to agree with one another.
Product fit
Which Shafa products fit a hospital
A hospital of this shape usually needs most of the suite, but not all at once. The modules below are the ones that matter for a multi-department facility, with a note on why each earns its place. Follow the links for the detailed feature pages; this page stays at the level of fit.
Shafa HMS with IPD and bed management
The suite is the foundation. Admissions, bed allocation, transfers and discharge sit in the inpatient module, and every department writes to the same patient account. Inventory and HR & Payroll ship in the same suite, so store issues and duty rosters are on the same platform rather than in a separate file.
OPD Management
Most admissions begin as an outpatient visit. Registering the patient once at the OPD counter, with a token, a consultation record and a settled fee, means the ward, the theatre and the discharge desk inherit a clean identity instead of creating another. High-volume evening sessions are where the module pays for itself.
Operation Theatre and post-operative care
Theatre time is the scarcest resource in a surgical hospital. Scheduling the list against surgeon, anaesthetist and room availability, recording consumables used in each case, and tracking recovery afterwards turns the whiteboard into a plan the administrator can see and the finance office can bill from.
Laboratory Information System
A hospital laboratory receives most of its orders from the ward and the OPD, not from walk-ins. When the order is placed by the doctor, the sample is barcoded, and the verified result lands back in the ward record and on the bill, the courier, the phone call and the missed charge disappear together.
Pharmacy Management
An in-house pharmacy is one of a private hospital's larger revenue lines and one of the easiest to lose track of. Issuing against a ward indent or an OPD prescription, charging the patient account at the moment of issue and watching expiry by batch keeps dispensing, stock and billing telling the same story.
Accounts
Every counter in the hospital collects money, and the finance head needs them to reconcile without a second entry. Charges from OPD, wards, theatre, laboratory and pharmacy post to one ledger tagged by counter and shift, so the day closes at the desk rather than in a spreadsheet the following week.
Facility journey
How a patient moves through the hospital on Shafa HMS
The order matters. Each step reads what the previous one recorded, which is why nothing is entered twice and why the final report needs no compilation.
Registration
The patient is registered once, at whichever door they enter, and receives a hospital ID that every later department reads. Returning patients are found by phone number or ID, so the ward never creates a second identity for someone the OPD already knows.
OPD consultation or admission
An outpatient visit produces a consultation record, a prescription and any test orders. If the doctor admits the patient, the same record opens an inpatient episode, a bed is allocated from the live occupancy view, and the deposit is taken against the new account.
Diagnostics and pharmacy
Orders written on the ward or in the consultation room reach the laboratory as barcoded samples and the pharmacy as indents to dispense. Results return to the treating doctor's screen, issued medicines are charged to the account, and stock is reduced at the same moment.
Operation theatre
A surgical patient is booked onto the theatre list against surgeon, anaesthetist and room. Pre-operative checks, the procedure note and the consumables used in the case are recorded in the theatre, and the patient moves into post-operative monitoring before returning to the ward.
Billing and discharge
At discharge the account already holds bed days, procedures, tests, medicines and consultant fees, because each was charged where it happened. The cashier reviews, applies any approved discount, settles against the deposit, and the discharge summary is printed from the same record.
Reporting
Occupancy, theatre utilisation, department revenue, payroll cost and the figures needed for the DGHS return are drawn from the records created along the way. The administrator reads them as reports on the morning they are needed, not as a compilation delivered at month end.
Standards and compliance
Standards and safeguards
HL7 FHIR-based interoperability
Records are held as HL7 FHIR resources and exchanged through HL7 messaging where the other system supports it, so a referral hospital, an insurer or a national programme asking for data does not lock you into a private format.
Role-based access and audit logs
Ward staff, cashiers, pharmacists and administrators each work within the permissions their role needs. Each look at a record and each change to an invoice leaves an entry naming the user and the time, which is what an internal audit or a complaint investigation needs.
Encryption and HIPAA-style handling
Patient data is encrypted on the wire and in storage, and handled to HIPAA-style practices for protected health information. The hospital owns its data under every deployment model and can take it with it.
DGHS formats and Bangla interface
Returns can be produced in the formats used for DGHS reporting, and the whole interface is available in Bangla and English, selected per user rather than per hospital.
Deployment
Deployment for hospitals
A hospital with wards and a theatre cannot stop admitting patients because a link has gone down, and some owners want the database inside the building. Shafa HMS therefore runs hosted in the cloud, installed on the hospital's own servers, or cloud with an on-site edge node that keeps working through outages. The choice can change later.
Cloud
Shafa Care hosts the suite with a separate database for the hospital, manages backups and updates, and adds new wards, counters or branches as user accounts rather than hardware.
On-premise
The full suite runs on servers the hospital owns and controls, for owners and boards who require patient data to stay on site. Shafa Care maintains it under a support agreement.
Offline sync
An edge node inside the hospital keeps admissions, ward records, dispensing and billing available when the internet fails, then synchronises queued work in order once the connection is restored.
FAQ
Questions hospital administrators ask
How much does hospital software cost in Bangladesh?
Shafa HMS is a subscription priced per facility, and the figure depends on which modules you enable, how many users and counters you run, and whether you deploy in the cloud or on your own servers. We do not publish a price list because two hospitals of the same bed count rarely need the same configuration. Send us your department list and we will return a written quote.
What size of hospital is Shafa HMS built for?
The suite scales from small to large facilities because modules, wards and counters are configured rather than fixed. A hospital with one ward and a single theatre enables what it uses; a multi-specialty hospital adds departments, branches and user roles on the same platform. What matters more than bed count is whether several departments need to share one patient record and one bill.
Do we have to go live with every department at once?
No, and we advise against it. A typical sequence begins with registration, OPD and billing so that the front desk and the cash counter are stable, then brings in IPD and bed management, followed by the laboratory, pharmacy and theatre. Accounts and HR & Payroll can join at any point. Each phase builds on the patient records and fee structures already in place.
Our departments run on paper registers and Excel. How does migration work?
Patient lists, fee schedules, drug formularies and test menus are loaded from your spreadsheets before go-live, so a returning patient is matched to an existing record instead of being registered again. Old paper files stay in the archive; the treating doctor records the relevant history at the first digital visit. Training is delivered department by department on the hospital's own configuration, and the paper register runs alongside the system for a short period before it is retired.
Can the system produce the returns DGHS requires from private hospitals?
Admissions, discharges, deaths, disease-wise counts, test volumes and outpatient summaries are all recorded at the point of care, so the periodic return is generated from live data and arranged in the formats used for DGHS reporting. Shafa Care is engaged with DGHS on national digital-health work and keeps the formats current. We do not claim a certification; the reports are simply drawn from the records the hospital already keeps.
What happens on the ward when the internet goes down?
With offline sync, an edge node inside the hospital carries on serving admissions, ward records, dispensing, laboratory entry and billing exactly as before. Work done during the outage is queued locally and synchronised in sequence when the link returns, so no receipt is duplicated and no order is lost. Nothing changes at the counter except a sync status shown on screen.
Solutions by facility · Hospitals
See Shafa HMS against your own department map
Tell us which departments you run, how many counters collect money and where the paper still travels. We will walk through admission, theatre, discharge and the month-end return on Shafa HMS with your structure, not a generic one.