NikshayBridge

What NikshayBridge does

Every TB diagnosis notified to NIKSHAY with the patient’s consent artefacts in order, treatment outcomes reported on schedule, and the facility’s notification register always current.

How you actually use it

1. 1Notify a diagnosisOn Notify a diagnosis, find the patient, set the date diagnosed, the basis (microbiological or clinical), the site (pulmonary or extrapulmonary), HIV and diabetes status and the ward or village, then Notify. An older diagnosis date is allowed on purpose, so a case remembered late shows up as late. The database keeps one open notification per patient.
2. 2Work the overdue list firstOverdue lists every open diagnosis whose 24 hours have run out with nothing recorded as sent. The hours run from the start of the diagnosis day in this clinic’s timezone against now, so they keep climbing while the row sits there; once the NIKSHAY id is recorded the row leaves the list and its clock stops at that moment. Nothing about lateness is stored.
3. 3Record the NIKSHAY idThe national portal is not connected — this deployment holds no NIKSHAY credentials, and nothing here submits anything. Record NIKSHAY id writes down the number the portal gave the person who notified the case by hand, once; that is what stops the clock, and the service refuses a second reference on the same notification.
4. 4Link the TBTrack course and report each monthLink course sets the TBTrack enrolment id once and reads it, never writing into TBTrack. Under Follow-ups, Report month takes the month, the sputum result, the weight and adherence; a month already reported on that notification is refused.
5. 5Close with an outcomeClose with outcome… offers cured, treatment completed, failure, lost to follow-up, died or not evaluated. Anything other than cured or treatment completed has to say what happened, and an outcome is recorded once.

What it does not do

It does not batch notifications — the statute says promptly, so it files promptly.

Questions clinics ask