This Summer in Digital Health: Now With 78% More Original Thoughts!

Welcome to This, er, Summer in Digital Health. We’re going to pretend I took the summer off from highlighting key headlines in healthcare technology and why they matter because I was busy peering off into the distance contemplating the right format to better engage with my readers and not because the least stressful way for the Beastwoods to navigate the transition from preschool to summer camp to summer vacation to kindergarten was for me to work quite a bit less.

Anyway … welcome to my new newsletter format! There’s still a handful of key themes, though there will probably be fewer than I’ve featured in the past. What’s new? More insights straight from my brain! When lots of headlines drop on the same topic, it’s easy to miss the forest for the trees. Here’s to hoping my perspective / free time to actually sit with these stories helps you make better sense of it all.

Does healthcare fear AI is too risky for clinical care?

If the first few months of 2026 were about the promise of AI for clinical care, as seemingly every tech company released an AI agent to automate this and streamline that, the headlines this summer seemed to suggest the honeymoon period is over.

My take: AI for clinical care is starting to seem a lot like coffee. One day, it’s bad for you. The next day, it’s good. The next day, it’s still good, but only in excessive quantities that make you jittery, paranoid, and irregular. Organizations clearly know they need to erect guardrails and draft governance policies, but FOMO seems to get in the way of taking these pragmatic and logical but also time-consuming steps. Unfortunately, that inaction is going to bite them back. I wouldn’t be surprised if the majority of pilots die on the vines in the next several months, along with the companies that created them.

With wearable data, everything old is new again

This summer, both Apple and Google announced updates to the health, fitness, and safety features linked to their watches and wearables. Meanwhile, a recent AMA survey found that most physicians do in fact review wearable data, 77% find it valuable for clinical care, and close to 30% have acted on the data they saw – findings that even surprised the association’s CEO.

However, only 6% have been able to integrate wearable data with clinical workflows. On top of that, many physicians don’t really trust wearable data, especially if it comes from FDA-cleared and not FDA-approved devices. Plus, few bother to use diagnostic and billing codes for remote monitoring, which would be the main motivation to look at and act upon wearable (or sensor) data in the first place.

My take: The challenge of figuring out what clinical teams are supposed to do with heaps of consumer wearable data is a tale as old as time. The evolution of technology over the last couple decades – from spreadsheets to databases to dashboards to generative AI summaries – clearly hasn’t made things any easier. As with a lot of healthcare’s problems, this one would have been solved by now if stakeholders wanted it to be. Since there’s no incentive for providers to even look at data, let alone interpret it and incorporate it into care plans, it’s just going to sit there, largely ignored, as it always has been.

Digital health apps benefit some conditions more than others

A literature review in The Lancet found that digital health apps work well for managing many conditions and symptoms – namely blood pressure, blood glucose, mental health, body weight, physical activity, and medication adherence – but not everything. Managing cholesterol, body fat, heart disease, and healthy diets proved to be difficult with apps alone, as these areas often require clinical inventions in addition to the educational content, feedback, and support loops that apps tend to specialize in.

My take: A lot of healthcare research confirms things we already knew, or at least suspected to be true. While this paper fits that description, that’s not necessarily a bad thing. Given the industry’s incessant push to do more with less, particularly when it comes to engaging with patients using technology that never quite lives up to its ROI potential, it’s helpful to have clear evidence of which apps can stand alone and which apps would need an all-important human touch and, depending on who, you ask, may not provide enough juice to be worth the squeeze.

The Epic effect remains strong but shows some cracks

Research firm Redesign Health published a report on the Epic Effect, or the strong gravitational pull of the industry’s leading technology vendor. More than 70% of health systems surveyed described themselves as Epic-first, and more than 90% are confident the vendor can execute on its AI roadmap. That said, nearly two-thirds would buy from a startup if it did something Epic doesn’t do as well, such as imaging, quality reporting, and scheduling and discharge. Also, 48% of health system admit they select Epic because it’s “good enough,” which the consultancy said suggests that “Epic gets to clear a lower bar.”

My take: Winston Churchill is credited with saying that democracy is the worst form of government except for all the other ones. Healthcare seems to feel the same way about Epic. Keynote speakers and other thought leaders are quick to offer criticism – some of it warranted, given its history of integration frustration and recent antitrust allegations – yet the company’s market share is only going up. Yes, there are sunk costs associated with keeping your current EHR, and it sure helps when the same vendor offers integrated features that meet needs you didn’t realize you had. At the same time, let’s remember that Judy founded Epic in 1979 (the year before I was born, mind you). That means the industry has had almost five decades to build a better alternative.

Bulking up build efforts in the build vs. buy debate

A couple publications offered new takes on the omnipresent build vs. buy question for healthcare’s technology teams. Healthcare Dive unpacked the effort to build oncology patient management tools at NYU Langone Health and Dana-Farber Cancer Institute, and Digital Health Insights explained the Cedars-Sinai approach to engage stakeholders from the beginning to ensure efforts succeed. That engagement helps avoid the pilot purgatory problem that plagues innovation efforts viewed less as tried-and-true technology implementations and more as experiments; it also helps demonstrate to decision-makers that teams know what they’re doing and deserve some leeway to tinker if they have a good idea.

