Skip to content
HOSPITAL SOFTWARE, END TO END

The whole hospital,running as one.

Reception to pharmacy, lab to ledger, consulting room to the patient’s phone — DivyaJivan is the single system a hospital actually runs on. Thirty modules you switch on as you grow. One login for every person, however many jobs they hold.

Book a walkthroughExplore the platform ↓
WHY DIVYAJIVAN

Hospital software is usually a pile of tools. This is a system.

A billing package at the front desk. A lab system down the corridor. Prescriptions on paper in between, and a ledger that agrees with none of them. DivyaJivan was built the other way around: one patient record, one ledger, one login — every department working inside the same system, so nothing is retyped, lost, or quietly different.

WHO IT'S FOR

One system. Eight ways in.

Eight kinds of person work an OPD day. Pick one to see what the system gives them.

Patients

01 / 08

A family's health, in one hand.

THE PATH
  1. Book a slot
  2. Visit
  3. Record updates
  4. Return reminder
01Up to seven family members on one membership — each with their own card number.
02Book a real slot: pick the hospital, the doctor, the time. Accept or decline a reschedule with one tap.
03Every prescription, bill, lab result, scan and vaccination — from every DivyaJivan hospital they've visited.
04Nine kinds of old reports, uploaded and kept with the record.
05Message the doctor who actually saw you — not a call centre.
06Return-visit reminders three days before, one day before, and that morning.
07Consent asked as three separate decisions — never one buried checkbox.

Reception

02 / 08

The front desk, without the chaos.

THE PATH
  1. Walk-in
  2. Register
  3. Token queue
  4. Day board
01Walk-in registration, a token queue, and a day board the whole floor can read.
02The same phone number never opens a second file.
03Find a patient by mobile, card or membership — even from another hospital.
04Every cross-hospital lookup is masked, audited, and capped at forty an hour.

Medical Officer

03 / 08

Vitals in, before the doctor sees them.

THE PATH
  1. Triage queue
  2. Vitals
  3. Priority
  4. To the doctor
01The triage queue, including the patients not yet allocated to a doctor.
02Vitals and priority recorded before the consultation starts.
03The doctor saving the chart does not overwrite what you put in.
04Duty notes and a shift handover, in the same record.
05A doctor's assistant sees the queue only, and only for their own doctor's patients.

Doctors

04 / 08

A chart that keeps up with the clinic.

THE PATH
  1. Encounter note
  2. Sign once
  3. Pharmacy · Lab · Billing
01A 13-section encounter note built for OPD speed.
023,238 tap-to-pick clinical phrases. 71,704 ICD-10 codes behind them.
03Pick-lists that follow the patient's age and sex.
04Suggestions that learn from your own charts — not someone else's habits.
05Prescribe by dose form; step-down courses total themselves.
06Print in English, Gujarati, or both.
07Sign once — pharmacy, lab and billing already have it.
08Signed notes lock. Corrections are additions, and they carry a date.
09Give your assistant some tabs, not others.
10Collect the fee at the chair.

Lab

05 / 08

Requisition to sign-out. Nothing skipped.

THE PATH
  1. Requisition
  2. Sample
  3. Result
  4. Sign-out
  5. Chart
01Requisition → sample → result → pathologist sign-out.
02Out-of-range results flagged wherever a range exists.
03Four jobs — one person or four people. The system doesn't mind.
04Signed results land straight in the chart.

Pharmacy

06 / 08

Dispense what was prescribed. Bill what was handed over.

THE PATH
  1. Prescription queue
  2. Dispense
  3. Stock down
  4. Bill
01The prescription queue arrives from the consulting room — nothing retyped.
02Dispense against live stock.
03A part-dispense bills only what actually crossed the counter.
04Purchase orders live in the same system as the shelf.

Accounts

07 / 08

One ledger for every rupee.

THE PATH
  1. Every department
  2. One bill
  3. Ledger
  4. Day book
01Every rupee in and out, in one ledger. A day book that closes.
02Part payments, tracked to the paisa.
03Refunds capped at what was actually collected.
04Concessions carry a reason and a named approver.
05Insurance claims followed from submission to settlement.
06The expense register lives in the ledger — not in a drawer.

