Skip to main content

TB Notification and Nikshay: A Workflow for Private Indian Clinics

Private clinics should organise TB notification as a documented public-health handover linked to the patient's diagnosis and continuing care. Use the authorised local NTEP/Nikshay route, verify existing records and retain acknowledgement or the unresolved submission state. A Nikshay identifier, a submitted form and a completed treatment handover are different things. Notification should support timely care and contact follow-up; it should not become a barrier to assessment or an excuse to create duplicate patient records.

By Bractis · Updated · 10 min read

Indian private practitioners and clinic teams coordinating TB notification, existing Nikshay records, public-health services and ongoing patient care.

Start from the notification requirement and the actual diagnosis

The Ministry of Health's notification of 16 March 2018 requires healthcare providers to notify TB patients to the designated local public-health authority and specifies practitioner and laboratory reporting formats. It also sets out pharmacy-related reporting and public-health follow-through. Use the current authorised process and local programme support; a clinic spreadsheet is not itself a submission.

The notification includes bacteriologically established cases and clinically diagnosed cases started on anti-TB treatment within its stated definition. A presumptive-TB investigation should therefore remain distinguishable from the clinician's diagnosis and treatment decision. Do not convert every cough, test order or uncertain laboratory item into the same case state.

Keep the diagnosing clinician, date, basis and source evidence visible. Retain the original laboratory wording and relevant report versions. Notification staff should transcribe verified information and escalate uncertainty, not infer a diagnosis or drug-resistance interpretation from a partial screenshot.

This article deliberately does not repeat old penalty wording, assume a universal portal deadline or reproduce benefit amounts. Those details can change or require specific legal and programme context. Check the current Central TB Division materials and designated programme office for the operational requirements that apply.

Source: MoHFW: TB Notification, 16 March 2018

Source: Central Tuberculosis Division: TB Surveillance and Notification

Distinguish the clinic file, health-establishment identity and Nikshay record

Confirm the patient using appropriate identifying details and the available source documents. Names may be transliterated differently across a laboratory, a hospital and a local clinic. A shared phone, similar name or changed address should not be the sole basis for joining records.

Keep the clinic's patient identifier separate from any Nikshay patient identifier and the provider or health-establishment registration. They refer to different entities. A screenshot of a provider login does not establish that a particular patient has been notified.

Ask about prior notification and treatment through another service, then use the authorised programme process to verify and reconcile the record. If identity or episode matching is uncertain, obtain programme assistance rather than creating a duplicate to clear the clinic's pending queue.

Do not invent identity fields to pass a form validation. Record the missing or disputed information and use the approved resolution route. Clinical assessment and the appropriate care response should continue while administrative clarification is handled.

Prepare a traceable notification packet with a named owner

Assign a responsible clinic role and a covering arrangement. The role needs access to the information required for the task, an authorised submission route and a way to ask the clinician about unresolved details. Shared staff passwords make it difficult to know who submitted or corrected information.

Prepare the relevant identity and contact information, diagnosis evidence, dates, treating service and other fields required by the applicable reporting process. Preserve the source used for each consequential detail. The clinic should be able to explain whether a value came from a laboratory report, the clinician's assessment or a patient account.

Check whether the packet relates to a new diagnosis, follow-up information, an amended result or a patient already linked to care elsewhere. A new report file is not necessarily a new patient or a new episode. Keep the original and corrected evidence linked rather than replacing it without explanation.

Record the channel, date, submitting person and reference or acknowledgement available. A saved local draft should remain visibly unsent. If a submission fails or its outcome is uncertain, retain that state and investigate through the authorised route before repeatedly submitting the same information.

Use local tracker states that show the next responsibility

The following states are an original clinic-tracker proposal, not a claim about the current Nikshay interface. Their purpose is to stop 'entered' from meaning both an internal draft and a confirmed external handover.

On a narrow screen, scroll the table horizontally to read all columns.

Local notification tracking without false completion
Local stateEvidenceNext responsibility
Clinical information pendingNamed missing diagnosis detail or sourceResponsible clinician resolves the clinical question.
Record matching pendingPossible existing record and the identity uncertaintyAuthorised staff/programme contact verifies the match.
Ready for submissionClinically confirmed packet and authorised routeAssigned person submits through the approved process.
Submitted, outcome unconfirmedAttempt time/channel and available responseCheck receipt or failure without blind duplicate submission.
AcknowledgedExternal reference or documented receipt linked to the patientConfirm downstream care and public-health responsibilities.
Correction neededOriginal submission and new evidence/reasonUse the authorised correction process and retain its outcome.
Care handover openOutstanding clinical or contact-follow-up arrangementNamed care or programme professional completes the agreed action.

Keep treatment, contact evaluation and support as separate work

Notification creates an important public-health connection, but it does not prove that treatment has started, that the patient understands the plan or that follow-up responsibility has been accepted. Record the actual care arrangement, the treating professional and unresolved barriers.

The 2018 notification describes public-health actions following receipt, including counselling, support and contact-related activity. Coordinate those responsibilities with the current programme service. Do not assume they have occurred because a patient identifier exists, and do not copy historical preventive-treatment wording as a current regimen.

Record whether the patient needs clarification of where treatment or investigations will occur and whom to contact if there is difficulty. Keep appointment, attendance, dispensing, actual use and clinical review distinguishable. A stock issue or a portal update alone cannot establish treatment completion.

