Clinical AI Tool Deployed Without an Identified Payment Pathway — Pulled at Next Budget Cycle
Hospital acquires an AI clinical decision support tool from the innovation budget. After 18 months, the tool shows measurable workflow improvements but no direct revenue line, no CPT/HCPCS code, no NTAP, and no VBC contract crediting it for denial avoidance. At budget review, finance classifies it as discretionary overhead and cuts it. Clinicians who built workflows around the tool absorb the disruption.
Before deployment, classify the tool against the six payment pathways. If the only available pathway is 'bundled / no separate payment,' require the vendor to produce a ROI model tied to DRG mix, LOS reduction, denial avoidance, or shared-savings impact. Tie the tool's contract renewal to those metrics — not to clinician satisfaction alone.
This is an internal governance scenario, not a payer conversation. The 'appeal' is the business case presented at the next budget review: pathway classification, measured impact against the pathway's success metric, and the documented downstream consequence of removing the tool from the workflow.