Liger Cub@realLigerCub
$NURS.V - Shafin provided the following detailed answer on why Palumbo is a non-issue:
1. Joe was our original medical director back when Hydreight was tiny.
He had ~50 licenses, which helped us get the early infrastructure in place.
That was years ago.
2. Since mid-2024 the business has not been tied to him — by design.
We intentionally removed any single-MD dependency as we scaled.
Today we have:
• 25+ medical directors
• 300+ physicians
• Redundant coverage across all 50 state
No single license, physician, or medical director can impact the platform.
3. His current role is strictly policy/procedure development.
Not patient-facing.
Not tied to active clinical services.
His licenses do not affect anything Hydreight delivers day-to-day.
4. The “5 disciplinary actions” narrative is misleading.
State boards often copy each other’s notices — it makes one issue look like five.
This is extremely common for MDs who have supervised many brick-and-mortar clinics over the years.
If a facility screws something up, the supervising doctor gets called in.
Not unique, not Hydreight-related, and not a red flag.
5. He will continue to get called in by boards because that’s what happens when you’ve overseen dozens of clinics.
It’s normal, and it has nothing to do with Hydreight.
No impact on operations, compliance, or service delivery.
6. Worst-case scenario? Zero business risk.,
If any physician in our network can’t practice in a specific state, we simply replace coverage.
No dependency, no disruption — this is exactly why we built a distributed doctor network.
Bottom line:
Hydreight is not exposed to one doctor’s personal licensing matters.
The platform was engineered to be redundant, scalable, and regulation-proof.
That’s why we’re ahead of the curve while the rest of the market is still trying to figure out compliance.
Happy to dig in further, but operational risk here rounds to zero.
