Healthcare entity

Yemi Okupe

Person

All 1 tracked stories fall under one category: telehealth. Yemi Okupe is most often covered alongside Alcon Inc., which appears in 1 of these 1 story. Each carries 2 original sources on average. We currently track 1 Healthcare story that mention Yemi Okupe, all published on August 18, 2026.

Last mentioned: 6d ago

Entity pulse

Recent coverage · Yemi Okupe

1 story
6 avg impact
100% positive
0% negative

Coverage balance Positive coverage leads. Positive coverage exceeds negative coverage by 100 percentage points.

  • 100% positive

Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.

What the coverage shows about Yemi Okupe

All 1 tracked stories fall under one category: telehealth. Yemi Okupe is most often covered alongside Alcon Inc., which appears in 1 of these 1 story. Each carries 2 original sources on average. We currently track 1 Healthcare story that mention Yemi Okupe, all published on August 18, 2026.

Stories tracked
1
Sources per story
2

Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 11 Healthcare stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.

Coverage cohort

Appears alongside

Other entities that clear the same relevance threshold in stories also covering Yemi Okupe. Shared-story counts are live from our verified record — not editorial picks.

Stories mentioning Yemi Okupe 1

Telehealth Positive

Hims Q2 revenue hits $753M; Alcon eye care grows 7%

Hims & Hers posted 38% revenue growth and 2.89M subscribers while absorbing $81M in nonrecurring charges, and Alcon's core EPS rose 9% to $0.84. Telehealth demand and ocular health innovation are driving divergent profit outcomes.

2 sources

Yemi Okupe is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.

See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.