Public Health Doesn't Have a Software Problem. It Has an Architecture Problem.
Public health departments are not short on software. They have EHRs tracking clinical encounters. They have MMIS — state-run Medicaid Management Information Systems — processing claims and managing eligibility. They have HIEs routing data between hospitals and agencies. They have disease surveillance platforms, immunization registries, eligibility engines, and inspection systems.
And yet, somehow, most of the actual work still runs on spreadsheets.
That is not a failure of adoption. It is a failure of architecture. Every one of those systems was built for a specific, narrow purpose — clinical documentation, claims processing, data exchange — and not one of them was designed for the daily reality of running a public health department. The longitudinal case management. The multi-funded programs. The workforce coordination. The community partnerships. The grant reporting. The work that actually happens between all those other systems.
So departments fill the gaps themselves. They build workarounds. They copy data from one system into another. They track things in shared drives. They make it work, because they always do. But the cost of that fragmentation is enormous — in time, in visibility, in outcomes, and in the energy of people who got into public health to serve communities, not to manage spreadsheets.
This is the problem Persimmony was built to solve. Not by replacing the systems that exist, but by being the platform that operates between and across them. The operating system for public health.
What an Operating System for Public Health Actually Looks Like
When we say "operating system," we mean the platform where the daily work of a public health department actually lives. Not a case management tool with a few features bolted on. A platform that encompasses case management, productivity and workforce mapping, communications, CRM, time study, grant tracking, coordination with community-based organizations, and reporting — all built for public health from the ground up.
In Persimmony, data is entered once and flows everywhere it needs to go. A case worker documents a home visit, and that activity is reflected in the client's case record, the grant report, the time study, and the supervisor's workload view — without anyone re-entering anything. When the entire operation runs on one platform, the work becomes visible, the reporting becomes automatic, and the coordination becomes real rather than aspirational.
This is fundamentally different from stitching together six or ten point solutions and hoping they talk to each other. It is a different architecture. One record. One workflow. One source of truth.
Why Now
Public health technology has been chronically underinvested for decades. The gap between what is possible and what is deployed has never been wider. But several forces are converging right now that make this the moment for a new architecture.
FHIR is becoming the standard. The FHIR data standard is making it possible for systems to exchange information without expensive, custom-built middleware. States no longer need massive integration hubs to move data between platforms. They need everyone on the same standard — and they need a platform where that information actually comes together. Persimmony, built API-first on FHIR, becomes the integration layer. Not a hub that routes data between other systems, but the platform where clinical, community, and operational information converges and becomes useful.
COTS is replacing custom builds. Governments are moving toward commercial off-the-shelf software and away from decade-long custom development projects. The appetite for purpose-built platforms that can be configured and deployed — rather than coded from scratch — has never been stronger.
AI is creating new possibilities. From documentation to reporting to pattern recognition across populations, AI is opening doors that did not exist even two years ago. But AI requires a foundation — clean data, unified workflows, a single system of record. Fragmented architectures cannot take advantage of what AI offers. Unified ones can.
The federal government is investing at historic scale. In December 2025, CMS announced the Rural Health Transformation Program — $50 billion in funding to all 50 states over five years to modernize and strengthen rural health care. That investment is not just about building new clinics. It is about modernizing technology, expanding telehealth, supporting remote patient monitoring, and building the data-sharing infrastructure that rural communities desperately need.
And yet the underinvestment persists. Despite all of this momentum, public health remains one of the most under-resourced sectors in technology. The systems are aging. The budgets are tight. The workforce is stretched. The need for a platform that does more with less — that consolidates rather than fragments — has never been more urgent.
The Rural Health Transformation Moment
The $50 billion Rural Health Transformation Program makes this concrete. CMS has awarded funding to all 50 states over five years to modernize and strengthen health care in rural communities. The ambition is enormous — and the timescale is short.
States are now expected to unify care delivery across outreach programs, education initiatives, telehealth, wearable devices, consumer health apps, and community-based organization coordination. That is not work that can be done on the fragmented systems described above. EHRs were not built to track community outreach. MMIS was not built to coordinate with CBOs. HIEs were not designed to pull in data from wearables or health apps. The old architecture simply cannot support what RHT demands.
And here is the timescale problem: RHT is a five-year program. States cannot afford to spend the first two years writing an RFP, the next year selecting a vendor, and the year after that building a custom system. By the time it is deployed, the program is over. States need to move now — adopting platforms that are ready today, that can tie all of their rural health initiatives together from day one, and that can grow with the program over its full lifecycle.
Rural health departments face every challenge their urban counterparts face, but with fewer resources, smaller teams, and less margin for error. They cannot afford six different software systems. They often do not have dedicated IT staff. What they need is a single platform that manages cases, coordinates with CBOs, tracks grants, monitors workforce, communicates with clients, and reports to the state — all in one place.
That is what Persimmony was built to do.
Not a Vision. A Track Record.
Persimmony is not a concept. It is a platform running today across more than 30 state and county customers, managing over $2 billion in budgets, supporting more than 2 million enrollments, and powering more than 100 unique programs.
The architecture problem in public health is real, and it has been real for a long time. The difference now is that the forces are aligned — FHIR, COTS, AI, and historic federal investment — to finally solve it. Not with more point solutions. Not with more integrations. With a platform built from the ground up for how public health actually works.
That platform is Persimmony.
