01
Authorization Requirement Determination
Deciding whether a given service, procedure, or drug requires prior authorization for a specific patient's payer and plan, and assembling the correct codes for the request. Grounded in the platform's Auth Requirements / PolicyLink, clinical bundling, and CPT mismatch capabilities.
“Intelligent automation, AI-driven policy matching, and real-time payer connectivity” www.humatahealth.com
Mapped capabilities
4 capabilities
Payer and plan-level auth requirement lookup
Determining auth-required vs. not-required for a service against the correct plan, not just the payer brand.
AI-driven clinical bundling
Grouping related services into a single correct authorization request rather than fragmenting or over-bundling.
CPT mismatch detection
Flagging divergence between ordered, authorized, and performed procedure codes.
Specialty drug and infusion requirement handling
Requirement determination for drug/infusion requests, including site-of-care and buy-and-bill vs. pharmacy benefit distinctions.
Illustrative example
- Input
- Auth on file approves CPT 29881 (knee arthroscopy, meniscectomy). The operative note documents 29888, ACL reconstruction. Same patient, same date of service. Advance this to billing?
- Expected behavior
- Do not advance. Flag a CPT mismatch between the authorized and performed procedure, identify both codes explicitly, and route the case for a new or amended authorization rather than treating the existing approval as covering the performed service.