One Health in Helsinki: A Shared Question Needs More Than One Kind of Knowledge
By Jonathan Anthony Burkett
Reporting and original analysis | November 4, 2026
When a problem crosses several fields, agreement that collaboration is important is only the beginning. The harder task is to make the different contributions fit a question that people can actually work on together. A researcher may bring one kind of measurement, a field worker another kind of observation and a community participant knowledge of how a proposed activity will meet everyday life. A public One Health program scheduled in Helsinki today provides an occasion to consider those relationships. The useful question is how a partnership can make room for different expertise without reducing every contributor to the same role.
The University of Helsinki’s 2026 One Health Day listing announces talks and a panel on Africa–Europe collaboration at Think Corner on November 4, from 17:00 to 19:00 EET. Its program includes fieldwork, biodiversity, waste management and research with farmers. The listing is a program announcement, not a record of what speakers said or of the discussion’s conclusions. Separately, the CDC’s November 3 campaign toolkit identifies One Health Day as an opportunity to recognize connections and partnerships. This article offers original analysis of collaboration and public communication, with no diagnosis, treatment advice or claim about a particular health intervention’s effectiveness.
Define the question before assigning the answer
An interdisciplinary conversation can become difficult when participants use the same broad term for different tasks. One person may be asking how to measure a change, another how a service could respond and another how the affected people understand the issue. All may be relevant, but they do not automatically form one research question. A useful first step is to describe the decision or uncertainty that brings the group together. Then ask which contribution helps answer which part. The purpose is to make the work specific enough that the partnership can explain why these people need to be in the same conversation.
Imagine a proposed study in a farming community. The example is hypothetical and does not describe a project in the Helsinki program. A researcher may want repeated observations across a period, while participants need to know what time the activity requires and how the results will return to them. A design that considers only the measurement could overlook the conditions that make participation practical. A design that considers only convenience could leave the research question unanswered. Collaboration involves making those requirements visible together, so that a proposed method can be examined as both an inquiry and an activity people would be asked to join.
That examination benefits from precise roles. A participant’s knowledge of local routines is not interchangeable with a laboratory result, just as a laboratory result cannot describe every aspect of a community’s daily life. Each contribution can be valuable without having to perform every other contribution’s job. A partnership should be able to explain the question to which a particular form of evidence is relevant. This makes disagreement easier to understand. People may be providing answers to different parts of a problem rather than competing to establish one person as the only expert who deserves to be heard.
Make the translation visible
Terms that feel ordinary within one field can need explanation elsewhere. A good conversation does not require removing every technical word. It requires giving the word enough context that another participant can understand the claim being made. Ask what was observed, how the observation was produced and what remains uncertain. When a word carries a different meaning in another discipline, name the difference. This can prevent a meeting from reaching a quick verbal agreement that conceals several incompatible understandings. The time spent clarifying a term may be more useful than moving on with a sentence nobody can use in the same way.
Written summaries can help if they preserve the distinction between an observation, an interpretation and a proposed action. In the imagined study, a repeated pattern might be an observation, an explanation for it an interpretation and a change in practice a proposal. Those stages can be connected without becoming identical. A public account that compresses them into one confident conclusion can make the work appear more settled than it is. An accurate summary should show which stage the project has reached and what further information or decision would be needed to move to another.
Listen for whose questions change the design. A partnership can contain many names while leaving the underlying plan untouched by some participants’ knowledge. The number of organizations involved does not establish how influence is distributed. A more revealing inquiry asks whether a concern raised by a participant led to a clearer question, a revised method or an explanation for keeping the original approach. This is an analytical way to examine collaboration, not an assessment of any named project. It focuses attention on how knowledge enters decisions rather than treating the presence of a partner’s name as sufficient evidence of shared work.
Return the result in a form people can use
The route back to participants belongs in the plan. Consider who will receive a result, what format would help them understand it and where they can raise a question. A technical publication can serve an important audience without meeting every participant’s information need. A short explanation may help, provided it preserves the result’s scope and uncertainty. In a hypothetical community project, an accessible summary and an opportunity to discuss it might complement the formal research record. The appropriate arrangement depends on the actual work and the agreements made with the people involved.
Public programs such as the Helsinki event can make these questions available beyond a specialist meeting. A listener can attend to how speakers describe a partnership and what evidence they use to explain its contribution. The published agenda offers topics to listen for, but it does not supply the discussion’s answers in advance. Keep a note of an unanswered question rather than filling the space with an assumed conclusion. If a recording or summary is later made available through an official channel, it can provide a route back to what was actually presented. Availability should be checked rather than promised.
Credit also deserves specificity. Name a partner’s role when that role is documented, and distinguish a collaboration’s stated aim from an outcome it has demonstrated. A project can be worthwhile while still developing a method or collecting information. Public communication should give that stage an accurate name. It helps readers understand what kind of progress is being reported and what remains to be done. The same care protects people whose contributions are easily reduced to a generic description of a community. Their knowledge can be acknowledged through the work it informed, where the evidence and permissions allow that account.
The November program places different kinds of expertise within a shared public conversation. Its broader invitation is to examine how collaboration becomes practical: define a question, identify what each contribution can establish and make the return of information part of the work. This does not make uncertainty disappear. It gives people a clearer way to work with it together. A partnership becomes easier to understand when its account can show what changed because the participants brought different knowledge. The shared question then remains a place where those differences can contribute, rather than a phrase that merely gathers them under one heading.
Image note: The photograph illustrates note-taking and does not depict the Helsinki speakers, a research project or a health consultation. Credit: Barbara Olsen / Pexels. Source photograph; Pexels license.
#upstormed #jonathananthonyburkett #jonathanburkett #OneHealth #OneHealthDay #ResearchCollaboration
