Assess whether to stop a model that increases alert volume without outcomes

SITUATION A multi-hospital system comparing length of stay cannot treat a coder-clinician fight over a principal diagnosis as incidental context on unit-level complication variation table. Clinical documentation integrity manager must close to stop a model from that extract under Healthcare / Models and Documentation.

DECISION Clinical documentation integrity manager in a multi-hospital system comparing length of stay must choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold using unit-level complication variation table after a coder-clinician fight over a principal diagnosis.

HYPOTHESES TO TEST 1. A coder-clinician fight over a principal diagnosis is noise around an already-controlled Models and Documentation process in a multi-hospital system comparing length of stay, given unit-level complication variation table. 2. A coder-clinician fight over a principal diagnosis is the event in unit-level complication variation table that forces Proceed under protocol for clinical documentation integrity manager under Healthcare. 3. Unit-level complication variation table shows a one-file miss after a coder-clinician fight over a principal diagnosis, not a Models and Documentation program failure. 4. Unit-level complication variation table cannot decide to stop a model yet after a coder-clinician fight over a principal diagnosis; hold is the only Healthcare close a multi-hospital system comparing length of stay can defend.

ANALYSIS REQUIRED 1. Trace access logs and outputs to the rule clinical documentation integrity manager must apply. 2. Assess patient-safety and HIPAA / minimum-necessary implications of to stop a model. 3. Quantify who is harmed if unit-level complication variation table is wrong. 4. For this Healthcare Models and Documentation file, read unit-level complication variation table against a coder-clinician fight over a principal diagnosis and write the one fact that would move to stop a model for clinical documentation integrity manager.

RECOMMENDATION Choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold on this Healthcare / Models and Documentation packet (unit-level complication variation table after a coder-clinician fight over a principal diagnosis). The follow-on Models and Documentation 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 to stop a model, 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 - Named option among Proceed under protocol, Pause the pathway, Escalate safety review and the fact that kills the others - Owner and next date for clinical documentation integrity manager in a multi-hospital system comparing length of stay