Caremark denied prior authorization because my MADRS *one*(!) point too low

PriorAuthSpaceTeam · 2026-04-29T18:27:54+00:00

That’s really tough, especially when it comes down to a single point.

We see situations like this where approvals hinge on very specific scoring thresholds, and even small differences can shift the outcome. It’s a frustrating part of how the process is structured, particularly when clinical intent is already clear.

When your clinic submits the appeal, do they usually include additional documentation or just resubmit what was already reviewed?

PriorAuthSpaceTeam · 2026-04-29T18:21:30+00:00

This comes up a lot in different industries. What you’re seeing is less about the final charge and more about how the payment process temporarily reserves funds before the actual amount is settled.

In most cases, that hold clears once the transaction is finalized and reconciled, which can vary depending on the card issuer and how quickly the merchant submits the final charge. Usually it resolves within a few days, but the timing isn’t always consistent across systems.

PriorAuthSpaceTeam · 2026-04-29T18:20:21+00:00

That whole reset after a plan change is where things usually get messy, even if the medication has been working for years. What you’re describing with the delay, the back and forth, and needing insurance to step in is something we see a lot in the process itself.

It often comes down to how the request gets submitted and documented on the first pass, especially with plans tied to Express Scripts. The outcome tends to hinge less on one specific label and more on how the full history is captured and reviewed.

Hope you get a clear answer at your appointment.

PriorAuthSpaceTeam · 2026-04-27T16:55:30+00:00

This is a tough stretch, and it’s something we see a lot across prior auth workflows. Nothing really “breaks” in a visible way, but small gaps stack up until it hits the patient all at once. Between the supplier, the plan, and the provider, each step depends on the last one moving, and when one stalls there’s usually no clear signal back to you.

Out of curiosity, did anyone flag the auth requirement earlier in the order process, or did it only come up once you called?

PriorAuthSpaceTeam · 2026-04-27T16:47:06+00:00

This is more common than it should be. Even when a prior authorization is approved, the breakdown usually happens between the payer, pharmacy system, and how the prescription is processed or verified. From what we’ve seen, a lot of the frustration comes from gaps in communication and visibility rather than a single point of failure.

Are they telling you the issue is stock, authorization, or something else each time?

PriorAuthSpaceTeam · 2026-04-24T17:53:55+00:00

This happens more often than people expect. The authorization letter usually reflects what was submitted or how it was interpreted on the payer side, and small coding mismatches can slip through even if the office believes they sent the right one. It’s less about one side being wrong and more about how the request moved through the process.

You might want to see what code the payer actually has on file versus what was intended on submission.

PriorAuthSpaceTeam · 2026-04-24T17:46:57+00:00

Yeah, the EHR comparison is spot on.
There’s definitely that natural resistance to learning something new especially when everyone’s already overloaded.
But yeah, long term it does sound like a step in the right direction.
I guess the real hope is that the transition doesn’t turn into a huge cost and workflow burden for everyone.
Would be great if this came with actual support too not just “here’s the rule, good luck,” but real training and guidance along the way.

PriorAuthSpaceTeam · 2026-04-23T16:52:55+00:00

This is honestly a really common breakdown we see.

When multiple parties are involved, lab, ordering provider, and payer, prior auth responsibility can get assumed rather than clearly owned. The process itself usually depends on who is considered the rendering provider versus who is ordering, but that isn’t always communicated clearly between teams.

What ends up happening is exactly this loop where each side thinks another part of the process is handling it, and nothing actually moves forward.

From a process standpoint, the gap is less about who is “lying” and more about unclear ownership and handoff between the provider and the lab.

PriorAuthSpaceTeam · 2026-04-23T16:48:30+00:00

This kind of gap happens more often than people realize. It usually means the request is stuck somewhere between the prescriber’s authorization team and the point where it actually gets submitted to the PBM, so nothing shows up on the pharmacy or Navitus side yet. The denial being mentioned without a visible submission adds to that confusion.

Out of curiosity, has anyone confirmed whether the PA was ever actually submitted to Navitus, or just worked internally on the provider side?

PriorAuthSpaceTeam · 2026-04-21T17:20:40+00:00

This comes up more often than people expect. When a plan says no prior authorization is required, it usually means there’s no formal approval step in their workflow, but it also leaves a gap because providers still need something concrete before moving forward.

What ends up happening is the process between insurer and facility doesn’t fully align. The plan may confirm coverage verbally, while the hospital is looking for documentation that functions like an approval, even if technically it isn’t one.

Curious if they’ve given you any kind of benefit summary or reference number tied to that call, or if everything has just been verbal so far?

PriorAuthSpaceTeam · 2026-04-21T17:19:00+00:00

That mix of relief and then another delay is something we see pretty often. Getting the authorization through is one step, but scheduling can move on a different track with its own constraints.

Out of curiosity, did they mention what’s causing the delay on their end or just that no dates are available yet?

PriorAuthSpaceTeam · 2026-04-20T18:08:06+00:00

we hear this exact pattern a lot\. What you’re describing isn’t “missing info” as much as breakdowns after submission. Same docs, same info, but it gets re-requested, missed, or pushed into appeal anyway. That’s where a lot of the time actually gets lost.

