Odoo for hospitals and diagnostic centers, minus the clinical layer.

Odoo Is Not an HMIS, and That's Fine

Every conversation about Odoo in a Bangladesh hospital or diagnostic center should start with what it cannot do. It has no clinical charting, no doctor's e-prescription module, no nursing medication administration record, no OT (operation theater) scheduling with clinical dependencies, and no integrated lab result interface reading directly off analyzer machines. Facilities that need those capabilities run a dedicated Hospital Management Information System (HMIS), whether a purpose-built local product or an international platform, and nothing in this guide argues for replacing that layer with Odoo.

What is true, and what makes Odoo genuinely relevant here, is that a large share of Bangladesh's private hospitals, clinics, and diagnostic/pathology centers, particularly the ones in the 30 to 150 bed range or the mid-size diagnostic chains with 3 to 15 branches, either have no proper financial and inventory system at all, or run their billing on a locally built or single-purpose billing package with weak accounting, inventory, and reporting depth. That gap, the business operations layer sitting underneath the clinical workflow, is where Odoo does real work: patient invoicing, package pricing, procurement, lab consumable stock, HR and payroll (detailed in Odoo HR & Payroll Bangladesh, directly relevant given how shift-heavy hospital staffing is), and the doctor referral commission structure most facilities currently track in a notebook or a private spreadsheet nobody outside the finance office sees.

Where Odoo Actually Fits in a Bangladesh Facility

The realistic architecture most Bangladesh facilities end up with, and the one worth designing for deliberately rather than backing into, runs a clinical system (HMIS or a simpler patient record tool) for anything touching diagnosis, treatment, and clinical documentation, and Odoo for everything that is fundamentally a business transaction: the invoice a patient pays at the counter, the reagent purchase order sent to a diagnostic supplier, the referral commission owed to a doctor, and the monthly payroll run for nurses, lab technicians, and administrative staff. Where the two systems need to talk, typically patient identity and the list of tests or procedures ordered, a lightweight integration (even a manually reconciled daily export/import in smaller facilities, or a proper API bridge in larger ones) keeps clinical data in the clinical system and financial data in Odoo without forcing either system to do the other's job badly.

Patient Billing and Package Pricing

Bangladesh private healthcare pricing runs on two parallel models that a billing system needs to handle simultaneously: individual walk-in pricing per test or procedure, and fixed-price packages bundling several tests or a full health check-up (a very common consumer product in Bangladesh diagnostic marketing, often sold as an "executive health check" or a targeted package for diabetes, cardiac, or pre-employment screening). In Odoo, under Sales > Products, a package is modeled as a kit-style product with component lines representing each included test or service, priced as a single fixed total distinct from what those same components would cost purchased individually.

This structure matters for a reason beyond convenience: it lets the facility see true package margin, the package price minus the actual consumable cost and referral commission triggered by each included component test, separately from standalone test revenue. Packages are almost always priced at a discount to the sum of individual test prices specifically to drive volume and win the price-sensitive segment of the market, and without component-level cost visibility, management cannot actually tell whether a popular package is a strategic loss-leader that is working as intended or a margin problem nobody has flagged.

Billing Type	Odoo Structure	Operational Note
Individual test/procedure	Standard sales product, single price	Priced per NBR VAT rules applicable to the specific healthcare service category
Fixed-price package	Kit product with component lines	Reveals true margin per package vs. sum of individual test costs
Insurance/corporate billing	Customer-specific price list, deferred settlement terms	Corporate clients often settle monthly on a consolidated invoice, not per visit
Admission/IPD billing	Running sales order accumulating charges until discharge	Bed charge, procedure, medicine, and consumable lines all roll into one final settlement

A package price is a marketing decision wearing an accounting disguise. Until the component cost is visible, nobody actually knows whether the discount was smart or expensive.

Lab Consumable and Reagent Inventory

Diagnostic and pathology lab operations consume reagents, test kits, culture media, and disposable collection materials that are expiry-sensitive in a way that closely resembles pharmaceutical inventory management: a reagent used past its expiry can produce an inaccurate result, which is a clinical risk, not just a cost write-off. Odoo's lot and expiry tracking under Inventory > Traceability, configured with FEFO (first-expiry-first-out) removal strategy on reagent and consumable products, ensures lab staff are directed to consume the soonest-expiring stock first rather than grabbing whatever is at the front of the shelf, and expiry alerts under Inventory > Reporting > Expiration Dates give the lab manager advance warning before stock ages out unused.

