PMNDP-covered dialysis patients grew 86% in four years, and peer-reviewed Indian research keeps finding real water quality compliance gaps in real dialysis units. Here's what a dialysis center actually needs the software running it to catch.
India's chronic kidney disease burden is large enough that estimates vary by a wide margin depending on methodology — population-based studies have found CKD prevalence anywhere from under 1% to over 17% of adults, depending on the diagnostic criteria and population screened. What's consistent across every credible source is the direction: growing. A 2025 Lancet-based analysis found India ranks second globally for chronic kidney disease burden, though it also found CKD prevalence in India has fallen 14.6% since 1990 even as the global figure rose 3.5% — a genuinely mixed picture worth stating honestly rather than reaching for the more alarming half of the finding alone.
The range in prevalence estimates deserves a moment of its own, because it's easy to misread wildly different numbers as sloppy research rather than genuinely different measurement choices. A study using a high serum creatinine cutoff in south Delhi found prevalence around 0.785%; the multi-centre SEEK-India study, screening nearly 5,600 subjects across 13 academic and private centres with broader diagnostic criteria including proteinuria, found 17.2%. Neither study is wrong — they're answering slightly different questions about what counts as CKD, and a hospital administrator citing "the CKD prevalence rate" should know which definition a given figure is actually using before repeating it as a single settled number.
What's less ambiguous is the demand side: India has an estimated 800 per million population living with CKD and an ESRD incidence commonly cited between 150 and 229 per million population annually, alongside roughly 820-plus practicing nephrologists and over 710 hemodialysis units nationally, most concentrated in South India, per figures reported in nephrology literature. That's a meaningful capacity gap relative to demand growth, and it's part of why PPP-mode expansion under PMNDP specifically, rather than public capital investment alone, has been the government's chosen path to scale access.
The Pradhan Mantri National Dialysis Programme (PMNDP), rolled out on 7 April 2016 under the National Health Mission in a public-private partnership model, gives the clearest measured trend. The programme's official portal describes its structure and dual components in full. Patients availing dialysis services under PMNDP grew from 2.43 lakh in FY 2019-20 to 4.53 lakh in FY 2023-24, according to a government reply in the Lok Sabha — an 86% increase in four years.
PMNDP now operates across all 36 states and union territories, covering 751 districts through 1,704 dialysis centres as of the most recent figures available. The programme covers both haemodialysis (HD) and peritoneal dialysis (PD), and its IT platform, launched in May 2022, links every participating centre into a renal registry with ABHA-based patient identification — explicitly designed to enable "One State, One Dialysis" portability, and eventually "One Nation, One Dialysis," so a patient can access care across facilities and states without restarting registration each time.
For a private centre, PMNDP participation is a genuine, active choice rather than a default — it means agreeing to serve BPL patients under the programme's terms alongside whatever private patient base the centre otherwise serves, and it means the centre's records structure needs to satisfy the registry's ABHA-linked format specifically, not just generically capture patient identity in whatever format the rest of the hospital's systems happen to use. A dialysis unit that treats both PMNDP and private patients through the same software needs that software to handle both record structures correctly, side by side, without one leaking into or corrupting the other.
Water quality is where dialysis software earns its keep, because the international standard is specific and the real-world compliance record in India is documented, and mixed. The Association for the Advancement of Medical Instrumentation, working with ISO, sets the governing standards: ISO/ANSI/AAMI 13959:2014 for water used in hemodialysis, 11663:2014 for dialysis fluid quality, 23500:2014 for preparation and quality management guidance, and 13958:2014 for the concentrates used to make dialysate. The AAMI threshold for product water is a maximum of 200 CFU/mL for microbial contamination and 2 IU/mL for endotoxins, alongside chemical contaminant ceilings — aluminum at 0.01 mg/L, fluoride at 0.2 mg/L, total chlorine at 0.1 mg/L among others.
A March 2025 study published in Cureus, conducted at the Regional Institute of Medical Sciences in Imphal across roughly three and a half years of sampling, tested water at four points in the dialysis system — product water, storage water, middle port water, and return water — and found unsatisfactory microbial growth against the AAMI standard in several product water and storage water samples, with Acinetobacter baumannii, a multidrug-resistant organism, detected across all four water types. The full study is published on PubMed Central for anyone drafting an internal water-testing protocol who wants the primary methodology rather than a summary. A separate, earlier Indian study found 16% of dialysate samples non-compliant with AAMI's RD52 standard, with Pseudomonas and Citrobacter species also detected. Neither study found a facility deliberately ignoring water quality — both describe exactly the kind of intermittent, hard-to-catch-manually failure that a fixed testing schedule with automatic flagging is built to prevent, and that a testing log kept on paper or in someone's memory routinely misses.
This is the single clearest example on this entire site of a compliance requirement that isn't a theoretical regulatory risk — it's a documented, recent, peer-reviewed finding of real gaps in real Indian hospitals. Contaminated dialysis water introduces microbial pathogens directly into a patient's bloodstream, with real consequences: pyrogenic reactions, sepsis, chronic inflammation. Software that schedules the testing, logs the result against a pass/fail threshold automatically, and flags a missed or failed test before the next session runs is solving a problem these studies show is actually occurring, not a hypothetical one.
It would be easy to read the Imphal and earlier studies as evidence that staff need better training on water testing protocols, and training genuinely matters. But the specific failure pattern both studies describe — intermittent contamination that appears in some samples and not others, across different water points at different times — is exactly the kind of pattern a human checking a testing calendar manually will miss, and a system with a fixed schedule and automatic escalation will not. A water test that's overdue by three days on a paper log is easy to overlook amid a busy shift; a water test flagged red on a dashboard, with the next session automatically requiring an override to proceed, is a different kind of safeguard entirely.
A technical overview of AAMI dialysis water testing methodology describes the three-stage system the standards actually govern — pre-treatment (sediment filters, water softeners, chemical injection), purification (reverse osmosis, deionization, endotoxin filters), and post-treatment (storage and distribution) — each of which needs its own testing checkpoint, not just a single test at the end of the process. A dialysis unit relying on end-of-line testing alone can miss exactly where in a three-stage system contamination is actually being introduced.
Water quality is the most dramatic compliance gap because it's the one independent research has actually measured and published, but it sits alongside a genuinely large day-to-day operational load. A busy dialysis unit running multiple shifts across a bank of machines is coordinating patient scheduling, machine rotation and maintenance, consumable stock (dialyzers, tubing, concentrate), and staff rostering simultaneously — and every one of those has to reconcile against the same patient and machine records the clinical documentation depends on. A scheduling conflict that double-books a machine, or a consumable stockout discovered mid-shift, isn't a minor inconvenience in a department where patients are on a fixed, medically necessary recurring schedule; a missed session has real clinical consequences in a way a missed OPD appointment usually doesn't.
Staffing carries its own version of this pressure. A dialysis session runs several hours, and a nurse assigned to a bank of machines is monitoring several patients simultaneously through that window — checking vitals, watching for intra-dialytic complications like hypotension, and managing the machine itself. Unlike a general ward where patient acuity varies bed to bed, every patient on a dialysis unit is, by definition, undergoing an active medical procedure for the full duration of their session. A roster that doesn't account for this — treating dialysis unit staffing the same way it treats a lower-acuity ward — is understaffing a department where every single patient present is mid-procedure, not resting.
This staffing reality has a direct scheduling implication: a roster built purely against total patient count, without accounting for the fact that every dialysis patient needs continuous monitoring for hours at a time, will systematically look adequately staffed on paper while actually running thin on the floor.
Hospital groups running dialysis units at more than one facility face a specific version of the capacity problem described above: a patient whose usual centre has a machine down for maintenance, or is fully booked for a shift, needs visibility into whether a sister facility has an open slot — particularly relevant given how many dialysis patients are on a fixed, non-negotiable weekly schedule that can't simply wait for the next available slot at one location. This is the same local-speed-versus-group-visibility problem we describe for bed management and OT scheduling in multi-location hospital ERP for chains and groups, and it applies with particular urgency here because a missed dialysis session, unlike a delayed elective procedure, has direct and immediate clinical consequences.
Machine-level visibility matters as much as bed-level visibility in this context. A group deciding where to route a displaced patient needs to know not just that a sister facility has capacity in the abstract, but that a specific machine there is available, water-quality-tested and ready, at the specific time slot the patient needs — a coarse "beds available" count that ignores machine-specific readiness can send a patient to a facility that technically has room but no actual dialysis slot ready to receive them.
Each patient's recurring session slot, matched to a specific machine, with the schedule visible to staff planning water treatment and consumable stock around actual session volume.
Weight, blood pressure and relevant vitals captured before and after each session, tied to the same patient record across every visit — essential for tracking inter-dialytic weight gain and adjusting the prescription over time.
Dialyser type, flow rates, session duration and dialysate composition recorded per session, not re-entered from memory or a paper chart each time.
Microbiological and chemical testing logged against the AAMI thresholds above, with the system flagging an overdue or failed test rather than relying on staff to remember a testing calendar.
Where a patient is covered under PMNDP, session records need to be structured for the programme's ABHA-based renal registry, supporting the portability the programme is explicitly designed to enable.
OneCity's own Dialysis Unit module and its dialysis management component cover hemodialysis scheduling, machine assignment, pre/post-dialysis vitals, dialysis prescription, water quality logging and session documentation in one connected workflow. We've written a full technical deep dive on the water quality compliance requirement specifically — including the AAMI standards, the real Indian studies documenting non-compliance, and what a testing schedule needs to catch — in dialysis water quality compliance in India.
Machine maintenance scheduling deserves its own mention alongside water quality, because the two are related in a way that's easy to overlook: a dialysis machine due for scheduled maintenance is also a machine whose water-contact surfaces need verification before it returns to patient use, and treating these as two unconnected checklists — one for engineering, one for infection control — creates exactly the kind of gap where a machine gets cleared mechanically but not verified for water quality, or vice versa. A system that ties machine maintenance status and water quality verification to the same record prevents a machine from being scheduled for a patient session until both checks are actually complete, not just one of them.
Dialysis patients are, almost by definition, long-term patients — a haemodialysis patient may be on a recurring schedule for years, generating a session record every few days that accumulates into a substantial longitudinal record. That volume and duration make retention planning genuinely different from an average inpatient stay; see our full guide to medical records retention rules for Indian hospitals for how the statutory floors apply across record types. Access to a dialysis patient's longitudinal record also needs the same audit trail described in role-based access control under the DPDP Rules, particularly given how many staff touch a single patient's record across dozens of recurring sessions over time.
The water quality testing records deserve a specific retention note of their own, separate from the patient's clinical record. A testing log that shows a facility's compliance history over months or years is exactly the kind of document that matters most during an accreditation review or, in the worst case, an investigation following a patient adverse event — and it needs to survive independently of any single patient's own record retention schedule, since it documents the facility's equipment and process, not an individual person's care.
This distinction between a patient record and a facility record is easy to lose when both live inside the same software, and it's worth building the retention rule around the record type rather than around whichever module happens to generate it. A hospital that purges old patient records on schedule, without checking whether a water quality test result got filed as part of that same patient's chart rather than as an independent facility log, can accidentally delete evidence it was legally required to keep, simply because the two record types weren't cleanly separated at the point of entry.
Given how consistently Indian studies find gaps here, a system that only records a test if someone remembers to log it is missing the actual point of the requirement.
Pre/post weight comparison across sessions should be a visible trend, not something staff reconstruct manually from separate entries.
If your centre participates in PMNDP, confirm the system's record structure actually supports the portability the programme is designed around.
See our guide to NABH accreditation software and implementation and migration services for how a dialysis unit's documentation fits the wider hospital accreditation picture.
PMNDP is a National Health Mission scheme, rolled out on 7 April 2016 in public-private partnership mode, providing free hemodialysis and peritoneal dialysis services to Below Poverty Line patients at district hospitals. It now operates across all 36 states and union territories, covering 751 districts through 1,704 dialysis centres, with patient numbers growing from 2.43 lakh in FY 2019-20 to 4.53 lakh in FY 2023-24.
The governing standards are ISO/ANSI/AAMI 13959:2014 for water used in hemodialysis, 11663:2014 for dialysis fluid quality, 23500:2014 for preparation and quality management guidance, and 13958:2014 for dialysate concentrates. AAMI sets a maximum of 200 CFU/mL for microbial contamination and 2 IU/mL for endotoxins in product water, alongside specific chemical contaminant limits.
Not consistently. A March 2025 peer-reviewed study at a tertiary hospital in Imphal found unsatisfactory microbial growth against the AAMI standard in several product and storage water samples, with a multidrug-resistant organism detected across all water types tested. A separate study found 16% of dialysate samples non-compliant with AAMI's RD52 standard. These are documented findings, not hypothetical risks.
Contaminated dialysis water introduces microbial pathogens directly into the patient's bloodstream during treatment, with documented risks including pyrogenic reactions, sepsis, and chronic inflammation.
The PMNDP IT platform, launched in May 2022, links participating dialysis centres into a renal registry built around ABHA-based patient identification, explicitly designed to support patient portability across facilities and, eventually, across states — described as "One State, One Dialysis" moving toward "One Nation, One Dialysis."
Estimates vary significantly by study methodology, ranging from under 1% to over 17% of the adult population depending on diagnostic criteria used. A 2025 Lancet-based analysis found India ranks second globally for CKD burden, while also finding prevalence has fallen 14.6% since 1990 even as the global figure rose 3.5% — a genuinely mixed trend worth reading in full rather than partially.
Want water quality testing that flags itself before a session runs, not after a problem is found?
Book a demo