Admin

08 / 08

Switch on what you run.

THE PATH
  1. Add staff
  2. Verify doctor
  3. Set tariff
  4. Switch a module on
01Add staff, verify doctors, and set what each of them can reach.
02Tariffs — and each doctor's fee — exactly as agreed.
03Turn modules on as the hospital grows.
04MIS that shows billed, collected, and what you did and never charged for.
05One login per person opens all their workspaces, however many jobs they hold.
THE DEPTH

Built deep, not thin.

30modules
5editions
71,704ICD-10 codes
3,238clinical phrases
13sections per encounter
18item WHO surgical checklist
7family members, one membership
40/hraudited lookup cap
GOVERNANCE

Built like it will be audited.

Every rule below is enforced by the system — not by a circular pinned to a noticeboard.

Signed notes lock; corrections are dated additions — the original never changes.
The same phone number never opens a second file.
Every cross-hospital lookup is masked, logged, and rate-limited.
Refunds can never exceed what was collected.
Concessions require a reason and a named approver.
A part-dispense bills only what actually crossed the counter.
Money is whole paise, from the counter to the day book.
Access is scoped by role — down to individual tabs of the doctor's screen.
Consent is three separate decisions, recorded separately.
The platform itself keeps a full audit trail.
ONE VISIT

Sign once. Three desks already have it.

A patient is registered, takes a token, and is seen. The note the doctor signs is the same object the pharmacy queue, the lab requisition and the bill are made from — so nothing is retyped between one desk and the next, and no two of them can quietly disagree.

Diagram: one visit drawn as a single rail — registered at the front desk, then a token, then the encounter note — running into the moment it is signed, which is drawn as one line across the plate. Three lines leave that same line at the same point, carrying the note to the pharmacy queue, the lab requisition and the bill.REGISTEREDTOKENTHE NOTESIGNEDPHARMACY QUEUELAB REQUISITIONTHE BILLONE SIGNATURE · THREE DESKS
The signature is the hand-off. Nothing is re-entered downstream, because there is nothing downstream to re-enter it into.
THE MONEY

Every department. One bill.

Consultation, pharmacy and laboratory all post onto the same folio for that visit — and so does whatever else the hospital switches on later. One total at the counter, and one day book at the end of it.

Diagram: consultation, pharmacy and laboratory each posting their charges into one junction, and from there onto a single folio for the visit which carries one total. The folio holds a specimen bill — an invented patient and invented items, changing every few seconds — and not real data from any hospital.POSTS TO THE FOLIOONE FOLIO · ONE TOTALCONSULTATIONPHARMACYLABORATORYSPECIMEN — NOT A REAL BILLITEMAMOUNT ₹TOTALSPECIMEN PATIENT AConsultation · General Medicine400Paracetamol 650 mg × 1042Amoxicillin 500 mg × 15186Complete blood count350978
The lines on the folio are a specimen: invented patients, invented items, cycling as you watch. What is true is the shape — everything a visit generates lands on one folio, and the counter reads one total off the bottom of it.
LANGUAGE

Prescriptions your patients can actually read.

One signed note prints in English, in Gujarati, or in both together. The doctor writes it once; the language is a setting on the printed sheet, not a second prescription to keep in step.

Instruction words print in English. Nothing else on the sheet is affected.

The drug name, the dose, the day count and the total print in Latin script whichever setting is used — those are what the pharmacist dispenses against, and transliterating a drug name is a dispensing error waiting to happen. Only the instruction words change: a fixed vocabulary of dose timings and food relations, written for this product.

A Gujarati-only sheet prints the same way, with the English line left off.

SPECIMEN SHEET

Three made-up lines, set to show the columns. Not a real patient and not a real prescription.

MedicineDoseTimeWhenDaysTotal
Amoxicillin 500 mg1-0-1Morning · NightAfter food510 tablets
Paracetamol 650 mg1-1-1Morning · Afternoon · NightAfter food39 tablets
Pantoprazole 40 mg1-0-0MorningEmpty stomach55 tablets

