Infobytes Nepal Services

Clinic Management Software in Nepal

Infobytes Nepal builds ClinicNP, a clinic and pharmacy management system for polyclinics, clinics, and medical centres across Nepal. It runs the front desk the way the day actually runs: patients and their visits, doctors and their shares, samples followed all the way to the report, medicines by batch and expiry, and one bill that carries all of it. Bikram Sambat on every screen and register, and the counter keeps working when the internet stops.

Overview

The problem is the counter, not the medicine

A clinic's hardest half hour is not clinical. It is a queue of eight people at one desk, a paper register, a billing package written for a supermarket, and a phone ringing to ask whether a report has come back. The consultation itself is the part that works. Everything wrapped around it — registering the same patient for the third time under a slightly different spelling, finding out whether the ultrasound was billed, telling somebody where their blood sample is — is where the day is lost.

ClinicNP is built for that wrapper. A patient is registered once and keeps one number for life, P-000001 onwards, never reused and never reset at year end. Every visit attaches to that record with its own number inside the fiscal year, V-2083/84-000001, so the register reads the way a Nepali clinic's register has always read. A patient from eighteen months ago is found by name, phone, or patient number, and their whole history and every attached report come back on one card.

The bill is one bill. A consultation, an ultrasound, an ECG, two lab tests, and the prescription leave the counter as a single invoice with one number and one payment, because that is what the person at the desk is actually being asked for. Services sit in their own block with the doctor on the line, medicines carry the unit, the batch, and the expiry, and the whole thing is driven from the keyboard rather than from a mouse — one search box finds a medicine or a service, and every counter action has a key.

Bikram Sambat is not a display setting here. BS dates are on every screen, every register, and every printed report, the year runs Shrawan to Ashadh, and a closed year stays readable and prints unchanged forever. That last part matters more than it sounds: an owner who cannot reprint last year's register in the form it was filed has not replaced the paper, only added to it.

Worth reading alongside this: software development company in Nepal, ready made systems from Infobytes Nepal, and web development in Nepal.

How We Help

How Infobytes Nepal solves these challenges

One patient record per person for life, with duplicate detection that catches a matching name and phone on save and leaves the merge decision to the owner.

One invoice series carrying services and medicines together, with one payment, one number, and one set of books behind it.

Five stamped laboratory stages, so a sample's position and the time it got there are a screen rather than a question.

Doctor shares calculated per line as the bill is raised, on a percentage, a fixed amount, or a share of listed services, and totalled into a payout sheet.

Service revenue reported by group and by service, so a machine's earnings can be read against what it cost.

Billing and patient registration that carry on through a full business day of zero connectivity and reconcile themselves afterwards.

A counter built for a clinic: a service needs a patient, a medicine-only bill can stay anonymous, and a bill can be held while the next person is served.

Fiscal years closed properly, with a backup taken first, and closed years that stay readable and print unchanged.

Included

Services and features

These areas can be shaped into a focused scope depending on your team, budget, timeline, and current workflow.

Patient records with one lifetime number and duplicate detection
Visits with optional vitals, complaint, findings, and advice
Appointments that become a visit in one keystroke
Doctor profiles, NMC number, and four ways to share revenue
Doctor payout sheets calculated per billed line
Laboratory worklists from collection to handing the report over
Partner laboratory statements: billed, cost, margin, paid, owed
One invoice for services and medicines together
Cash, QR, and credit with settlement from the bill register
Pharmacy stock by batch and expiry, with expired stock held back
A4 invoice, OPD slip, and lab dispatch slip from the browser
Bikram Sambat dates, fiscal years, and a guided year-end rollover
Offline billing and registration with automatic reconciliation
Four server-enforced roles and a signed activity log
Fifteen registers and reports, every one exportable to Excel

Process

A practical process from idea to improvement

01

Decide which halves you are switching on

ClinicNP is one system with two modules, clinic and pharmacy, and each is switched on or off on its own. A clinic with no dispensing counter runs the clinic half alone. Switching a module off removes its screens, its menu, and its server routes rather than hiding them, and never deletes anything, so the decision is reversible.

02

Load your services, rates, and doctors

Your service catalogue is defined as you actually sell it: name, short code, group, rate, whether a doctor is required on the line, whether it goes to an outside laboratory and at what partner cost, whether it keeps a file, and the follow-up rule. Doctors are loaded with qualification as printed, specialty, NMC number, and the share basis that drives their payout.

03

Open the fiscal year and bring the patients in

The current Bikram Sambat year is opened, your active patient list is imported so the counter is useful on day one, and opening stock is entered by batch and expiry if the pharmacy half is on.

04

Train the counter, then the doctors

