Building public health tools for citizens, not just for systems
When people think about public-sector software, they often imagine internal systems: administrative platforms, records, workflows, and back-office processes.
Those matter a lot.
But some of the most meaningful work I did during my years building software for the Municipality of Olavarría was different.
It focused on tools made directly for citizens.
Not software designed only to help the institution operate better, but software designed to help people understand where to go, how to act, and how to access public health services with less friction.
That distinction matters.
Because public software should not only organize the inside of an institution. It should also reduce confusion on the outside.
Public tools for real situations
Two examples capture that idea well.
One was a medical report transcription tool, published by the municipality as part of the local hospital system. The interface was built around voice input and included features such as dictation, correction of the current dictation, correction of the full document, voice commands, and medical abbreviations. Even from the public interface alone, its purpose is clear: help practitioners work faster and make clinical reporting easier to complete.
The other was a health center finder for citizens, also published by the municipality. That tool allowed people to enter their address or use their device location in order to identify the appropriate nearby institution. The public interface explicitly asks for the user’s current address or device location and offers to show the closest institution, making access to the right point of care easier in situations where orientation matters.
On the surface, these may look like small tools.
They were not.
They represent a way of thinking about government software that I still believe in strongly: useful digital tools should meet people where they are, in language and workflows that make sense in the moment they need them.
Software as public guidance
One of the biggest problems in health systems is not only lack of information.
It is friction.
People do not always know where they should go. Staff do not always have time to complete documentation comfortably. Small delays and small confusions accumulate, and eventually they become part of the everyday burden of the system.
That is why I find these kinds of tools so meaningful.
A public health center finder is not just a map.
It is a way of reducing uncertainty.
And a voice-based reporting tool is not just a convenience feature.
It is a way of helping clinical information get captured more naturally and with less resistance from daily workload.
Both belong to the same broader idea:
public digital tools should make public services easier to navigate, not harder.
What this taught me
Working on public-facing health tools taught me something I still carry into every product I build: clarity is a feature.
Not in a decorative sense. In a structural one.
When software is built for citizens, every extra doubt matters. Every unclear step matters. Every unnecessary delay matters.
That kind of work pushes you to think differently.
You stop asking only whether the system works.
You start asking whether the person on the other side understands what to do next.
That shift is one of the most valuable things public-sector software taught me.
Because sometimes the best digital tool is not the most complex one.
It is the one that quietly helps someone move forward with less confusion than before.