Invite a correction before drawing a conclusion
A recipient brief asks which interpretation is wrong, which question matters most and who else should see it. The same facility brief can support several role perspectives; the accompanying message can ask whether the topic overlaps with the recipient’s work. A correction should retain its source, date and reviewed disposition. Feedback improves the next reviewed version; it does not imply automatic model training or an unreviewed change to the public record.
If a facility believes a displayed affiliation, measure context or calculation is wrong, it needs to know what evidence was used and what happens after the issue is raised. A silent correction—or no correction path at all—weakens trust.
Public intelligence is not trustworthy because it never receives a challenge. It is trustworthy when a challenge can be captured with context, reviewed against source evidence and resolved without silently rewriting history.
That is why Report data issue belongs across the Lime Health Evidence Journey rather than on one administrative page. A discrepancy may appear in a facility identity, affiliation, program classification, payment context, comparison, timeline or explanatory article. The action must be easy to find without dominating the screen.
Context reduces correction burden
For a correction to a public brief or website page, email contact@limehealth.co. Include the facility name or CCN, the page or brief edition, the value or wording in question, and a public source if available. Please do not include patient information or private operational records.
Prasada at Lime Health will reply. An email starts a review; it does not automatically update CMS data or a published brief. We may ask for clarification, explain the calculation or prepare a corrected copy after checking the source.
A receipt is not an approval
Sending a correction is different from having it accepted. A reviewer needs the original source, its reporting period, the proposed correction and the reason for the change. A corrected copy should identify its edition so readers can distinguish it from the earlier version.
Reference intake and receipt controls help explain the intended audit trail. They are not a promise that this public email route creates an automated case, issues a service receipt or resolves a report within a fixed time. Corrections remain human reviewed.
Correction improves the product loop
Corrections are also product evidence. Repeated issues may reveal a brittle source mapping, confusing terminology or a missing business rule. Those patterns can become governed improvement candidates without turning every user report into automatic truth.
The trust signal is therefore not an exclamation mark or a promise of instant repair. It is a low-friction route into a controlled process whose limits are visible.