The first wave of direct-to-patient healthcare was mostly about access. Get the care closer. Remove the waiting room. Eliminate the friction between a person having a problem and a person getting help. That was real and it mattered, and a lot of organizations built meaningful things inside that frame.
The next phase is harder. It's not about closing the distance anymore. It's about building the infrastructure that makes direct-to-patient care sustainable, clinically credible, and commercially viable at scale. And most of what I see in the market suggests we haven't fully made the turn.
what the first wave got right and what it skipped
Speed was the right starting point. Healthcare had chronic access problems. Long waits, narrow windows, geography as a filter on who gets care. Direct-to-patient models proved that technology could remove those constraints, that a person could get a thoughtful clinical interaction without taking half a day off work or driving forty minutes to a specialist.
That proof mattered. It changed expectations in a way that isn't going back. Patients who've experienced frictionless care delivery don't go back to tolerating friction voluntarily. That's a permanent shift in the market and it's a good one.
What the first wave underinvested in was the layer underneath. The clinical infrastructure that determines whether a DTP model is actually delivering appropriate care, or just convenient care. The standards for how you triage a patient in a virtual environment. The protocols for what happens when the presenting issue is more complex than the intake suggested. The systems that connect a virtual touchpoint to the broader care relationship so the patient isn't starting from zero every time.
Without that infrastructure, speed becomes liability. You're moving fast in a direction that hasn't been fully validated, and in healthcare, the cost of getting that wrong isn't a bad NPS score. It's a patient outcome.
why infrastructure is the commercial moat
I've spent time thinking about this from a commercial perspective, not just a clinical one, and the insight that keeps coming back is that infrastructure is the only durable moat in healthcare. Apps get replicated. Features get copied. Price gets competed away. But the clinical infrastructure that makes a DTP model trustworthy, and the operational infrastructure that makes it scalable, those take years to build and can't be bought off a shelf.
The organizations that built that infrastructure early are the ones with defensible market positions now. Not because they outmarketed their competitors, but because they built something that buyers can actually rely on, and in healthcare the bar for reliance is higher than almost any other industry. You're not just buying software. You're extending your clinical brand through a partner, and a failure on their end lands on your reputation.
That's why the procurement conversations in this space are so intensive and why the sales cycles are so long. Buyers aren't being slow. They're being appropriately careful. They're asking whether the infrastructure behind the product is real, whether it can flex with their patient population, whether the clinical standards are rigorous enough to put in front of their own medical leadership without embarrassment.
The companies that can answer those questions confidently close. The ones with great demos and thin infrastructure don't.
what the next phase requires
The organizations that are going to win the next phase of DTP commercialization are building in a few specific directions.
They're investing in clinical standards that can be measured. Not policies that live in a PDF, but protocols that are embedded in how care gets delivered and can be evaluated over time. This is the work that doesn't show up on a pitch deck, but it's what separates a clinical partner from a technology vendor.
They're thinking seriously about continuity. The value of a single DTP interaction is relatively low. The value of a DTP model that connects meaningfully to a patient's ongoing care relationship is very high. The infrastructure question isn't just "can we deliver a visit?" It's "can we deliver a visit that fits into something larger?" That requires integrations, data sharing agreements, care coordination workflows, and a lot of work that happens long before a patient opens an app.
And they're being honest about where direct-to-patient models belong in the care continuum and where they don't. The organizations trying to position DTP as a replacement for in-person care in every clinical context are going to run into both clinical and regulatory friction that slows them down. The ones that understand the model's natural scope, and build within it, are moving faster and closing with more credibility.
the commercial implication
If you're commercializing in this space, the infrastructure story is your story. Not as a features list, but as a proof of rigor. Buyers need to know that what you've built can hold up under scrutiny, that it won't create clinical or compliance risk for them, and that the speed you're promising doesn't come at the cost of the quality they're responsible for.
That story has to be told with specificity. Abstractions about "clinical excellence" and "quality-first care" don't do the work anymore. The market has heard those words too many times from organizations that didn't back them up. What moves a sophisticated buyer is the specific answer to "how do you know your clinical standards are working, and what happens when they're not?"
The access problem in healthcare is largely solvable with technology. The trust problem is not. Trust is built through infrastructure, through standards, through consistent performance over time, and through the humility to acknowledge where the model has edges.
The organizations that build the infrastructure first will earn the market second. In healthcare, there's no shortcut to that order.