My take: It’s interesting to see this topic continually resurface, as it’s a tale almost as old as time. For general-purpose technology, or anything that needs to be done at scale, Buy is a pretty clear answer – or Partner, if a health system is large enough to meaningfully influence what a technology vendor will do. Build makes more sense for anything highly specialized and/or personalized, either because the patient (sub)population is unique or the process is nuanced (a polite way to say complicated). Yes, AI is moving the needle on scaling specialized, personalized, and nuanced workflows enough to shift some technology from Build into Partner or Buy, but systems still need to weigh how much control over the process they’re willing to give up for what very well may be the temporary convenience of not doing it themselves.

Digital health funding trends don’t shock or surprise

The latest analysis of digital health funding from Rock Health found that deals are getting a little bit bigger, while deals more than $100 million make up an increasing volume of all capital invested. The firm found that investors prioritize domain expertise, scalability, post-implementation support (especially when it comes to AI), and broad partner ecosystems. Conversely, Modern Healthcare reported that investors shy away from point solutions, products that don’t scale, and business models solely reliant on reimbursement models subject to the whims of the Trump administration (my words).

My take: The points about which product categories aren’t seeing much investment make perfect sense and suggest the digital health landscape is maturing quite a bit. This also ties back to a couple of the other themes. If Epic is going all-in on AI, it stands to reason that AI startups will soon face a steep uphill battle and cannot rely on their products alone. If more health systems are comfortable rolling their own software, there’s less room for unfamiliar partners. Plus, just about everyone’s operating on razor-thin margins, and ROI is one of the first terms to come up in any conversation about technology investment. I get the feeling a slowdown is coming.

This Month (or so) In Digital Health: AI, Data, GLP-1s, and Money (Lots and Lots of Money)

Welcome to the eighth edition of This Month in Digital Health, where you get to read my very own thoughts on the news and trends that caught my attention over the last few weeks. We’re a bit tardy this month – Sandwich Generation Caregiving for the win, am I right? – which means there’s been extra time to gather hot takes on AI, data, healthcare costs, and GLP-1s. Have at it, folks.

AI likes it easy. Healthcare isn’t. Therein lies the rub. Yet another paper has shown that LLMs can outperform physicians when making rote decisions (even general-purpose LLMs) that don’t have to account for the stuff that happens in real life – whether it’s delays in prior authorization or claims denials powered by AI or, like, patients’ unaddressed social needs or the stress of the hospital. Nor does it help that providers fear overreliance on AI will diminish clinicians’ critical thinking capabilities.

Who can access data? What is data? What is access? Rock Health found that 57% of Americans own at least one wearable, and many are tracking health metrics. That’s good! The bad news: Wellness apps interpreting device data aren’t really regulated, and physicians have no idea how they conclude a patient is at risk of, say, depression. Plugging data into an LLM isn’t much better, as general-purpose LLMs aren’t HIPAA covered entities (though the healthcare-specific ones are).

GLP-1s are taking over healthcare, and not in the best ways. Speaking of wearables, Mass General and Samsung Health are partnering to see whether a smartwatch can track muscle loss in adults on a GLP-1. That’s good, because it’s a common concern for patients who lose weight. Other concerns are emerging, too, including GLP-1 prescriptions from telehealth providers who don’t talk about the risks or the importance of healthy habits, and the efficacy of GLP-1 pills, which has self-employed insurers thinking twice about insurance coverage.

Great googily moogily, healthcare is expensive. On top of everything else, GLP-1s are making healthcare even more expensive – to the tune of 9% increases in commercial costs in 2027, per PwC. Only 7 nonprofit Blues plans had positive operating margins in 2025, and many provider-sponsored health plans are giving up amid rising costs and general industry instability. Speaking of which, more than 75% of executives think healthcare’s financial instability will reach an existential tipping point before the end of the decade. Good times.

Meanwhile, in other stories of interest:

  • Given the odd juxtaposition of primary care (with low costs and generally stable utilization) and health insurance (which is meant to cover expensive, unpredictable events), a JAMA paper proposed the notion of primary care as a public utility through which states create a common fund that pays practices directly. Insurers could still compete on other lines of business. I’ve heard worse.
  • The ACCESS Model for Medicare goes into effect on July 5. With 150+ participants already lined up, Second Opinion posed a reasonable question: What about ACCESS for Medicaid? Makes sense to me, especially since states have embraced managed care.
  • When it comes to rural health transformation, the numbers don’t add up. As $50 billion in federal aid doesn’t equal nearly $1 trillion in losses, states are focusing on cost-cutting strategies, not innovation. Good job, everyone.

