Skip to main content
Back to products

00 Product

NADI

From the counter to the claim, in one system

Hospital information system for private hospitals & clinics.

Built and run by Tech Lead Malaysia.

Talk to us
Status
Ready to use
Platforms
Web
Sector
Healthcare
Built by
Tech Lead Malaysia Sdn. Bhd.
MOF
357-0002439120
NADI screens
NADI

01 Problem → Solution → Impact

Care given is actually paid for: accurate bills, panel claims from one desk.

The workflow, end to end

was manual, now in the systemdone in the system

  1. 01Registerdone in the system
  2. 02Queuedone in the system
  3. 03Pharmacydone in the system
  4. 04Wards and bedsdone in the system
  5. 05Billingmanual → system
  6. 06Panel claimsmanual → system
  7. 07e-Invoicemanual → system
  8. 08Receivablesmanual → system
  1. Before

    Panel claims paid late

    Root cause

    Retyped into each panel's portal

    Tech Lead solution

    One claims desk, deadlines counted, payor rules checked

  2. Before

    Bills fixed by hand

    Root cause

    No control after the bill is finalised

    Tech Lead solution

    Missing charges checked, changes by numbered notes

  3. Before

    Old system cannot change

    Root cause

    Old desktop app, data locked in a server

    Tech Lead solution

    Browser system, e-Invoice and receivables built in

Impact

  • UsersExpected result

    Claims no longer retyped

  • ManagementExpected result

    Receivables by payor, no spreadsheet

  • OrganisationExpected result

    No missed charges, no silent bill changes

  • StrategicExpected result

    e-Invoice and Act 586 in the workflow

Modules in one system
16

What we bring that clients don't see Accounts close after discharge: only the Business Office can add a late charge, with a reason, recorded in the audit log.

Case scenarioIllustrative scenario

Discharge day for an insurance panel patient

The old way

A panel patient is ready to go home, but the cashier adds a late lab charge by hand and the bill is reprinted. A week later the claims officer retypes that bill into the panel portal and finds the deadline almost gone.

Root cause: Bills and claims sit in separate systems with no control after the bill is finalised.

Same-day result: The bill and the claim are done on discharge day, with no retyping and no missed charges.

With the system

  1. The nurse marks the discharge on the bed board; the bed joins the cleaning list.

    NADI hospital bed board across every ward
  2. The cashier opens the bill: doctor fees are separated and missing charges are checked before finalising.

    NADI bill with doctor fees separated from hospital charges
  3. The account closes after discharge; late charges only by the Business Office, with a reason, in the audit log.

  4. The claim appears on the claims desk with the payor deadline counted, ready to send.

    NADI claims desk for every payer

Who else needs this Private hospitals, medical centres and specialist clinics

If your panel claims are still retyped and bills still fixed by hand, NADI is a finished system: one to three months to set up, including data migration and staff training.

Bring us the problem. In a working session, the team that built this system will show you the IT way to solve it, with your data.

Email [email protected]

02 What it does

What NADI does.

Our hospital information system for private hospitals and clinics. It follows the patient from the counter to the cashier: a queue by station, a bed board across every ward, pharmacy checks before dispensing, and bills that keep doctor fees apart from hospital charges. Claims for every payer run from one desk, and each hospital or clinic switches on the modules it needs.

  1. 01Patient queue by station, from registration to the cashier, with waiting times and priority flagsPatients move from registration to triage, doctor, pharmacy and cashier, and each station shows who is waiting and for how long.
  2. 02A bed board across every ward: occupied, vacant, reserved, cleaning and maintenanceNurses see every bed across the wards, with the beds patients are waiting for and the day’s discharges.
  3. 03Pharmacy dispensing with allergy and interaction checks, batches picked by earliest expiry and bilingual labelsThe pharmacist checks allergies and interactions, picks the batch that expires first and prints a label in two languages.
  4. 04Bills that keep doctor fees apart from hospital chargesDoctor fees follow the Thirteenth Schedule and stay apart from hospital charges, so each part of the bill can be checked on its own.
  5. 05Accounts close after discharge; late charges come only from the business office, with a reason, and are loggedAfter discharge the account closes; a late charge needs the business office and a reason, and it is logged.
  6. 06One claims desk for every payer: drafts, queries, rejections and paymentsEach claim shows its payer and the days left before it lapses, with drafts, queries and rejections kept apart.
  7. 07Stock by batch and expiry, with reorder levelsStock is tracked by batch and expiry date, with alerts when an item falls below its reorder level.
  8. 08Modules switched on per hospital or clinic, with roles and permissions set by its own adminA module that is not switched on disappears from the menus and search, and each customer’s admin sets roles and permissions.

