Thirty-three years after the 74th Amendment, why a city health officer still runs on a state's IT budget.

In 1992, India's 74th Constitutional Amendment gave urban local bodies — municipal corporations, municipalities, nagar panchayats — formal constitutional standing, transferring responsibility for urban planning, water, sanitation, and public health to the tier of government closest to the citizen. On paper, it was a genuine devolution of power. In practice, analysis of the Amendment's implementation over three decades describes a persistent pattern: accountability handed down to local bodies "not backed by either adequate finances or the capacity for planning and management" — and reform that has mainly benefited large municipal corporations while smaller urban local bodies remain functionally under-resourced.

The effect on public health technology specifically is that a city's health data infrastructure usually isn't decided by the people running the city's health department. It's inherited from whatever the state built, retrofitted onto whatever budget a municipal corporation could negotiate, and rarely designed around the reality that a city's health system spans municipal dispensaries, state-run PHCs, and private clinics that don't report to any of it consistently. A municipal health officer can be constitutionally responsible for an outbreak response with no system that shows them, in real time, what's happening across all three.

The gap isn't ambition — it's the fragmentation nobody assigned anyone to fix

This isn't a story about municipal governments lacking urgency. A city outbreak response team knows exactly what it needs to see: case counts by ward, bed availability across every facility type in its jurisdiction, and a supply chain view that doesn't stop at the municipal dispensary's own four walls. What it typically has instead is three separate, non-interoperable pictures — one from its own dispensaries, one it has to request from the state PHC network, and none at all from the private clinics treating a meaningful share of the same city's patients — with no single body funded or mandated to unify them. The 74th Amendment assigned the accountability. It never assigned, or funded, the integration work that accountability actually requires.

Smaller urban local bodies feel this hardest. A large municipal corporation — Mumbai, Bengaluru, Delhi — has the tax base and administrative weight to negotiate real IT budgets and, increasingly, to build its own health-tech capacity. A tier-2 or tier-3 municipality with the exact same constitutional mandate typically has neither, which is precisely the asymmetry the three-decade implementation record describes: reform that helped the corporations already large enough to help themselves, and left the rest running on whatever a state chose to extend to them.

What infrastructure built for this tier actually looks like

This isn't a case for giving every municipality a state-scale system — most municipal budgets couldn't sustain one, and don't need to. A city doesn't need a scaled-down replica of a state HMIS; it needs something architecturally different: lighter, interoperable by default with whatever the state already runs so a city isn't left maintaining its own disconnected island, and priced and staffed for a municipal reality rather than a state one. Concretely, that means designing the integration layer first — the piece that lets a municipal dispensary, a state PHC, and a participating private clinic all report into one ward-level view — rather than starting from a facility-management system and hoping interoperability gets added later.

It's also a case for treating this tier as a distinct client with distinct constraints, not a smaller version of a state health department. That distinction is why it sits explicitly in Who We Serve as its own tier rather than folded into state-level engagements, and why the standard engagement pattern here starts from budget and staffing reality rather than a state-scale specification scaled down after the fact.