Happy summer, Northern Hemisphere. If you know me, you know this is my least favorite time of the year. (And if you don’t, well, now you do.) If you need me, I’ll be under an oscillating fan, within a foot of an AC, and waiting until the humidity breaks to do anything that will cause me to begin to sweat.

The Beastwood Files: May 2026

I survived my marathon, helped my son adhere hundreds of monster truck stickers to sheets of paper, took my mother to two doctor’s appointments, installed our window ACs, and wrote a few things here and there to boot. In other words, just another month here at Brian Eastwood Writes, LLC. (And I was named Employee of the Month AGAIN!)

Stuff I Wrote

Things I Did, Marathon Edition

  • Finish my 5th consecutive Vermont City Marathon (and 6th marathon since my won was born) within the two-minute time window of 3:24:31 to 3:26:31 (in this case, 3:26:23), which means I’m officially nothing if not consistent
  • Gather acceptable snacks to share with my son at the finish line, including slices of pizza, Nutri-Grain bars, and the all-important free underripe bananas that are the reason like 73% of marathon runners compete
  • Wear brand-new compression socks to recover from said marathon because I forgot to pack them and had to purchase a new pair the day before the race
  • Remember to pack everything else that mattered – including the cowbell than my son shook vigorously while in the hotel room but not (AFAIK) while outside cheering for runners

Adventures in Fatherhood

  • We completed / survived our first-ever Kid Race, which was a 1/2-mile loop in Burlington, Vermont’s lovely Waterfront Park. We also overcame our pre-race jitters, which were 100% attributable to the presence of mascots in unexpected proximity. We celebrated with pre-packaged trail mix and a sampling from a local ice cream truck.
  • We also experienced and enjoyed our first-ever roller coaster at a local fundraiser fair, though our favorite part very well may have been the fried dough. (Can’t argue with that.) We decided we didn’t like the teacups – and I learned I can’t handle the teacups as well as I used to – but did like the Ferris wheel (even if the waiting was the hardest part).
  • Yes, we heard the sonic boom from the meteorite that landed in the middle of Cape Cod Bay. No, we didn’t think anything of it at the time, especially as our neighbors are in the midst of a large renovation project and it hasn’t been uncommon to hear things get loudly dropped into a Dumpster.

Enjoy June and the beginning of summer. We’re gearing up for a pre-summer-vacation trip to Cape Cod , preschool graduation, and a trip to New Hampshire for the Fourth. We’re NOT going to New Hampshire in June because I told a story once about black files and now we’re convinced that’s when there are YUCKY BUGS in our neighbor to the north. I’m sure we’d have fun, as we talk about the YUCKY BUGS while laughing, but between Champy and the teacups, I’ve scarred my son enough for quite some time.

The Beastwood Files: April 2026

A panel on tough questions for healthcare marketers in 2026 at Swaay.Health LIVE

I’ve been able to take a bit of a breather over the last few weeks. The work schedule has lightened up (on purpose), the need to fill out and sign forms for kindergarten in the fall has abated (for now), and I’ve entered taper time for my spring marathon (which is Memorial Day weekend in Burlington, Vermont). I even had time to spend a day at Swaay.Health LIVE, catching up with old friends, learning a thing or two about healthcare IT marketing, and looking important sitting on a tall stool while moderating a panel.

Things I Wrote

Stuff I Did

  • Leave the house during the work week to attend a conference, which was such a big deal that I felt like mentioning it twice
  • Finish my darn eBook, which was also such a big deal that it warrants a second mention
  • Finally take a deep breath and schedule body work for our car after I was in a minor but embarrassing fender-bender in the preschool parking lot this winter
  • Help my son keep his secret about the Mother’s Day present he was making at school and the card he made
  • Continue to adhere the new household rule: Don’t get so much cereal that it doesn’t fit in the cupboard, Brian

Adventures in Fatherhood

  • We fulfilled a months-long dream and went to Monster Jam the day before Mother’s Day. We admittedly had more fun at the pre-show pit party (when you get to look at the trucks and meet the drivers) than during the show (when it’s loud and there’s a decent chance the trucks may flip over). We decided we prefer looking at pictures of monster trucks doing tricks in books than seeing them in person – though we do like stadium snacks.
  • Luckily, our monster-truck themed birthday party the prior week was much more successful. I made multiple large cardboard ramps for toy trucks to run down, and my wife and son worked together on crafts and decorations. Special thanks to Costco, Chewy, and especially REI for supplying our home with large boxes – the latter with a long, thin ski box that was just the right size for a single truck. Also, no one got scared when the toy trucks flipped over.
  • One of our birthday presents was a Big Boy Bike with pedals and no training wheels. Our first ride was quite successful until we bumped into a bridge at a park. I then explained to my son that Daddy did the exact same thing when he was leaning to ride a bicycle, only he was in his 30s and it therefore hurt a lot more. (I didn’t show him the scar.)

I hope everyone had a happy Mother’s Day. Ours was rather relaxing, which was entirely the point. I think our son was old enough to understand that’s what it’s all about. We’ll see if Father’s Day proceeds the same way…