Assess whether documentation queries are driving coding or care (d1b783)

SITUATION After a CMS preview report showing a star-rating drop, unit-level complication variation table is what mortality-and-morbidity reviewer can touch in a rural hospital with long transfer times. Healthcare will live with Documentation queries are driving coding versus Care on this Outcomes Review file.

DECISION Mortality-and-morbidity reviewer in a rural hospital with long transfer times must choose Documentation queries are driving coding / Care using unit-level complication variation table after a CMS preview report showing a star-rating drop.

HYPOTHESES TO TEST 1. A CMS preview report showing a star-rating drop is noise around an already-controlled Outcomes Review process in a rural hospital with long transfer times, given unit-level complication variation table. 2. A CMS preview report showing a star-rating drop is the event in unit-level complication variation table that forces Documentation queries are driving coding for mortality-and-morbidity reviewer under Healthcare. 3. Unit-level complication variation table shows a one-file miss after a CMS preview report showing a star-rating drop, not a Outcomes Review program failure. 4. Unit-level complication variation table cannot decide documentation queries are driving yet after a CMS preview report showing a star-rating drop; hold is the only Healthcare close a rural hospital with long transfer times can defend.

ANALYSIS REQUIRED 1. Separate a documented exception from an OCR-relevant gap in a rural hospital with long transfer times. 2. Validate clinical-outcome evidence and protocol steps in unit-level complication variation table after a CMS preview report showing a star-rating drop. 3. Trace access logs and outputs to the rule mortality-and-morbidity reviewer must apply. 4. For this Healthcare Outcomes Review file, read unit-level complication variation table against a CMS preview report showing a star-rating drop and write the one fact that would move documentation queries are driving for mortality-and-morbidity reviewer.

RECOMMENDATION Choose Documentation queries are driving coding / Care on this Healthcare / Outcomes Review packet (unit-level complication variation table after a CMS preview report showing a star-rating drop). If unit-level complication variation table cannot force a Healthcare label under Outcomes Review, stop. If unit-level complication variation table after a CMS preview report showing a star-rating drop cannot support Documentation queries are driving coding versus Care on this Healthcare Outcomes Review close, mortality-and-morbidity reviewer must state the unresolved clinical or safety evidence requirement explicitly.

COMMAND RETURNS - Bottom-line Healthcare option on documentation queries are driving, then the evidence in unit-level complication variation table, then the action for mortality-and-morbidity reviewer - Hypothesis scorecard against unit-level complication variation table: supported / rejected / untestable - Outcomes Review finding in unit-level complication variation table that a second reviewer can re-perform - Missing page in unit-level complication variation table after a CMS preview report showing a star-rating drop, if any