03 Inside the system

How NADI works, step by step.

Screens from the product, with sample data.

Every bed, every ward, one board

Occupied, vacant, reserved, being cleaned or under maintenance, with the beds patients are waiting for and today’s discharges beside it.

NADI hospital bed board across every ward
NADI · Every bed, every ward, one board
  1. 01The queue, station by station
  2. 02A bill that holds up
  3. 03Checked before it is handed over
  4. 04Every payer on one desk
  5. 05Stock that does not expire on the shelf
  1. 01

    The queue, station by station

    Registration, triage, doctor, pharmacy and cashier, each with its waiting time and priority flags for the elderly, pregnant patients and emergencies.

    NADI outpatient queue board by station
    NADI · The queue, station by station
  2. 02

    A bill that holds up

    Doctor fees under the Thirteenth Schedule sit apart from hospital charges; once the bill is final, only the business office can add a late charge.

    NADI bill with doctor fees separated from hospital charges
    NADI · A bill that holds up
  3. 03

    Checked before it is handed over

    Allergies and interactions are checked, controlled medicines are flagged, and the pharmacist hands over from the same queue.

    NADI pharmacy dispensing queue
    NADI · Checked before it is handed over
  4. 04

    Every payer on one desk

    Drafts near their deadline, unanswered queries, rejected claims and payments still awaited, for every panel and insurer.

    NADI claims desk for every payer
    NADI · Every payer on one desk
  5. 05

    Stock that does not expire on the shelf

    Expired and expiring batches, items below their reorder level and stock adjustments waiting for approval.

    NADI pharmacy and store inventory with expiry alerts
    NADI · Stock that does not expire on the shelf

04 Why it stands out

Why NADI stands out.

  1. 01

    Follows the patient, not the menu

    Each role lands on its own work list, and finishing a consultation sends the patient on to the pharmacy and the cashier.

  2. 02

    Bills that hold up to an audit

    Charges are checked for gaps before a bill is finalised, and any change after that becomes a numbered debit or credit note.

  3. 03

    One desk for every panel

    Payer rules are checked before a claim goes out, and lump-sum payments are matched back to each claim to show what was underpaid.

  4. 04

    Switched on module by module

    Each hospital or clinic gets its own name and logo on letters and receipts, and only the modules it needs.

05 Build · Host · Run

Build. Host. Run.

The team that built this product can also host it and keep it running.

  1. B Build

    Built by one team

    One roof: build, host and maintain.

  2. H Host

    Hosted, if you want, on our own servers in a Kuala Lumpur data centre

    We run our own server infrastructure in a Kuala Lumpur data centre, on-shore in Malaysia, and offer it as hosting: from a single website to systems whose data must stay in the country.

    See hosting options

  3. R Run

    Managed operations

    Patching, backups and monitoring by the team that built the system.

07 Contact

Talk to us about NADI.

Tell us what you need to run. We will reply with an honest view of scope, timeline and the right procurement route.

Who you will meet

  • Razlan RazakFounder & Director
  • Nabil RadzuwanProject Manager
  • Zahrin AzamCo-Founder
  • Adzrul NizamBusiness Development Manager
  • Mohammad NorBusiness Development Manager

Razlan Razak (Founder & Director) and Nabil Radzuwan (Project Manager) lead the first working session, with Zahrin Azam (Co-Founder), Adzrul Nizam and Mohammad Nor (Business Development) alongside.

What happens next

  1. 1You tell usWhat you need to run, by WhatsApp, e-mail or a brief.
  2. 2We replyAn honest view of scope and timeline.
  3. 3The right routeThe procurement route that fits your system.