Case Study8 min read4 May 2026

Tech with a Soul: How Digiflux Helped Strengthen India's TB Care Tools

Not every build is a commercial product. Here is what we learned shipping digital health tooling for Ni-kshay SETU, and why public-impact software demands a different kind of craft.

Healthcare professional using a tablet

Software can optimise a sales funnel. It can also strengthen a public health system. Over the last year, Digiflux worked as a technical development partner on Ni-kshay SETU, a digital platform supporting tuberculosis care capacity across India, alongside consultant development partner Dr. Harsh Shah and the broader public-health team driving the programme.

The problem was not “more content”

Frontline TB care depends on healthcare workers who need current guidelines, practical decision support, and answers in the moment, not another PDF buried in a shared drive. Ni-kshay SETU (Support, Engage, Train, and Update) was built to meet that need: role-specific learning, clinical decision support, and an AI-assisted chatbot aligned with National Tuberculosis Elimination Program protocols.

  • Cross-platform access: Android, iOS, and web for workers in very different settings
  • Mobile-first UX with offline-friendly patterns where connectivity is unreliable
  • AI-assisted query handling trained on a large corpus of TB-related questions
  • Privacy-conscious design, the platform is oriented around knowledge and support, not storing personal health records

Public-impact software is judged differently. Reliability, clarity, and trust matter more than feature novelty. If a field worker cannot use it under pressure, it does not count.

Medical team reviewing information together
Public-impact software is judged by trust under pressure, not feature novelty.

What “tech with a soul” means in engineering terms

It means treating domain experts as co-builders, not ticket writers. Dr. Shah’s guidance on requirements and direction at every stage kept the build grounded in how TB programmes actually operate. Our job was to translate that into software that ships, scales, and stays maintainable, without overbuilding.

  • Translate clinical and programme requirements into clear product scope
  • Ship modular surfaces that can be updated as guidelines evolve
  • Prioritise accessibility and language realities over demo polish
  • Keep the architecture simple enough for long-term public stewardship

Why this work belongs next to our commercial AI practice

The same principles apply: do not automate chaos, do not ship shallow chat without operational logic, and do not disappear after go-live. Whether we are wiring a reasoning layer for a SaaS company or supporting a public-health platform, the craft is the same, systems that help people act with better information under real constraints.

Eight years in, Digiflux still believes the best technology is the kind that creates measurable impact, in boardrooms and in the field.

Work with us

Turn this into
a live deployment.

We scope, build, and ship in weeks. First conversation is free.

Start a conversation