This lot-tracking discipline is the same mechanism covered for pharmaceutical manufacturers in Odoo for Pharma Bangladesh, applied here to a healthcare provider's internal consumption rather than a manufacturer's production batches. The volume and cost profile differ significantly (a diagnostic center is managing shelf stock of purchased reagents, not manufacturing anything), but the underlying requirement, knowing exactly what lot of what reagent was on hand and used on which date, is structurally identical, and it is just as important for a facility defending a result dispute or an insurance audit as it is for a pharma company defending a batch recall.

Doctor Referral Commissions

Physician referral commissions, a percentage of test or procedure revenue paid to the doctor who referred the patient, are a widespread and commercially normal practice across Bangladesh private healthcare, and they are also a genuinely sensitive topic: informally tracked or under-documented referral payments have drawn regulatory and public scrutiny in Bangladesh's healthcare sector precisely because a lack of clear records makes it impossible to distinguish a standard commercial referral arrangement from something more problematic. A facility with a properly built, auditable referral tracking system in Odoo is protecting itself as much as it is managing an expense line.

The practical build: each referring doctor is a vendor/partner record, and every patient invoice line that resulted from that doctor's referral carries a reference (a custom field or analytic tag) linking back to the referring doctor. A scheduled report or automated computation, built either as a simple filtered list under Accounting or a custom Odoo Studio field calculation, totals the commission owed per doctor per period at the agreed percentage or flat rate, and settlement runs through the standard vendor bill and payment cycle under Accounting > Vendors > Bills, entirely separate from the patient's own payment record. Keeping this workflow structurally distinct from patient billing, rather than netting commission off the patient invoice directly, is what preserves a clean audit trail on both sides: the patient's bill shows the full service price, and the doctor's commission is a separate, dated, traceable payment.

DGDA-Adjacent Procurement Compliance

It is worth being precise about which regulator does what here, since this is a common point of confusion. The Directorate General of Drug Administration (DGDA) directly regulates pharmaceutical manufacturers and licensed drug importers and distributors, which is the relationship covered in the pharma manufacturing article referenced above. A hospital or diagnostic center's own relationship with DGDA is one step removed: it is a purchaser of medical consumables, drugs for internal dispensing, and diagnostic reagents, and its compliance obligation is procuring only from DGDA-licensed suppliers and maintaining a clean, auditable trail of what was purchased, from whom, and when it was consumed.

In Odoo, this means vendor master records under Purchase > Vendors should carry the supplier's DGDA license reference as a stored field, purchase approval workflows should block procurement from unverified or unlicensed suppliers for regulated categories, and the same lot/expiry tracking discussed for lab reagents extends to any drugs the facility dispenses internally (common in inpatient settings where medication is billed as part of the patient's overall charge rather than sold separately). This is a lighter compliance burden than a manufacturer's batch-level DGDA reporting, but a facility that cannot produce a clean procurement and consumption trail on request, whether for a regulatory visit, an insurance audit, or a legal inquiry following an adverse event, has a real exposure that a properly configured Odoo procurement and inventory setup closes.

Staffing and Duty Roster Realities

Hospitals and diagnostic centers run continuous shift coverage, nurses, lab technicians, and support staff working rotating shifts including night duty, which creates payroll complexity beyond a standard office HR setup: shift differentials, night duty allowances, and overtime calculated against actual roster hours rather than a flat monthly salary. Odoo's Attendance and Payroll modules, configured with shift-based work schedules under Employees > Configuration > Working Schedules, handle this correctly when set up with the facility's actual shift patterns rather than a generic 9-to-5 template inherited from a standard office HR deployment, a mistake that is common when a facility's first Odoo configuration is done by someone without healthcare staffing experience.

On-call and locum physician arrangements, common for hospitals that do not employ every specialist full-time, add a further layer: a doctor on a per-visit or per-shift retainer is typically modeled as a vendor arrangement (similar in structure to the referral commission tracking above) rather than a standard payroll employee, since the payment basis, frequency, and tax treatment differ from salaried staff.

Reporting Hospital Management Actually Wants

