Agree what a shared record means on both sides

What we found in the news

In July 2026, WHO and the International Telecommunication Union opened a consultation (opens in a new tab) on draft guidance for national digital health infrastructure. The announcement describes infrastructure:

“aligned with priority health sector goals”

The document was a draft for review, not a final standard or a certification of any product. Its national scope is much larger than a local service partnership. It nevertheless offers a useful starting point for a smaller question: what useful work should a connection between two organizations make possible?

Why this matters to us

Moving a record is one part of sharing information. Understanding it is another. One team may use a status to mean that it has sent a request. Another may read the same word as confirmation that the request has been accepted.

A connection can work technically while leaving people with different expectations. We are interested in the agreements that make shared information useful: what it means, who maintains it and what someone should do next. Those details deserve attention before a busy team has to interpret them in a hurry.

Compare one ordinary example

Imagine a community coordinator and a partner service colleague reviewing a sample referral together. A participant is helping them check how the process will be explained. The card names a destination and an interest in a weekly group.

The two colleagues discover that their systems use the same status label for different stages. One means ready for review; the other means a place has been offered. The participant wants a simpler answer: whether they should make arrangements to attend.

Start with an invented example that contains no personal information. Walk it through both organizations. Ask each person what the record tells them and what action they would take. Differences are easier to resolve while they are still examples.

Agree the meaning of the important fields

Choose the information that supports the actual handoff. A preferred contact method, the date of a request and the source of a stated preference may matter more than a long collection of background fields.

Write down what key terms mean. Distinguish a request from an offer, an observation from a person's own statement, and a current preference from an older entry. Agree how a change or withdrawal should appear on the receiving side.

Include permission and responsibility in that discussion. Which information is appropriate to share for this purpose? Who can update it? Who answers when the record is unclear? A technical field mapping becomes useful when it reflects these everyday working agreements.

Check what happens when details change

The first successful transfer is a beginning. A participant may choose another contact method, an activity may move or a partner may change its intake process. The connection needs a way to handle those ordinary changes.

Confirm which organization owns each detail and how the other team learns that it has changed. Test the handling of an incomplete record as well as a perfect one. Make sure staff can recognize information that needs clarification.

Set a practical review point with the partner. Bring examples of confusion and decide what to adjust. Keep the participant's explanation of the process in view: it should remain understandable even when the underlying systems are complicated.

What this means for the people you serve

People can receive a clearer account of where a request stands and whom to contact. Families and staff spend less effort translating between organizational terms. The intended benefit is a shared understanding that supports the next conversation, rather than an assumption that sending data has completed the work.

The genus connection

The current devices and integrations (opens in a new tab) approach makes the scope of a connection something to confirm: the systems involved, information flow, permissions and operating responsibilities. The partner portal (opens in a new tab) provides configured staff workflows around the organization's work.

A genus integration discussion can use a sample journey to make those choices concrete. Agree the meaning and ownership of the information alongside the technical connection. Then check that the receiving team and the person involved understand the same next step.

One question to take away

Which shared status or field could mean something different to the organization receiving it?