The person raising bills and the doctor checking their own list use completely different screens, and they are trained separately on the ones each will touch. Counter training is hands on the keyboard, because that is how the counter is meant to be driven.

05

Go live and watch one real week

We start on live patients with support on the phone, watch a full week including a busy morning and an evening day close, and adjust the service catalogue, the print layouts, and the reports against what the week actually showed.

Why Infobytes Nepal

Built for practical teams in Nepal

Built in Nepal for a Nepali clinic: Bikram Sambat throughout, fiscal years that close properly, and registers that print the way they were filed.

The counter survives the internet. Billing and registration carry on through a full business day with no connectivity and reconcile by themselves.

One counter and one invoice across the clinic and the pharmacy, rather than two systems and two reconciliations.

Built for a keyboard, because the people using it are working a queue, not exploring a dashboard.

Support on the phone, in Nepali, from the team that wrote the software.

Honest boundaries. We say plainly what ClinicNP does not do and point you at the right product when it is not this one.

Related services and products

FAQ

Common questions

What is clinic management software?

Clinic management software is one system that runs the non-clinical half of a clinic: registering patients and keeping one record per person, recording visits and appointments, billing consultations and diagnostics, tracking samples sent out for testing, dispensing medicines, calculating doctor shares, and reporting the day's money. ClinicNP by Infobytes Nepal does all of that on one counter and one invoice series.

Is there clinic management software made in Nepal?

Yes. ClinicNP is built and supported in Nepal by Infobytes Nepal Pvt. Ltd., with Bikram Sambat dates on every screen and register, fiscal years that run Shrawan to Ashadh and close properly, and support on the phone in Nepali. It is designed for the way a Nepali polyclinic actually bills, which is one counter carrying consultations, diagnostics, lab tests, and the prescription together.

Does ClinicNP work without internet?

Yes. Billing and patient registration carry on through a full business day of zero connectivity, held in an outbox and sent the moment the line comes back, and patient numbers are assigned without collision even from two devices at once. The medicine catalogue and the patient list are cached on the machine so search still answers, and it installs like an app on the counter machine, a tablet, or the owner's phone.

Can ClinicNP handle a clinic that also has a pharmacy?

Yes, and that is the case it was built for. The clinic and pharmacy halves are two modules of one system sharing one counter, one invoice series, one patient record, and one set of books, so a consultation and the prescription that follows it leave as a single bill with one payment. Each half can also be switched on or off on its own without deleting anything.

Does ClinicNP enter lab results and print report cards?

No, and that is deliberate. ClinicNP bills a test, follows the sample through five stamped stages, and keeps the report that comes back against the patient's visit, which is the counter around a laboratory. Entering results, holding reference ranges, producing report cards, and interfacing with analysers is a laboratory information system, and that is our other product, Nidanyo.

How are doctor shares calculated?

Four ways, set per doctor: nothing, a percentage of the consultation, a fixed amount per consultation, or a percentage of listed services. The share is calculated on each line as the bill is raised rather than reconstructed at month end, and totals into a payout sheet per doctor that exports for the month.

What does ClinicNP print?

The A4 invoice on your own letterhead, marked TAX INVOICE when you are registered for VAT; the OPD slip with the patient, visit number, doctor, and complaint plus a large empty area for the doctor's handwriting; the lab dispatch slip that goes with the sample; and refund and stock-out notes on an 80 mm roll with a signature line. All of it prints through the browser from an ordinary office printer, with no drivers to install.

Can staff be stopped from changing a rate on a bill?

Yes. Editing a rate is a permission the owner switches on or off per user, an edited line is marked as edited on the bill itself, and the change is signed and logged with a name and a time. Bills are never deleted either: a cancelled bill stays visible to the owner with who cancelled it and when.

How much does ClinicNP cost?

ClinicNP is quoted by the size of the clinic and the modules you switch on rather than sold at a list price, and it is substantially cheaper than commissioning the equivalent, which for custom software in Nepal typically starts around NPR 200,000 for a focused first version. Tell us your daily patient count, how many counters you bill from, whether you dispense medicines, and how many doctors take a share, and you get a written quotation at no charge.

How long does it take to get a clinic running on it?

For a single counter clinic with a settled service list, expect one to three weeks from catalogue setup to go live, including training and a parallel run alongside your current process. What takes the time is almost never the software: it is agreeing the service catalogue, the rates, and the doctor share basis, because those are usually written down for the first time during setup.

Keep reading

Explore more from Infobytes Nepal

Software and systems we build

Custom software, industry systems, and automation built around how a Nepali business actually runs.

Ready to discuss?

Build the next practical step with Infobytes Nepal.

Share your requirement, current workflow, or growth goal. We will help you identify a focused and realistic digital direction.

Contact Infobytes Nepal