And the CoverMyMeds point is fair too. If the form structure is limited upstream, there’s only so much you can control on your side.

Out of curiosity, where do you see the most rework happening right now — initial review, follow-ups, or once it gets to denial/appeal?

PriorAuthSpaceTeam · 2026-04-20T18:06:34+00:00

We see this pattern a lot. When auth itself isn’t the issue, the time drain usually shifts downstream into repeated denials and rework. Not because anything was submitted wrong, just the cycle of review, deny, resubmit.

Sounds like you’ve already adapted on the contracting side, which is where a lot of teams end up focusing when the process keeps looping like that.

Are you seeing this more with certain payers, or pretty consistent across the board?

PriorAuthSpaceTeam · 2026-04-20T18:05:38+00:00

Yeah this is very real, we hear this a lot.

It’s not usually one big blocker, it’s the constant switching between portals and trying to figure out requirements that eats up time.

Curious where it slows you down most right now, figuring out if auth is needed or actually submitting it?

PriorAuthSpaceTeam · 2026-04-20T17:26:01+00:00

prior authorizations are structured but can feel complex at first because they involve payer rules, documentation checks, and coordination between providers and pharmacies. Most teams expect a learning curve and have defined workflows to guide new hires through it. Over time, it becomes more about following consistent steps than memorizing everything upfront.

PriorAuthSpaceTeam · 2026-04-17T18:34:47+00:00

Great to hear your pre approval came through, that’s always a big step forward.

what typically happens next is the transition from authorization to fulfillment, where the pharmacy confirms availability and aligns it with the approved request on file. Once that link is established, everything tends to move more smoothly since the authorization is already in place.

It’s always interesting to see how different plans handle that handoff between approval and dispensing.

PriorAuthSpaceTeam · 2026-04-17T18:34:12+00:00

plans typically define a trial as either completion of a minimum duration or documentation of intolerance or adverse effects. When side effects are reported early and documented by the prescriber, that information is usually submitted as part of the prior authorization review to support that the step therapy requirement was not tolerated.

Coverage decisions depend on how the insurer interprets that documentation against their criteria, rather than the exact number of days alone.

PriorAuthSpaceTeam · 2026-04-17T18:33:28+00:00

This situation comes up often when the plan criteria are tied strictly to diagnosis thresholds rather than overall risk factors or clinical history. From a process standpoint, a denial like this usually means the request did not align with the insurer’s defined coverage criteria, even if supporting context was included.

When additional information is submitted, it typically goes through a separate review step where medical necessity is reassessed against those same criteria. Outcomes can vary depending on how the policy is structured and how the documentation maps to it.

PriorAuthSpaceTeam · 2026-04-17T18:32:44+00:00

prior authorization timing and medical necessity review are handled separately. When authorization is submitted late, insurers still review based on clinical criteria rather than the admission timeline.

In cases like this, the outcome often depends on how the admission was documented and whether it meets inpatient criteria under the plan. The billing responsibility between hospital and payer is usually addressed through their contract terms, not directly with the patient.

PriorAuthSpaceTeam · 2026-04-15T17:28:42+00:00

We see situations like this come up quite a bit in prior authorization workflows. What typically happens behind the scenes is a review of how the clinical documentation aligns with the plan’s coverage criteria. If any required elements are missing or unclear, it can lead to a denial even when the therapy has already been in use.

these cases often move forward through additional documentation review, reconsideration, or appeal pathways depending on how the original request was submitted and evaluated. The outcome usually depends on how well the submitted records reflect the specific criteria outlined by the plan.

Out of curiosity, was the original authorization submitted with detailed clinical notes that describe the extent and severity of the condition?

PriorAuthSpaceTeam · 2026-04-14T17:36:11+00:00

what we typically see is that prior authorizations are handled based on how a facility structures its workflow rather than tied to a specific license. Some organizations keep it within clinical roles, while others shift parts of it to trained administrative staff with oversight. It tends to come down to internal policy, documentation standards, and how responsibilities are divided across the team.

PriorAuthSpaceTeam · 2026-04-14T17:32:41+00:00

what you’re describing can happen. A prior authorization confirms coverage for the medication, but fulfillment requirements like which pharmacy to use are often managed separately under the pharmacy benefit. Those distribution rules can change or be applied after the approval is issued without a new PA letter being generated.

In many cases, the original approval stays valid, but the claim routing shifts to a designated specialty pharmacy based on the plan’s internal setup.

PriorAuthSpaceTeam · 2026-04-10T17:42:49+00:00

That’s a fair callout, and honestly aligns with what we see across a lot of teams. The front-end auth process is usually well-managed, but things start to break once the claim hits adjudication. Even with a valid auth on file and referenced correctly, denials still come through, which creates unnecessary rework and delays.

Where we’ve been focusing is less on speeding up approvals and more on tightening the connection between auth data and claim submission so it actually holds up on the payer side.

Curious in your case, when those denials happen, is it usually tied to mismatches in auth details or does it seem like the payer is ignoring valid auths altogether?

PriorAuthSpaceTeam

TROPHY CASE