What Coverage Questions Usually Mean
MedPay is a first-party benefit—meaning it is tied to the injured person’s own auto policy (or a policy they qualify under), not the other driver’s fault. A liability claim is different: it is made against the at-fault driver’s insurance and generally requires proving fault. When a carrier says “no MedPay is listed,” they are saying the policy does not include that optional first-party medical-bill benefit.
Common Potential Sources of Payment (High-Level)
- At-fault driver’s liability coverage: This is the usual path for recovering injury-related losses when another driver caused the crash.
- Uninsured motorist (UM) / underinsured motorist (UIM): In North Carolina, UM coverage is required on most personal auto policies, and UIM is required in many situations depending on the liability limits purchased. These coverages can apply when the at-fault driver has no coverage, leaves the scene, or does not have enough coverage. North Carolina’s UM/UIM framework is set out in N.C. Gen. Stat. § 20-279.21.
- Medical payments coverage (MedPay): If it is not listed, it is generally not available under that policy for this claim.
- Health insurance: Often used to keep treatment moving while the injury claim is investigated and negotiated (coordination and reimbursement issues can come up later, depending on the payer).
Information to Gather
- Declarations page(s): The dec page is usually the quickest way to confirm whether MedPay exists and, if it does, the limit and who is covered.
- Named insured and household info (generic): Coverage can depend on whether the injured person qualifies as an “insured” under the policy (for example, as the named insured, a resident relative, or an occupant).
- Crash basics (generic): Date, vehicles involved, and whether the injured person was a driver, passenger, or pedestrian—because that can affect which policy applies.
- What other coverages are listed: UM/UIM, collision, rental, and any endorsements that might change how benefits apply.
Common Coverage Disputes and Practical Next Steps
- “No MedPay” vs. “MedPay exhausted”: These are different. “No MedPay” means the coverage was not purchased (or is not on that policy). “Exhausted” means it existed but has been used up.
- Wrong policy or wrong vehicle: Sometimes the carrier reviewed a policy connected to the household, but a different policy (or a different vehicle’s policy) may be the one that applies.
- UM/UIM still matters even without MedPay: MedPay is about paying medical bills early without proving fault. UM/UIM is about compensating for damages caused by an uninsured or underinsured driver, and it has its own rules and procedures under North Carolina law.
- Document the confirmation: If a carrier confirms “no MedPay,” it helps to get that confirmation in writing (or preserve the email/letter) and keep a copy of the dec page in the claim file.
How This Applies
Apply to the facts: Here, the carrier reviewed the auto policy connected to the injury claim and advised there is no MedPay listed. In practical terms, that usually means the firm should not expect a separate MedPay payment stream from that policy for medical bills, and should instead focus on confirming other available coverages (especially UM/UIM) and pursuing the injury claim through the appropriate liability and/or UM/UIM channels based on the crash facts.
What the Statutes Say (Optional)
- N.C. Gen. Stat. § 20-279.21 (UM/UIM requirements) – explains key required/available motor vehicle coverages in North Carolina, including uninsured and underinsured motorist coverage rules.
Conclusion
If your auto policy does not include MedPay, it generally means there is no built-in, no-fault medical-bill benefit under that policy for this crash. That does not end the injury claim, but it can change how medical bills get paid while the case is pending and where recovery may come from (liability coverage and/or UM/UIM). A practical next step is to obtain the declarations page and confirm, in writing, what coverages are available and who qualifies as an insured.
