|
The part of the portfolio many programs miss |
|
Copay programs are built around pharmacy claims, because that’s where the volume lives. Applied to a medical or dual benefit product without adjustment, that same infrastructure creates a gap, not because the vendor did anything wrong, but because the claim type is different.
|
|
Claims Routing One path becomes several Pharmacy claims flow through a single, standardized retail or specialty pharmacy path. Medical claims split across physician offices, infusion centers, and hospital outpatient departments, each billing differently. |
Closing This Gap Requires: Documentation requirements mapped by site of care before the first claim goes out, not pieced together after a denial reveals the gap. |
|
|
Benefit Investigation Automated lookup becomes manual verification Pharmacy benefit investigation is largely an automated eligibility check. Medical benefit investigation often requires manual verification with payer and plan-specific documentation before a claim can even be filed correctly. |
Closing This Gap Requires: A benefit investigation process built for manual, payer-specific verification as the default, not an automated pharmacy check with medical bolted on. |
|
|
Reimbursement Timing Point of sale becomes after the fact Pharmacy adjudicates at the counter, so a cost problem is visible immediately. Medical adjudicates through claims processing after treatment, so an affordability gap can surface weeks later, well after the patient experience is already set. |
|
|
|
PA and Appeals Formulary logic becomes medical policy Medical payer criteria differ from the pharmacy formulary and PA logic most programs are tuned for. A program built around pharmacy PA patterns tends to misread medical denials rather than resolve them. |