Skip to content
Home About Services Work Notes Contact Start a project
Healthcare software

Hospital management software development

OPD and IPD, billing, pharmacy, pathology, radiology, blood bank and records — built module by module, and running in production at a government medical college hospital.

Hospital software is judged at the counter. If registration takes ninety seconds instead of fifteen, the queue reaches the door and the staff go back to the register book. Every design decision I make in this domain comes back to that.

I built and continue to run the hospital management system for Darbhanga Medical College & Hospital — a government medical college hospital — along with its radiology, attendance and campus systems. It is Django and PostgreSQL, deployed with Redis caching and connection pooling, because the boring stack is the one that stays up.

Typical stack

DjangoPostgreSQLRedisPgBouncerCeleryDockerNginxGunicornBiometric integration

Related services

What's included

What this actually covers

Registration & OPD

Patient registration, unique identifiers, department and doctor allocation, token queues and repeat-visit lookup that finds the record in one field.

IPD & ward management

Admission, bed and ward allocation, transfers, daily charge accrual, discharge summaries and the final bill.

Billing & collections

Rate lists, categories and concessions, part payments, refunds, daily collection registers and shift-wise reconciliation.

Pharmacy & stores

Drug masters, indents and issues, batch and expiry tracking, stock movement across medicine store and central store.

Pathology & radiology

Test ordering, sample tracking, result entry with reference ranges, report authoring and delivery, plus a patient-facing report lookup.

Blood bank & records

Donor and unit registers, grouping, cross-matching and issue records, alongside a medical records room module for filing and retrieval.

How it runs

From first call to production

  1. 01

    Discovery

    A working session to pin down what the system has to do, who touches it and what already exists. You get a written scope, an architecture sketch and a realistic estimate before anything is committed to.

  2. 02

    Design & architecture

    Data model, API surface and screens, agreed before the build. Designing against real data and real edge cases is what stops the rebuild three weeks in.

  3. 03

    Build in slices

    Working software every week against a staging URL you can open, rather than a big reveal at the end. Feedback lands while it is still cheap to act on.

  4. 04

    Launch

    Deployment, DNS and TLS, database migration, backups, monitoring and an handover walkthrough. The system goes live on infrastructure you own.

  5. 05

    Run it

    Optional retainer: security patches, feature work, performance passes and a person who already knows the codebase when something breaks.

Proof

Related case studies

Darbhanga Medical College & Hospital — Hospital Management System (HMS)

Darbhanga Medical College & Hospital

An end-to-end hospital management system covering patient registration, OPD and IPD workflows, billing, pharmacy, pathology, radiology, blood bank and medical records — running in production on a government medical college campus.

Read the case study
Questions

Frequently asked

Do you have a hospital system already running?

Yes. The HMS at Darbhanga Medical College & Hospital is live, along with separate radiology, attendance and digital signage systems on the same campus. That is production experience in a government hospital, not a pilot.

Can we start with one department?

You should. Registration and billing first, then pharmacy, then diagnostics. Each module goes live and earns trust before the next one starts — attempting a whole hospital at once is how these projects fail.

Can it run on our own servers?

Yes, and for hospitals it is often the right choice — patient data stays inside the building and the system keeps working when the internet link does not. Cloud hosting is equally supported.

What about patient data security?

Role-based access by department and designation, audit logging of record access and changes, encrypted transport, and backups tested by restoring them. Access is scoped so a pharmacy login cannot read pathology records.

Can it integrate with lab analysers and biometric devices?

Yes. Biometric attendance integration is already in production on the DMCH campus, and analyser and device integrations are handled case by case depending on the interface the hardware exposes.

Next step

Need hospital management software?

Tell me what you are trying to ship. You get an approach, a timeline and a realistic estimate — usually within a working day.