For contacts, arrange the appropriate programme or clinical evaluation and track the handover without making a diagnosis from family relationship. Contact screening and preventive-treatment decisions require the responsible service's assessment under current guidance. Do not prescribe a regimen from a notification worksheet.

Where the patient moves between districts or providers, preserve the handover evidence and accepted responsibility. Closing a local task because the person moved should not conceal uncertainty about who will continue care.

Source: MoHFW: TB Notification, 16 March 2018

Explain the public-health handover without exposing unnecessary information

Explain why information is being notified, which service will receive it and what follow-up the patient should expect. Separate this public-health purpose from marketing, a public testimonial or an informal message to relatives. An obligatory reporting task does not justify unrelated disclosure.

Confirm suitable contact arrangements, particularly when a phone is shared or the patient is concerned about stigma. Record the practical communication route agreed with the patient and programme team. Do not promise that every contact can remain invisible to others if the process or household circumstances cannot support that promise.

Use authorised channels and appropriate access for notification data. Avoid putting a whole clinical chart into an uncontrolled spreadsheet or messaging group simply because several staff members are helping. Send the required information for the task and retain the record in the clinic's governed process.

If a patient raises concerns or refuses a proposed contact arrangement, document the concern and obtain appropriate clinician/programme guidance. Do not misrepresent notification as an optional promotional consent, and do not let an unresolved communication preference replace the applicable reporting obligation.

Keep one concise summary of notification and continuing care

This original outline supports local accountability. It is not the official reporting form and does not replace the current NTEP/Nikshay instructions or the treating clinician's TB care plan.

Reconcile diagnoses and acknowledgements without inflating case counts

Compare the clinic's relevant diagnosed episodes with the notification tracker at an agreed operational review. The purpose is to identify missing acknowledgement, unresolved matching, corrections and unfinished care handovers. Do not use the number of laboratory PDFs as the denominator.

Review duplicate reports and repeated visits as events within the appropriate patient episode. Keep an existing notification from another service visible rather than presenting it as a newly notified case by this clinic. Where programme rules determine episode classification, use those rules and the authorised clarification route.

Audit timeliness using actual event dates: diagnosis, attempted submission, acknowledgement and accepted care responsibility. Do not substitute the date a staff member updated the spreadsheet. A clean dashboard should be the consequence of resolved work, not of backdating or deleting difficult entries.

When considering clinic software, ask for observable evidence of any claimed integration. A link to Nikshay or a local notification checkbox is not proof of an authorised working exchange, successful submission or reconciliation of external identifiers.

Fictional example: six documents, three patients and different next actions

A clinic reviews six source events: two diagnostic documents for patient A, one record for patient B already notified elsewhere, one clinically established case record for patient C, and two follow-up documents for A. There are three patients in this example, not six new notifications. The team verifies B's existing linkage, handles the notification requirements for A and C through the authorised process, and adds A's follow-up evidence to the appropriate record. It separately checks who owns continuing care for all three. The count is an illustration of reconciliation, not a rule for classifying recurrence or a substitute for programme definitions.

TB Notification and Care-Ownership Worksheet

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Case basis
Which clinician confirmed the diagnosis, on what date and evidence, and is the episode distinct from a presumptive investigation?
Matching
Does an existing Nikshay record apply, how was identity verified and what uncertainty remains?
Acknowledgement
What proves the authorised submission was received, and who resolves failures or corrections?
Care continuity
Who owns treatment follow-up, contact evaluation and support, and what confirms that each handover was accepted?

Questions doctors ask

Do private Indian practitioners have a TB notification responsibility?

The Ministry's 16 March 2018 notification requires healthcare providers to notify TB patients to the designated public-health authority. Use current authorised NTEP processes and programme support; an internal clinic entry alone is not notification.

What if the patient already has a Nikshay identifier?

Verify that it belongs to the correct patient and relevant record through the authorised process. Reconcile the existing linkage and responsibilities rather than automatically creating a duplicate to complete the clinic's queue.

Does a submitted form prove TB care is complete?

No. Submission, acknowledgement, treatment arrangements and ongoing public-health follow-through are different events. Retain the evidence and responsible person for each.

Can a clinic start every household contact on the same preventive regimen?

Contact evaluation and preventive-treatment decisions belong to the responsible clinical or programme service using current guidance. A family relationship or notification worksheet does not establish eligibility or select a regimen.

What demonstrates a working Nikshay integration?

Ask for authorised scope and an end-to-end demonstration with test data: identity matching, submission, acknowledgement, errors and corrections. A portal link or a local complete checkbox does not establish that integration.

Sources and scope

Updated on . The proposed local states, reconciliation example and worksheet are original operational guidance. They are not the official notification form, a TB treatment protocol, a current benefits schedule or a legal compliance certification. No independent clinical or legal review is claimed.

  • MoHFW: TB Notification, 16 March 2018

    Primary Gazette notification used for reporting scope and public-health follow-through. Official indexed text was reviewed; direct retrieval timed out. Historical penalties and preventive-treatment regimens are not reproduced.

  • Central Tuberculosis Division: TB Surveillance and Notification

    Current official resource directory checked on 24 October 2026. Use the designated programme office and authorised instructions for present operational details; no Bractis integration or live submission was tested.

Try the workflow
with Bractis.

Use invented TB records to ask Bractis how local notification work, existing external identifiers and accepted care responsibility would be recorded. Require evidence for any claimed external integration; no live patient submission is needed for this evaluation.

Request a clinic demo