As local public health agencies across Minnesota transition to FPHR annual reporting, many of us are actively learning and adapting to a new way of entering our time – while continuing to serve our communities every day. That is no small task, and your willingness to lean into this work is what makes strong data possible.
At the same time, many of us are learning that good data is about more than simply entering information into a system. Good data starts with shared understanding.
In Northeast Minnesota, our seven counties approached the FPHR reporting transition as both a technical and adaptive change, using it as an opportunity to strengthen alignment around how we define our work together. Strong organizational data is not created by a few reporting fields in Nightingale Notes – it is created when teams take time to build shared meaning, align expectations, and thoughtfully discuss how work should be understood.
Why shared definitions matter
FPHR annual reporting is intended to help Minnesota better understand:
Where public health capacity exists
What foundational and community-specific work is happening across the state, and
Where gaps or needs may require future investment
While FPHR reporting data can offer meaningful insight on its own, intentionally operationalizing shared definitions improves consistency, accuracy, and long-term data quality.
For example, if one county codes an activity under Maternal, Child, and Family Health while another codes that same activity under Chronic Disease & Injury Prevention, the data becomes harder to analyze and use for decision-making.
Shared definitions help ensure our data supports our collective story.
These shared definitions are grounded in statewide guidance developed through a collaborative, consensus-driven process led by the Statewide Community Health Services Advisory Committee (SCHSAC), local public health, and MDH, and are available for reference on the MDH FPHR definitions webpage: Definitions, Criteria, and Standards for Fulfillment of Foundational Public Health Responsibilities - MN Dept. of Health.
Why conversation matters in multi-county environments
When multiple agencies contribute data into a shared regional picture, even small differences in interpretation can affect staffing trends, workload analysis, and how our work is understood by leadership and funders.
That’s why our Northeast region prioritized conversation before implementation. We recognized that statewide reporting expectations must still be grounded in local operational realities if they are going to be implemented successfully.
Public health leaders and planners came together to:
Discuss how the state definitions apply to our local practice
Work through gray-area examples
Identify differing interpretations
Seek feedback from local staff on workflow and implementation considerations
Build consensus on shared expectations
These conversations take time, but they strengthen data quality by improving consistency across counties and building trust in the reporting process.
A special thank you to Erin Melz (Aitkin County), Joanne Erspamer (Carlton County), Susan Vitulli (St. Louis County), and NE Infrastructure Team members, Anne Graves, Mary Parsatoon, and Erika Guenther, as well as the NE Local Public Health Leadership Team, for helping lead and support this effort.
Supporting this work in Northeast Minnesota
To support this regional effort, Northeast Minnesota developed shared guidance resources including:
These resources are intended to support – not replace – professional judgement and local workflow realities. We view them as living documents that will evolve as staff raise new questions, implementation surfaces new learning, and statewide understanding of FPHR matures. So keep your questions coming!
Final thoughts
These conversations are not extra work. They are the work of building better systems.
When we take time to create shared definitions together, we build data that is more trustworthy, more useful, and more reflective of the important work happening every day in local public health. Thank you for doing the work you do.