Beyond individual invoices and commission ledgers, the reports that matter to a hospital administrator or diagnostic chain owner are aggregate ones: revenue by department or test category, package versus individual-test revenue mix, referral commission expense as a percentage of revenue by doctor and specialty (useful for identifying both the facility's most valuable referral relationships and any single doctor whose referral volume creates concentration risk), consumable cost as a percentage of lab revenue, and bed or equipment utilization for hospitals running inpatient services. The dashboard-building approach covered in Odoo Dashboards & KPI Bangladesh applies directly here, and a well-built single-screen view of these figures is typically the single most valued deliverable of a hospital Odoo implementation, since it replaces a monthly manual compilation exercise that previously took the finance team days to assemble from disconnected registers.

One additional reporting item worth building deliberately rather than leaving as an afterthought is a monthly variance report comparing budgeted versus actual consumable spend per department, since diagnostic and pathology departments in particular tend to see reagent cost creep quietly upward as test volume grows, and a facility that only reviews this annually during budget season typically discovers the drift long after it has eroded a full year of margin. Tying this variance report to the same lot and consumption data already captured for expiry tracking means no additional data entry burden, only a different lens applied to data the system is already recording.

Implementation Sequencing Alongside a Live Facility

A hospital or diagnostic center cannot pause patient billing to implement a new system, which makes sequencing critical:

• Start with billing and package pricing first, since it is the highest-volume, most visible daily transaction and delivers the clearest immediate improvement over a disconnected billing tool.
• Bring lab inventory and expiry tracking in as a second phase, once billing staff are comfortable, rather than launching both simultaneously and overwhelming a small implementation team.
• Build the referral commission structure carefully and confidentially, involving only the finance leadership who need to see it, since this is sensitive data that should not be broadly visible across general staff access.
• Run billing in parallel with the legacy system for at least two to four weeks before fully cutting over, reconciling daily totals between old and new systems to catch configuration errors before they compound.
• Bring payroll and HR online last, timed to a payroll period boundary rather than mid-cycle, to avoid a confusing partial-period calculation for shift-based staff.

Frequently asked questions

Can Odoo replace a Hospital Management Information System (HMIS) in Bangladesh?

No, and it should not be positioned that way. Odoo has no clinical/EMR module, no e-prescription workflow, no nursing charting, no OT scheduling, and no clinical decision support, which are the core functions of a purpose-built HMIS. What Odoo genuinely covers well is the business and operations layer sitting alongside clinical care: patient billing and package pricing, lab consumable and reagent inventory, doctor referral commission tracking, procurement, accounting, and HR/payroll. Most Bangladesh private hospitals and diagnostic centers that adopt Odoo run it side by side with a dedicated HMIS or a simpler clinical record system, using Odoo specifically for the parts an HMIS typically handles poorly: finance, inventory, and vendor management.

How do you set up package pricing for diagnostic tests in Odoo?

A test or health-check package (for example, a fixed-price bundle covering CBC, blood sugar, lipid profile, and a chest X-ray) is modeled in Odoo as a Bill of Materials style kit product or a Sales product with component lines representing each included test, priced as a single fixed total under Sales > Products, distinct from the sum of each test's individual walk-in price. This lets the diagnostic center report true package margin (package price minus the cost of consumables and referral commission triggered by each component test) separately from standalone test revenue, which matters because packages are usually priced at a discount to individual test totals specifically to drive volume, and management needs to see whether that volume actually offsets the margin given up.

How should doctor referral commissions be tracked in Odoo?

Referral commissions should be tracked as a separate, auditable ledger tied to the referring doctor as a vendor/partner record, calculated as a defined percentage or flat amount per referred test or procedure, and settled through a standard vendor bill and payment cycle under Accounting > Vendors, completely separate from the patient's own billing and payment. Building this as its own workflow, with the referring doctor recorded against each patient invoice line as a custom field or analytic tag, gives the facility a clean, auditable commission report by doctor and by period, which matters both for the facility's own cost control and because loosely documented referral payment practices are a recurring source of scrutiny in Bangladesh private healthcare, so a clear paper trail protects the facility as much as it tracks the expense.

Does DGDA regulate hospital and diagnostic center procurement in Odoo?

The Directorate General of Drug Administration (DGDA) directly regulates pharmaceutical manufacturers and drug importers/distributors, which is a different relationship than a hospital or diagnostic center's own procurement of medical consumables, reagents, and drugs for internal use and dispensing. A healthcare provider's Odoo setup does not need manufacturing-grade DGDA batch compliance, but it does need to procure only from DGDA-licensed suppliers, maintain lot/expiry tracking on drugs and reagents purchased under Inventory > Traceability, and be able to produce a clean purchase and consumption trail if a regulatory or insurance audit asks for one. This is a lighter compliance layer than the manufacturing-side DGDA requirements covered for pharma companies, but it is not optional.

What does an Odoo implementation cost for a Bangladesh hospital or diagnostic center?

For a diagnostic center or small private hospital (30 to 150 beds or equivalent daily patient volume), an Odoo implementation covering billing, package pricing, lab inventory, referral commission tracking, and accounting typically runs BDT 8 to 20 lakh, with BDT 3 to 8 lakh per year for support, excluding any separate clinical HMIS licensing the facility runs alongside it. Larger multi-branch diagnostic chains or hospitals wanting deep integration between Odoo and an existing HMIS (for patient master data sync, for example) should budget additional integration development cost on top of these baseline figures.