The person can disagree with the summary

What we found in the news

A November 2023 study in the Journal of Medical Internet Research (opens in a new tab) examined reported errors, omissions, and offensive content in online health records among people receiving mental health care in Sweden. The authors argued that:

“patients can and should act as collaborators”

— Annika Bärkås and colleagues

The survey concerned people’s reported experiences, rather than an independent audit of every disputed record. It was not a study of AI summaries. Its relevance here is the person’s contribution to accuracy when an account of their life is written by someone else.

Why this matters to us

A summary can look finished while leaving something important unsettled. The person described may recognize a detail that the writer could not know.

Imagine a community participant asking to attend a morning session next week because of a temporary transport arrangement. A later summary says they prefer morning activities.

That small change turns a particular request into an ongoing preference. If the summary shapes future invitations, it could keep doing so long after the transport arrangement has ended.

Whether a colleague wrote the sentence or an assistant helped draft it, the practical question is the same: can the person see the relevant account, point out the difference, and find out what happens next?

Make the correction easy to start

A person should not have to understand the system’s internal workflow to raise a concern. Offer a clear route through an appropriate colleague, accessible form, or other agreed channel.

In our example, the participant marks the sentence on a printed summary. The staff member can ask what they would like clarified and check the context of the original request.

Make room for different kinds of concern. A date may be wrong, a description may omit important context, or the person may disagree with how an experience has been characterized. Those issues need attention, even when the response to each is different.

Explain who will review the concern and how the person will hear back. Avoid leaving a marked-up page in a pile with no one responsible for the next step.

Preserve the difference that matters

The revised account might say that morning attendance was requested for a particular week. The team can then confirm the person’s broader preferences separately.

That is more useful than replacing one broad assumption with another. Someone correcting a sentence does not necessarily want every related record rewritten in the same way.

Check where the disputed detail has already been used. If it helped prepare next month’s invitation list, the person reviewing that list may need the relevant correction too, through the organization’s appropriate process.

Handle changes according to the record’s purpose and requirements. Some information needs an amendment with an explanation or review history. A quick edit should not make it harder to understand what changed and why.

Close the loop in words the person can use

After review, tell the person what was changed, what remains under consideration, and what could not be changed. Give a clear reason where a different view remains.

For the participant in our example, a brief explanation and the amended passage may be enough. They can check that the temporary request is now understood and add anything still missing.

Use these moments to improve the drafting process. If staff repeatedly turn short-term arrangements into lasting preferences, the template or guidance may need a more specific prompt.

Keep the response respectful. A person correcting an account is helping the service understand them more accurately. They should not need exceptional persistence to make that contribution count.

What this means for the people you serve

Being described in a record should leave room for being heard. People can contribute context, question an interpretation, and ask how a correction affects future support. An understandable response matters even when the organization cannot resolve every disagreement immediately.

The genus connection

Today, genus partner-portal workflows can support staff observations and reviewed summaries within configured roles and access arrangements. Staff review remains part of preparing an account for its intended audience.

A service using those workflows should agree how participants and families can raise corrections, who reviews them, and how relevant changes reach subsequent work. The technology can help organize the account; the team needs a clear practice for listening when someone says it is incomplete.

One question to take away

If a person spots one sentence that changes the meaning of their experience, how will they get it reviewed?