Assess whether documentation queries are driving coding or care (1d968a)

SITUATION Unit-level complication variation table arrived with a transfer that missed a stroke window. Clinical documentation integrity manager in a health system after a CMS quality-reporting miss still has an evidence gap on whether documentation queries are driving coding or care.

DECISION Clinical documentation integrity manager in a health system after a CMS quality-reporting miss must choose Documentation queries are driving coding / Care using unit-level complication variation table after a transfer that missed a stroke window.

HYPOTHESES TO TEST 1. Unit-level complication variation table reads as Documentation queries are driving coding once a transfer that missed a stroke window is maps to the same Healthcare population. 2. Unit-level complication variation table is closer to Care after a transfer that missed a stroke window; Documentation queries are driving coding would over-claim this Pediatric Protocols extract. 3. A dual reading is still live in unit-level complication variation table for clinical documentation integrity manager in a health system after a CMS quality-reporting miss. 4. Unit-level complication variation table is missing the fact clinical documentation integrity manager needs after a transfer that missed a stroke window; stop this Healthcare close.

ANALYSIS REQUIRED 1. Assess patient-safety and HIPAA / minimum-necessary implications of documentation queries are driving. 2. Quantify who is harmed if unit-level complication variation table is wrong. 3. Separate a documented exception from an OCR-relevant gap in a health system after a CMS quality-reporting miss. 4. For this Healthcare Pediatric Protocols file, read unit-level complication variation table against a transfer that missed a stroke window and write the one fact that would move documentation queries are driving for clinical documentation integrity manager.

RECOMMENDATION Choose Documentation queries are driving coding / Care on this Healthcare / Pediatric Protocols packet (unit-level complication variation table after a transfer that missed a stroke window). The follow-on Pediatric Protocols action is what clinical documentation integrity manager does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Healthcare option on documentation queries are driving, then the evidence in unit-level complication variation table, then the action for clinical documentation integrity manager - Hypothesis scorecard against unit-level complication variation table: supported / rejected / untestable - Regulatory or exam hook Pediatric Protocols would cite - Pediatric Protocols finding in unit-level complication variation table that a second reviewer can re-perform