The quality department asks inpatient coding to remove a clinically validated hospital-acquired condition code from several accounts so publicly reported rates improve. What should the coding professional do?
Select an answer to reveal the explanation.
Short Explanation
Quality scores do not get to erase real diagnoses. If the HAC code is clinically valid, it stays—even when the dashboard looks ugly. Escalate the ask; do not become the eraser.
Full Explanation
When quality at a civic hospital asks inpatient coding to remove clinically validated hospital-acquired condition codes so publicly reported rates improve, the coding professional must refuse and escalate through compliance channels. Public reporting only serves the community if the underlying abstracts remain truthful; deleting valid HAC codes is data falsification dressed as performance improvement. Removing the codes immediately with a quality override note in the encoder institutionalizes unethical undercoding. Replacing HAC diagnoses with symptom codes that quality software does not read hides the clinical event while pretending the abstract is complete. Agreeing only if finance likes the payment impact subordinates ethics to revenue optics. Exam caveat: quality dashboards never authorize omission of clinically valid, guideline-supported codes. Operational check: confirm clinical validation and guideline support, leave the codes in place, escalate the removal request to compliance/integrity leadership in writing, and educate stakeholders that rate improvement comes from care redesign, not abstract erasure. Sustain civic accountability by pairing correct code assignment with transparent denial, quality, and privacy escalation paths so public reporting and payment integrity move together.