Assess whether a mortality cluster is coding, case mix, or care (322f28)

Situation

Quality-measure abstraction disagreements arrived with a transfer that missed a stroke window for risk-model validation lead. That is a Healthcare Outcomes Review decision on a mortality cluster is in a 400-bed community hospital with alert fatigue.

Decision

Risk-model validation lead in a 400-bed community hospital with alert fatigue must choose A mortality cluster is coding, case mix, / Care using quality-measure abstraction disagreements after a transfer that missed a stroke window.

Hypotheses to test

• Quality-measure abstraction disagreements reads as A mortality cluster is coding, case mix, once a transfer that missed a stroke window is lined up to the same Healthcare population.
• Quality-measure abstraction disagreements is closer to Care after a transfer that missed a stroke window; A mortality cluster is coding, case mix, would over-claim this Outcomes Review extract.
• A dual reading is still live in quality-measure abstraction disagreements for risk-model validation lead in a 400-bed community hospital with alert fatigue.
• Quality-measure abstraction disagreements is missing the fact risk-model validation lead needs after a transfer that missed a stroke window; stop this Healthcare close.

Analysis required

• Trace access logs and outputs to the rule risk-model validation lead must apply.
• Assess patient-safety and HIPAA / minimum-necessary implications of a mortality cluster is.
• Quantify who is harmed if quality-measure abstraction disagreements is wrong.
• For this Healthcare Outcomes Review file, read quality-measure abstraction disagreements against a transfer that missed a stroke window and write the one fact that would move a mortality cluster is for risk-model validation lead.

Recommendation

Choose A mortality cluster is coding, case mix, / Care on this Healthcare / Outcomes Review packet (quality-measure abstraction disagreements after a transfer that missed a stroke window). The follow-on Outcomes Review action is what risk-model validation lead does next: implement the option, assign an owner, and log the missing fact.

Command returns