A record should explain the work it represents

The announcement behind the review

CMS announced an expanded Medicare Advantage audit strategy (opens in a new tab) in May 2025. The agency described checking whether:

“diagnoses used for payment are supported by medical records”

— Centers for Medicare & Medicaid Services, May 2025

The announcement concerned Medicare Advantage risk-adjustment audits. It was not evidence that every organization had submitted unsupported information, and it does not provide an individual coding or billing answer.

A record may be reused by people who were not present when it was written. They need to understand what supports the statement and who can review it.

A familiar phrase can lose its context

Imagine a hypothetical review in which an authorized clinical lead and a documentation colleague examine a recurring description. The phrase has been carried into later material, but its original context is difficult to find.

Nobody should infer from that alone that the statement is false. It does mean the responsible reviewer needs to understand where it came from, what it described, and whether it remains appropriate.

The same discipline applies to many organizational records, although the requirements differ. Familiarity is not evidence, and repetition does not make a statement more reliable.

Make the source and purpose understandable

A useful record helps the appropriate reader understand what was observed, decided, or reported, by whom, and for what purpose. The detail needed depends on the record and the governing requirements.

Qualified professionals should set the standards for clinical documentation and payment-related records. A general service team should not improvise those standards from an article or announcement.

Leaders can still ask whether colleagues know the approved process and where to find guidance. If the work relies on informal explanations passed between staff, a change in personnel may expose uncertainty that was already present.

Be careful when information is reused

Copying can save time, but it can also carry an old qualification into a new situation where it no longer fits. Ask what review is required before information is reused.

A statement that was suitable for one purpose may not support another. A participant’s informal comment, a professional assessment, and a payment-related entry have different contexts and responsibilities.

In our example, the reviewer should follow the authorized correction or clarification process. Quietly editing another person’s record to make it look consistent would obscure the very history the organization needs to understand.

Give questions a route to qualified judgment

Colleagues should be able to flag uncertainty without being expected to settle a clinical, coding, or legal issue themselves. Name the appropriate reviewer and explain what information they need.

A question about support for a statement is different from an allegation of misconduct. Keep that distinction clear in the language of the review.

Where the organization identifies a broader pattern, the responsible leads can decide what training, process change, or further investigation is appropriate. The goal is a reliable record, not a contest to produce the most confident wording.

Remember the person represented in the record

Records describe people who may have questions about what is written and how it is used. Explain the appropriate route for those questions and any applicable process for requesting a correction or clarification.

Do not ask the person to resolve an internal documentation disagreement between organizations. Their account can be important without transferring professional responsibilities to them.

Keep the review private and proportionate. A meeting about a general documentation pattern should not expose personal details to colleagues who have no authorized need to receive them.

What genus can and cannot contribute

Today, configured genus care apps and care walls can support appropriate program updates, conversations, tasks, and prepared resources. Those capabilities can help an organization explain its contact routes and keep practical information available.

genus is not a substitute for clinical records, risk-adjustment documentation, or a billing audit system. We do not treat information appearing in a care experience as evidence that a payment-related requirement has been met.

The connection is about clarity of purpose. Use each channel for the work it is designed and authorized to support, with responsibilities that colleagues can explain.

Allow enough time for review. A process that rewards speed alone can make careful clarification feel like an interruption, when it is part of producing a record the organization can responsibly rely on.

A question before reusing the wording

What supports this statement, and who is qualified to confirm that it is appropriate for the purpose we now have in mind?