Assess whether to escalate a case to peer review (329197)

SITUATION Quality-improvement physician is responsible for to escalate a case to peer review in a unit, using a new early-warning model with unexpected mortality case series as the only working extract. A coder-clinician fight over a principal diagnosis is what reset the timeline for this Healthcare Outcomes Review file.

DECISION Quality-improvement physician in a unit with a new early-warning model must choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold using unexpected mortality case series after a coder-clinician fight over a principal diagnosis.

HYPOTHESES TO TEST 1. The population in unexpected mortality case series is the one a coder-clinician fight over a principal diagnosis named, so Proceed under protocol follows for this Outcomes Review file. 2. The population in unexpected mortality case series is adjacent only to a coder-clinician fight over a principal diagnosis; Pause the pathway is the honest Healthcare call. 3. A unit with a new early-warning model already contained a coder-clinician fight over a principal diagnosis before unexpected mortality case series arrived; no new Outcomes Review path. 4. Provenance on unexpected mortality case series after a coder-clinician fight over a principal diagnosis is broken; do not pick Proceed under protocol or Pause the pathway yet.

ANALYSIS REQUIRED 1. Assess patient-safety and HIPAA / minimum-necessary implications of to escalate a case to peer review. 2. Quantify who is harmed if unexpected mortality case series is wrong. 3. Separate a documented exception from an OCR-relevant gap in a unit with a new early-warning model. 4. For this Healthcare Outcomes Review file, read unexpected mortality case series against a coder-clinician fight over a principal diagnosis and write the one fact that would move to escalate a case to peer review for quality-improvement physician.

RECOMMENDATION Choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold on this Healthcare / Outcomes Review packet (unexpected mortality case series after a coder-clinician fight over a principal diagnosis). Lead with the Healthcare option unexpected mortality case series can support after a coder-clinician fight over a principal diagnosis, then the two facts that force it, then the Monday action for quality-improvement physician in a unit with a new early-warning model.

COMMAND RETURNS - Bottom-line Healthcare option on to escalate a case to peer review, then the evidence in unexpected mortality case series, then the action for quality-improvement physician - Hypothesis scorecard against unexpected mortality case series: supported / rejected / untestable - Outcomes Review finding in unexpected mortality case series that a second reviewer can re-perform - Missing page in unexpected mortality case series after a coder-clinician fight over a principal diagnosis, if any