Coordination as a Clinical Layer

When we started building 76 Health, we expected to spend most of our time thinking about the operational work — the billing, the scheduling, the prior authorizations, the records flow. The administrative layer that wears practices down and asks too much of patients.

What we've found is that the administrative work is real, but it's not the most interesting layer to build.

The more interesting layer — and the more clinically consequential one — is what we've started calling coordination as a clinical layer.

The work of holding the patient's plan, watching the data, surfacing the right questions, and helping clinicians act on what's actually happening rather than what's documented at the last visit.

This is what we want to think out loud about here.

What "care coordination" usually means

When you hear "care coordination" in healthcare, the meaning depends on who's using the term.

For an insurance company, it usually means navigation services that help members understand benefits and find in-network providers.

For a hospital, it usually means discharge planning — making sure the patient gets home with the right follow-up scheduled.

For a primary care practice, it sometimes means the front desk fielding calls and transferring records.

For a value-based care company, it usually means population health management — tracking which patients are due for screenings, which are at risk of escalation, which need outreach.

None of these are coordination as a clinical layer. They're each pieces of a broader category, but they don't add up to what the patient actually needs in the days between visits.

What's missing, in most patients' care, is a clinical layer that watches the plan as it unfolds, against the data, in real time — and adjusts course before the next appointment, not at it.

What coordination as a clinical layer actually does

A few specific functions, if we describe what we've been building toward.

It holds the plan. The plan signed by your physician at the start of an episode is the plan we work from. Your therapist works from it. Your check-ins are organized against it. Your progress is measured against it. The plan is the through-line.

It captures function and outcome data. Not at annual visits. Continuously. Weekly check-ins. Validated outcome measures. The data is collected because it informs the next clinical decision, not because it satisfies a reporting requirement.

It watches for stalls. The patterns we've talked about in other articles — pain that plateaus, function that regresses, side effects that surface — show up first in the data. The coordination layer's job is to surface those patterns to the clinician who can act on them.

It triggers escalation when warranted. Not every plateau is a flag. Not every stall is concerning. But the decisions about when to bring the physician back in, when to adjust the plan, when to escalate to imaging or specialist consult — those decisions need clinical eyes on the data, and the coordination layer is what makes that possible.

It coordinates around the patient's other providers. The primary care doctor. The specialists. The therapist. The pharmacist. Everyone touching the case stays in the loop, working from the same plan, instead of running parallel tracks.

It absorbs the administrative work that wasn't supposed to be the patient's job. The records, the prior auths, the eligibility checks, the appointment shuffling. Those happen below the clinical layer, but the patient stops having to do them.

That's the layer. None of those functions are individually novel. The combination, delivered consistently, is unusual.

Why it's harder to build than it sounds

The temptation, when describing care coordination, is to make it sound like software.

You could imagine a dashboard that shows the patient's data. A workflow tool that triggers the right alerts. An integration with the record system that pulls everything together.

The software pieces are real. They matter. But they're not the hard part.

The hard part is staffing, training, and sustaining the human layer that actually does the work — the care coordinator who knows the patient, the clinical lead who reviews the data, the rhythm of touchpoints that catches the patterns. None of that is automated. All of it depends on people doing the work well, over time, across many patients.

The other hard part is structural. Healthcare reimbursement is largely visit-based. The work of coordination doesn't have a billing code in most contexts. Practices that build coordination layers do so as a financial bet — that the coordination will produce outcomes, retention, and downstream economics that justify the investment.

The third hard part is consistency. Coordination is most valuable when it's sustained — when the same coordinator is with the patient across the arc, when the data is captured every week, when the patterns get surfaced reliably. The moment coordination becomes inconsistent, the patient stops trusting it. The moment it becomes industrialized in the wrong way — call centers, scripted touchpoints, automation without humans — it stops being clinical.

What the evidence says about getting it right

The published research on coordinated care models has been broadly positive — across multiple conditions, multiple delivery models, and multiple outcome measures.

The Hinge and Sword findings we discussed in another article are part of the evidence base. Studies of coordinated care for chronic conditions consistently show improvements in patient-reported outcomes, function, and downstream cost. The research isn't perfect — selection effects, model differences, and inconsistent definitions of "coordination" all complicate the synthesis — but the direction is clear.

What's harder to find is research on what specific elements of coordination matter most. Is it the data capture? The continuity of the coordinator? The integration with the clinical team? The rhythm of check-ins? Probably all of the above, in some balance.

That ambiguity is part of why building this well is hard. The principles are clear. The exact recipe is still being worked out.

What we've been thinking about

We're spending a lot of time, while building 76 Health, on what coordination as a clinical layer actually requires.

The temptation is to lean on technology to solve the layer. The pattern we've been arriving at is that technology helps where the work is structured — capturing data, tracking patterns, triggering workflows. But the clinical layer itself depends on people who hold the through-line.

What we're trying to build, ultimately, is a coordination layer that's structured enough to scale, human enough to be trusted, and clinical enough to actually change outcomes.

We're early. We don't have the full operational version yet. But we keep coming back to the idea that this layer — clinical care coordination, done as a discipline — is the missing piece for the conditions we're focused on.

If we get it right, it's the layer that closes the gap between what the evidence supports and what patients actually experience.

That's the work.

Sources: Hinge Health and Sword Health peer-reviewed published outcomes; broader literature on coordinated care for chronic conditions.