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

SITUATION A transfer that missed a stroke window put documentation-query response lag in front of clinical documentation integrity manager in a multi-hospital system comparing length of stay. This Healthcare / Models and Documentation close is documentation queries are driving from documentation-query response lag, and the live options are Documentation queries are driving coding, Care.

DECISION Clinical documentation integrity manager in a multi-hospital system comparing length of stay must choose Documentation queries are driving coding / Care using documentation-query response lag after a transfer that missed a stroke window.

HYPOTHESES TO TEST 1. Documentation-query response lag reads as Documentation queries are driving coding once a transfer that missed a stroke window is maps to the same Healthcare population. 2. Documentation-query response lag is closer to Care after a transfer that missed a stroke window; Documentation queries are driving coding would over-claim this Models and Documentation extract. 3. A dual reading is still live in documentation-query response lag for clinical documentation integrity manager in a multi-hospital system comparing length of stay. 4. Documentation-query response lag is missing the fact clinical documentation integrity manager needs after a transfer that missed a stroke window; stop this Healthcare close.

ANALYSIS REQUIRED 1. Quantify who is harmed if documentation-query response lag is wrong. 2. Separate a documented exception from an OCR-relevant gap in a multi-hospital system comparing length of stay. 3. Validate clinical-outcome evidence and protocol steps in documentation-query response lag after a transfer that missed a stroke window. 4. For this Healthcare Models and Documentation file, read documentation-query response lag 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 / Models and Documentation packet (documentation-query response lag after a transfer that missed a stroke window). Lead with the Healthcare option documentation-query response lag can support after a transfer that missed a stroke window, then the two facts that force it, then the Monday action for clinical documentation integrity manager in a multi-hospital system comparing length of stay.

COMMAND RETURNS - Bottom-line Healthcare option on documentation queries are driving, then the evidence in documentation-query response lag, then the action for clinical documentation integrity manager - Hypothesis scorecard against documentation-query response lag: supported / rejected / untestable - Owner and next date for clinical documentation integrity manager in a multi-hospital system comparing length of stay - What changes documentation queries are driving if a transfer that missed a stroke window is later withdrawn