Skip to main content
Insights

Healthcare needs solutions, not more products.

Erik Abel, PharmD, MBA · May 2, 2025 · 7 min read

Healthcare's innovation pipeline is not short on products. It is short on purpose. Over-spec'd devices chase feature and function wars no one asked for, and the result exposes a growing divide between product thinking and solution building.

Across too much of healthcare and medtech, spanning devices large and small, technology in every form, and AI in many shapes, we are witnessing a chronic industry condition. Technologies engineered for technical achievement rather than clinical relevance, operational simplicity, or measurable value.

The diagnosis is clear. Pick your poison, as each may apply.

  • Z99.99, Chronic Feature Fatigue. Endless spec upgrades without solving real clinical or operational problems.
  • Z00.999, Encounter for Device with No Clinical Value. Technologies that add workflow burden, not workflow clarity.
  • T82.89XA, Malfunction of Innovation, Initial Encounter. Brilliant inventions that stall when they meet the complexity of real-world healthcare.

Why this matters now

Healthcare is not buying devices anymore. It is buying outcomes, workflow efficiency, embedded decision support, elevated patient experience, and measurable system value.

Why? Because that is what the system and the market demand. Yet too many companies still pursue strategies rooted in old habits.

  • Technical isolation. Building standalone products with no data liquidity or interoperability.
  • Spec sheet escalation. Assuming more features equal commercial appeal, and maybe adoption.
  • Transactional selling. Pushing individual products rather than enabling care transformation.

The result? Devices that do not fit the market need. Workflows that do not improve. Value propositions that do not resonate. Innovation efforts that burn capital without bending cost curves in a socially optimal direction.

The solution-centered mindset

To thrive, companies must reset how they think about innovation, commercialization, and customer engagement, starting with roadmaps and internal process.

A comparison of mindsets.
DimensionProduct-centered approachSolution-centered approach
Technology focusTech performance in isolationEnable full care pathways and real-world clinical decisions
Development prioritiesMore features, faster specsOutcome measurement, interoperability, workflow fit
Go-to-market strategySell devices on spec superiorityDeliver bundled, interoperable solutions focused on outcomes
Provider experienceManual, fragmented integrationEmbedded decision support, streamlined data flow
Payer enablementLittle evidence, high prior-auth frictionClear value evidence, outcome-linked ROI pathways
Patient experienceDisjointed, delayed diagnosis and treatmentSeamless escalation, faster answers and access, better engagement

It is not enough to build the solution. Price, package, and deliver it differently.

Even the most elegant solution will stall without a commercial model that reflects its value. Solution-centered strategies must be paired with go-to-market approaches and business models that lower adoption barriers and align incentives across stakeholders. That includes advancing approaches for:

  • Subscription or usage-based models that shift capital expense to operational ROI.
  • Outcome-based pricing that aligns with value-based care contracts.
  • Managed service models that bundle devices, software, services, and support into a turnkey care delivery platform.
  • Risk-sharing structures that let provider organizations and payers co-invest in transformation.

Repackaging solutions through these models does not just make adoption easier. It makes value tangible.

Interoperability is no longer optional. It must go beyond technical checkboxes.

  • Contractual interoperability may open access.
  • Technical interoperability may transmit data.
  • Semantic interoperability may translate meaning.

But business and clinical interoperability are what unlock system value. They empower organizations to:

  • Support seamless patient journeys.
  • Empower providers with real-time, actionable data and clinical decision support.
  • Enable payers to recognize and reward value without excess friction.
  • Drive continuous evidence generation and outcomes validation.

Disconnected devices, even powerful ones, do not create scalable change. Connected systems do. As I have said before, solving the less glamorous problems may be the most attractive work, because that is where monotony, burnout, and fragmentation live.

Solution thinking across the care continuum

Imagine a typical patient journey.

  • Screening. Early risk detection through wearables, AI-enhanced screening tools, and predictive analytics.
  • Diagnosis. Seamless escalation from point-of-care diagnostics, such as ultrasound and ECG, to advanced imaging and specialist consultation without fragmentation or friction.
  • Treatment planning. Integrated data platforms, AI-enabled decision support, and interdisciplinary coordination that accelerate time to treatment and reduce variability.
  • Ongoing management. Remote patient monitoring, home-based diagnostics, and population health platforms that prevent readmissions and lower the long-term cost of care.

Every product, platform, or service should map to and enhance this continuum. If you cannot connect your offering to meaningful improvement across the entire patient and provider journey and the value chain, you are not delivering a solution. You are delivering a widget.

The future belongs to solution builders

Healthcare should no longer tolerate technological brilliance that does not translate to clinical relevance, operational value, and financial sustainability. To help our patients most, we need to lean in differently. I believe the healthcare and healthtech companies that lead the next decade will:

  • Design for workflows horizontally across the continuum, not in fragmented silos.
  • Prove outcomes, not just pitch features.
  • Build systems of success, not just sell products.

Chronic feature fatigue is treatable, but only if we stop assuming success equals specs and features, and instead start delivering system-focused transformation.

The ICD-10 codes referenced here (Z99.99, Z00.999, T82.89XA) are used satirically to illustrate common challenges in the medtech industry. They are not real clinical codes and should not be interpreted as actual medical classifications. All views and analyses reflect my independent professional perspective and do not represent the views or positions of any current or former employer or affiliated organization.

Working on something in the gap?

I take a small number of advisory engagements, board seats, and speaking invitations each year.

Start a Conversation More Insights