Queue Management for NABL-Accredited Diagnostic Labs: How a QMS Maps to ISO 15189:2022 Compliance

Diagnostic laboratories in India operate under two parallel layers of quality requirements: ISO 15189:2022, the international standard for medical laboratory competence and quality, and NABL 112, the India-specific assessment criteria document that incorporates it for the National Accreditation Board for Testing and Calibration Laboratories. Both share three operational pillars that every NABL-accredited lab must demonstrate during audit — positive patient identification, confidentiality of patient information, and documented turn-around time (TAT) communication. A queue management system, deployed correctly, produces auditable evidence on all three pillars. This post maps QMS features to the standard.

Why this matters now

ISO 15189:2022, published in December 2022, raised the bar significantly on pre-examination process controls compared with the 2012 edition. NABL has aligned its 112 assessment document accordingly, and Indian diagnostic labs going through first-time accreditation or renewal are now facing far more scrutiny on workflow controls — specifically how patients are identified at every touchpoint, how their data is protected during the visit, and how TAT is measured and communicated to the requesting clinician. Manual paper-based queue systems create documented gaps that NABL assessors find quickly. An electronic queue management system, configured to ISO 15189 expectations, closes those gaps.

The audit reality is simple. When the NABL assessor walks in, they do not ask 'do you have a queue system?' They ask 'show me your patient-identification verification log for the past 30 days,' 'show me your TAT log per test type,' and 'show me the access-control list for patient data.' A properly configured QMS produces all three as exportable reports. Without it, the same evidence must be manually reconstructed from paper logs — a process that historically fails a meaningful share of first-time NABL audits.

Patient identification — ISO 15189:2022 Clause 7.2 (Pre-examination processes)

ISO 15189:2022 Clause 7.2 (pre-examination processes), and specifically the sub-clauses covering primary sample collection and patient identification, require positive identification using at least two independent identifiers at every patient interaction point. The standard examples are full name plus date of birth, or full name plus a unique patient or national identifier. NABL 112 reinforces this with explicit India-context expectations. The compliance failure pattern is well-known: a paper token that is just a number, called out at random, with no verifiable link back to the patient's identity at the registration desk.

How a queue management system addresses this clause:

• At registration, the system binds the issued token to the verified patient profile (name + date of birth + Aadhaar / UID / hospital MRN, depending on lab policy).
• Token-forwarding architecture means the same patient profile follows the same token across every downstream counter — registration → phlebotomy → radiology → reporting — with no re-keying of identifiers and therefore no transcription error opportunities.
• At each counter, when the token is called, the counter-facing screen displays the patient's full identification details for the technician's verification step; the public-facing display shows only the token number.
• Every touchpoint produces an audit log entry with timestamp, verified identifier set, counter ID and operator ID — exactly the trail an assessor wants to see.

Confidentiality — ISO 15189:2022 Clause 4.2 (Confidentiality)

ISO 15189:2022 Clause 4.2 covers confidentiality of patient information end-to-end, including both digital and physical protection. The standard expects the lab to prevent unauthorised disclosure of patient information through any channel — spoken disclosure in a public waiting area, visual disclosure on a screen, casual disclosure during counter interactions, or paper disclosure on a token slip. A queue system that calls out patient names over a public address in a crowded waiting room is, in audit terms, a documented confidentiality breach.

How a queue management system addresses this clause:

• Public-facing displays show anonymous token identifiers only (T-101, T-102), never patient names. This is the single most important confidentiality control in the standard.
• Voice announcement (where used) calls out the token and counter, never the patient name.
• Counter-facing screens that display patient identifiers are positioned at angles that block over-the-shoulder visibility from the waiting area.
• SMS-based virtual token mode lets the patient wait outside the lab building until their position is near the top of the queue — this removes the waiting-area exposure entirely.
• Supervisor dashboard access is role-restricted; only authorised staff see patient-level information, with a server-side access log that is itself part of the NABL submission.

TAT communication — ISO 15189:2022 Clauses 7.2, 7.4 and 7.5

ISO 15189:2022 explicitly requires the laboratory to define expected turn-around time (TAT) for each examination, to monitor actual TAT against the defined target, and to communicate TAT to the requesting clinician or, where appropriate, the patient. The relevant clauses span pre-examination (7.2 — including the time from sample collection to receipt in the lab), examination (7.4 — the testing TAT itself), and reporting (7.5 — communicating the result and the TAT to the requester). NABL 112 layers documentation expectations on top — a laboratory cannot demonstrate compliance with this clause without a system actively measuring TAT.

How a queue management system addresses these clauses:

• Every token logs its actual timestamps at each touchpoint — entered the queue, called to counter, sample collected, sample dispatched to the lab, result reported. End-to-end TAT is computed automatically per visit.
• Supervisor dashboards display live wait-time per queue and per counter; exceptions to the target TAT get flagged in real time so corrective action can happen before the audit, not after.
• End-of-day and end-of-shift reports export TAT data per service type in the format NABL assessors expect to see during the submission review.
• SMS notifications to the patient at sample collection, sample received and report ready serve as documented TAT communication — auditable proof that the lab is meeting its 7.5 reporting obligation.
• Historical TAT data demonstrates the trend-monitoring requirement that ISO 15189:2022 expects to see across audit cycles, not just a single snapshot.

Implementation pattern at Indian diagnostic centres

Diagnostic centres are one of the largest segments we serve at Infra DigiTech, because the multi-touchpoint patient journey — registration, phlebotomy, radiology, reporting — is exactly where a NABL-aligned QMS architecture has the most measurable impact. Recent deployments across Bengaluru include Asian Diagnostics, Padmashri Diagnostic Centre (Vijayanagar), Lotus Diagnostic Centre (Indiranagar) and Indian Institute of Science Medical Centre (Malleshwaram). Each runs token-forwarding architecture with verified patient-profile binding, anonymous public displays, role-based supervisor access, and TAT logging pre-configured for NABL audit export.

A typical NABL-aligned QMS deployment for a single diagnostic centre takes 2-4 weeks end to end — site survey, centralised controller installation, counter unit pairing, SMS-gateway configuration, role-based access setup, and a 30-day post-install validation period before the first audit. Existing display and counter wiring can typically be reused; the architecture is designed to retrofit into an operational lab without downtime.

The payback moment is the first NABL audit after deployment. The three pillars of ISO 15189:2022 compliance — patient identification, confidentiality, TAT — are now demonstrable from exportable platform reports, in the format the assessor expects. The same documentation also strengthens BCSBI-style customer-service reporting if the lab also serves corporate or insurance customers requiring service-level evidence.