The desk, the counter, the tax return and the printer nobody wants to replace.

Money in and receipt out, the hardware already on the counter, the clinical systems you keep, and every other Dule on the same record. What connects, what it means when it does, and what is still on the roadmap.

Money and the books

Money in, receipt out, books balanced

Real double-entry accounting sits under the billing screen, which is uncommon at this size of organisation. It is why the reconciliation is a report rather than a project.

UPI, card, and cash

All three settle onto the same ledger, so the daily total is one number rather than three reconciliations that meet on Monday.

Tax-aware receipts

GST handling is part of the receipt, and each receipt is sealed into a hash-chained fiscal record rather than written and forgotten.

Double-entry underneath

Every charge posts a journal entry as it happens. What you dispensed and what you invoiced are the same fact, not two records that have to agree.

Export and audit trail

Revenue, dues, and expenses export in a form your accountant can take straight into their own books, and the access log behind them is append-only.

The hardware on the desk

The iron you already own is already the right iron

Hardware here is declared, not hard-coded: a device is described in a definition file rather than waiting for a driver in a release. Unknown elements are skipped rather than thrown, which is what lets an old printer keep printing a layout authored after it shipped.

Receipt printers, ESC/POS

The de facto command set every thermal printer speaks, in the subsets they actually implement. Receipts print from a definition, so a change to the layout is not a release.

Label printers, ZPL and TSPL

The industrial and the Asian barcode-printer languages, plus legacy EPL. Media size is treated as a real design constraint rather than a purchasing detail.

Barcode scanners, 1D and 2D

Most scanners emulate a keyboard, so most of them simply work. We recommend a 2D imager even where 1D would do, because packaging QR and payment QR are both 2D.

Cash drawers

Not a device at all: the drawer opens on a command sent to the printer over its kick port. Modelled as a printer capability, which is what it actually is.

Card terminals

Your payment processor should be a choice you can change without changing your front desk. Terminals settle onto the same ledger as cash.

Biometric attendance

On the roadmap, and worth knowing the shape: a registered device signs and encrypts the capture itself, so an attendance module never handles a biometric template. Device certification is the gate, not our code.

Systems and rails

The systems you keep, and the ones you are told to join

HL7 v2 and FHIR R4

Standard interfaces for the systems a clinic already runs, so hospiDule is added rather than swapped in. HL7 v2.5.1 is the baseline on the lab hop, R4 the external contract.

ABDM-ready

Available for clinics that want it, on the ABDM sandbox track, and never a prerequisite to onboard. Linking records to ABHA is a national programme, not our lock-in.

Audit evidence, as you work

Immutable access logs and complete trails are written while the clinic works, so NABH-style audit prep is assembling what exists rather than reconstructing it.

Insurance and TPA claims

On the roadmap. India now has a claims exchange rail under ABDM, and joining one rail is a better answer than sixty bilateral integrations with insurers.

Excel and paper registers

The one-time migration from what you keep today is part of onboarding, not an integration project you scope and pay for separately.

The platform and the door out

One record, every surface, and your own way in

docDule

The consultation your doctors record is the consultation the clinic bills.

medDule

Lab and pharmacy activity lands on the same visit and the same ledger, so stock and revenue move together.

patDule

Bookings, reminders, and reports reach the patient without the front desk re-sending anything.

A versioned REST API

Everything the screens do is reachable over a documented HTTP API, with published events for anything that needs to react rather than poll.

Export, whenever you ask

Patients, visits, receipts, stock, and the ledger export in open formats. There is no exit fee and no export project.

Early Access

Ask what connects to your setup

Tell us what your clinic runs on today, down to the printer model and the accountant's format, and we will tell you what connects, what needs a definition writing, and what does not connect at all.

Data migration from Excel, paper registers, or another system is included in onboarding.

Explore

More from hospiDule

The full picture, one page at a time.

Features

Everything hospiDule does, from the front desk to the month-end reconciliation.

Use cases

Who hospiDule is for, by facility type, by the job you do inside it, and by the day it fixes.

Pricing

Revenue protection, billing, and operations for clinics and hospitals, priced per location. Free during early access.

FAQ

Every question we are asked about hospiDule, answered in one place.