The 90-Day Data Black Hole: Why You Don't Know Your True Amputation Rate (And How to Fix It)

The Rearview Mirror Model Is Broken for Wound Care

Claims data is retrospective. That's its nature. A claim gets filed when a service is rendered. It gets processed. It gets audited. It gets reported. By the time it hits your analytics dashboard, 60-90 days have passed.

For most chronic diseases, this lag is manageable. You can see that a patient had an ER visit last month and adjust their care plan today.

But for wounds, especially progressive diabetic foot ulcers and pressure injuries, a 90-day lag is catastrophic. A wound can go from "manageable" to "requires amputation" in 4-8 weeks. If your data system is telling you about the problem 90 days after it started, you're missing the entire intervention window.

Here's what happens in real time:

• Week 1: Wound appears. No claims yet.
• Week 2-3: Patient sees PCP, gets referred to wound center. Still no claims in your system.
• Week 4-6: Wound is stalling or worsening. Clinical alarm bells should be ringing. But your dashboard shows nothing yet.
• Week 6-8: Infection develops. Patient goes to ER or gets admitted. Now there are claims, but they're still processing.
• Week 10-12: Amputation happens. Claim hasn't hit your system yet.
• Month 4: The amputation claim finally appears in your reports. You're now reviewing an event that happened 12 weeks ago.

By the time your analytics team has confirmed the problem, the problem is already permanent.

Real-Time Clinical Data vs. Retrospective Claims Data

There's a better way. And it changes everything about how you manage your highest-risk patients.

Instead of waiting for claims data, imagine a system where your wound care clinician reports on wound trajectory weekly. Not monthly. Weekly.

Week 1: Wound presents. Clinician documents baseline size, depth, drainage, surrounding tissue health. Is this wound healing? Stalling? Worsening?

Week 2: Clinician is back in the home. Same wound. Is it smaller? Same size? Larger? Is there new drainage? Early signs of cellulitis? New pain?

Week 4: Four weeks of data points. The trajectory is clear. This wound is on a healing path (great), or it's stalling despite appropriate care (escalation needed), or it's worsening (emergency intervention required).

This is GPS. Real-time position data. Your population health team isn't waiting for claims. They're seeing the trajectory as it unfolds.

Integration Into Your Population Health Dashboard

Here's what changes when you feed real-time wound data into your population health infrastructure:

Every Monday morning, your population health team gets an update: "15 chronic wounds under active management. 12 on healing trajectory. 2 stalling (escalation recommended). 1 showing signs of systemic infection (needs vascular assessment today)."

Now you're not reacting to events. You're anticipating them. The patient showing signs of cellulitis gets a same-day vascular consult, not a week later. The wound that's stalling at 6 weeks gets escalated to infectious disease before sepsis develops.

This is the difference between "managing amputations" and "preventing them."

The data integration works like this:

1. Clinical assessments from home visits feed into a centralized database weekly
2. Wound metrics (size, depth, healing rate, infection risk) are translated into risk scores
3. Those risk scores automatically populate your population health dashboard alongside claims data, EHR data, and care management notes
4. Your population health team can filter for "high-risk wounds" and trigger interventions in real time
5. Historical data is retained, so you can see the full trajectory—not just the latest snapshot

Why This Matters for Your Risk-Based Contracts

If you're operating under a full-risk capitation model or a shared-savings arrangement, real-time wound data isn't nice-to-have. It's essential.

Under fee-for-service, a delayed amputation is just an expensive claim. Under risk-based contracting, a preventable amputation is the difference between hitting your quality metrics and missing them. It's the difference between meeting your cost target and blowing it.

An amputation in January shows up in your data in April. By then, you're analyzing Q1 results, assessing whether you need to take corrective action. But the corrective action was needed in week 6, not month 4.

Real-time clinical data changes that calculus. Your data is your action system, not your historical archive.

The Accountability Question

Here's the hard truth: Most MA plans and ACOs don't actually know their true amputation rate. They know their claim-based amputation rate, which lags 3-4 months. But they don't know what's happening in their population right now.

Ask your analytics team: "How many patients in our population are currently managing unhealed wounds with evidence of progression?" They probably can't answer that. They're working from claims data that's old.

Ask them: "Of the wounds currently being treated, how many are on a healing trajectory vs. stalling vs. worsening?" They probably can't answer that either.

This is the data black hole. Your population is full of clinical activity you can't see because your data system is built for historical analysis, not real-time management.

And structure determines behavior. If your data infrastructure is designed around retrospective claims analysis, you'll default to managing amputations instead of preventing them. If your data infrastructure includes real-time clinical feeds, you'll naturally shift to early intervention and escalation.

The patients are the same. The clinical opportunity is the same. The difference is whether you're seeing the signal in time to act on it.