The sheet scrolls sideways — six columns.

  • Four columns — Latin script in every mode.
  • Two columns — the instruction words, and all the setting changes.
MODULES

Thirty modules. Switch on what you run.

Start with a consulting room. Add pharmacy when there's a counter, a laboratory when there's a bench, the family app when patients ask for it. Same system throughout — nothing to migrate later.

  • Reception & token queue
  • Appointments & slots
  • Patient registry & family accounts
  • Day board
  • Doctor EMR
  • e-Prescriptions
  • Laboratory
  • Document vault (old reports)
  • Pharmacy dispensing
  • Pharmacy purchase & stock
  • OPD billing
  • Accounts & ledger
  • Expense register
  • Concession & refund controls
  • MIS & analytics
  • Patient Android app
  • Messaging & reminders
Diagram: the thirty modules laid out by where they live in the hospital — front of house, clinical, diagnostics, inpatient and critical, pharmacy and supply, money, governance and back office, and patient-side — with the count of each group, and a note that seven of the thirty are always on.THE THIRTY, BY WHERE THEY LIVEFRONT OF HOUSECLINICALDIAGNOSTICSINPATIENT & CRITICALPHARMACY & SUPPLYMONEYGOVERNANCE & BACK OFFICEPATIENT-SIDESEVEN OF THE THIRTY ARE ALWAYS ONPATIENT IDENTITYSCHEDULINGCLINICAL ENCOUNTERBILLINGNOTIFICATIONSCONSENT & AUDITPLATFORM CONFIGURATION
Seven are always on: identity, scheduling, the encounter, billing, notifications, consent and audit, and configuration. The other twenty-three switch on as the hospital grows — some of them today, the rest as they come out of development.
See all thirty →
EDITIONS

From one doctor to three hundred beds.

Solo Clinic

One doctor, one room, the essentials.

Polyclinic

Several doctors, one front desk.

Nursing Home

Beds, nursing, the ward round.

Hospital

Departments, theatres, the works.

Enterprise

Up to 300 beds, every module on.

Diagram: the five editions drawn as a nested scale, each reaching further along it than the one before and containing it, from one doctor in one room out to a hospital of up to three hundred beds. The two nearest editions are drawn in solid ink with filled markers; the three beyond them continue in hairline dashes with hollow markers, showing how far along the plan the product delivered so far reaches.SOLO CLINICPOLYCLINICNURSING HOMEHOSPITALENTERPRISEONE DOCTOR, ONE ROOMUP TO 300 BEDS
Each edition contains the one before it. Growing means switching more on — not moving to another product, and not migrating anything.

Pricing on request — every hospital runs a different mix.

Talk to us about pricing
FOR FAMILIES

A family's health, in one hand.

One membership, up to seven people. Real appointment slots, every record from every visit, reminders that arrive before you forget.

Android · available through partner hospitals · app-store listing on the roadmap

See the app →
01

Family

One membership number for the household, and a card number for each person on it.

02

Booking

Pick the hospital, then the doctor, then a real open slot from their own calendar.

03

Records

Bills, lab results, scans, prescriptions and vaccinations from every hospital they've used.

04

Uploads

Photograph an old report and file it against the right family member, under one of nine types.

05

Messages

Ask the doctor who actually saw you. A doctor with no visit cannot be messaged at all.

06

Reminders

A return visit is remembered three days ahead, the day before, and that morning.

07

Consent

Terms, privacy and health-data consent are three separate decisions, recorded separately.

IN THE WORKSHOP

What's next.

In active development — not live today. We'd rather tell you that here than in a demo.

SOONOnline payments
SOONOTP self-signup & password reset
SOONPush notifications
SOONVideo consultations
SOONDrug-interaction checking
SOONABDM & FHIR
SOONPatient web portal
SOONPublic app-store release
QUESTIONS

The things owners ask first.

See it running on your OPD's busiest morning.

A thirty-minute walkthrough on your own cases — a token queue, a part-dispense, a refund, a concession that needs an approver. Bring your hardest workflow.