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

SITUATION After a transfer that missed a stroke window, transfer-delay file for time-sensitive diagnoses is what mortality-and-morbidity reviewer can touch in a rural hospital with long transfer times. Healthcare will live with Documentation queries are driving coding versus Care on this Outcomes Review file.

DECISION Mortality-and-morbidity reviewer in a rural hospital with long transfer times must choose Documentation queries are driving coding / Care using transfer-delay file for time-sensitive diagnoses after a transfer that missed a stroke window.

HYPOTHESES TO TEST 1. Authorize Documentation queries are driving coding now; transfer-delay file for time-sensitive diagnoses already has the discriminator after a transfer that missed a stroke window. 2. Keep Care in force until transfer-delay file for time-sensitive diagnoses is completed after a transfer that missed a stroke window for mortality-and-morbidity reviewer. 3. Treat transfer-delay file for time-sensitive diagnoses as Documentation queries are driving coding because both readings appear after a transfer that missed a stroke window. 4. Refuse a Healthcare close: mortality-and-morbidity reviewer does not have the decision documentation queries are driving turns on in transfer-delay file for time-sensitive diagnoses.

ANALYSIS REQUIRED 1. Separate a documented exception from an OCR-relevant gap in a rural hospital with long transfer times. 2. Validate clinical-outcome evidence and protocol steps in transfer-delay file for time-sensitive diagnoses after a transfer that missed a stroke window. 3. Trace access logs and outputs to the rule mortality-and-morbidity reviewer must apply. 4. For this Healthcare Outcomes Review file, read transfer-delay file for time-sensitive diagnoses against a transfer that missed a stroke window and write the one fact that would move documentation queries are driving for mortality-and-morbidity reviewer.

RECOMMENDATION Choose Documentation queries are driving coding / Care on this Healthcare / Outcomes Review packet (transfer-delay file for time-sensitive diagnoses after a transfer that missed a stroke window). The follow-on Outcomes Review action is what mortality-and-morbidity reviewer 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 transfer-delay file for time-sensitive diagnoses, then the action for mortality-and-morbidity reviewer - Hypothesis scorecard against transfer-delay file for time-sensitive diagnoses: supported / rejected / untestable - Owner and next date for mortality-and-morbidity reviewer in a rural hospital with long transfer times - What changes documentation queries are driving if a transfer that missed a stroke window is later withdrawn