Hospital price transparency
Stale files past the update window
Standard charge information updates at least annually. Every repost is also a fresh statement: the file affirms its contents are true, accurate and complete as of the date in the file. A stale file is therefore two failures at once - a missed update cycle and an affirmation that no longer matches reality.
Staleness is visible from outside. The file carries its own date. Contracts renegotiate, chargemasters revise, and the payer mix shifts; a file dated fourteen months ago tells any reviewer that at least one annual cycle has been missed. No complaint is needed for CMS monitoring to flag it.
The refresh triggers are predictable: the annual cycle, plus any renegotiation or system change that makes the encoded charges wrong. The attestation adds one more - a change in the named attester, whose name sits inside the file.
The fix is boring and that is the point: a dated owner, a calendared republication, and a rule that no repost goes up without the file being regenerated and re-checked, including the affirmation.