healthcare optimist | simply zero accomplishments

New York, USA
Joined April 2020
My one career intention is to build something that betters healthcare I write to learn how to do this out loud: research intriguing strategies & products, explore trends, and muse on what may be next. Here's Quite A Few Claims - my collection of thoughts quiteafewclaims.substack.com…
1
2
6
we've discovered teleportation and we're using it to get to the bus station on time. healthcare especially is full of assumptions we've stopped questioning. it's about time we picked some apart. a billion years since i last wrote something, so might as well have an upbeat title.
1
1
83
my opinion of how smart someone is solely depends on whether or not they say “chassis” when talking about their business idea
1
126
Much of the pain of digital health (and sidecar point solutions for enterprises in general) that is often blamed on EHRs is actually a manifestation of the principal agent problem - where one party (the agent) makes decisions on behalf of another party (the principal), but has different interests and incentives. The expectation is that if you build a good product that is attuned to a user and solves their problem, you will be successful. This is largely true in consumer facing software (if you can handle CAC) - the buyer and the user are the same. When it comes to super small businesses, the buying motion of SMBs can resemble a DTC sale, as the buyer and the user may be the same. If they're not, they're usually close enough to have the same or similar interests. This is not the case for larger and larger enterprises. For example, the CEO wants efficient operations and profitability. The doctor wants more time spent with patients and medical decision autonomy. Your choice to sell to large healthcare organizations (or really any enterprise in general) incurs a silent cost. You now are building for two distinct sets of stakeholders with fundamentally different and often opposing needs - the economic buyer who makes the purchase decision and controls the budget, and the end user who has to actually use your product day-to-day. This tension forces you to either compromise your product's user experience to satisfy buyer requirements, or risk failing to gain institutional adoption despite having happy users. Every GTM motion has pros and cons. This is just the reality of the enterprise motion.
3
4
1
19
2,048
if you're not reading @markolschesky's substack you're missing out especially if you're building healthcare tech products especially if you're thinking about LLM implementations into your stack open.substack.com/pub/health…
1
2
259
tyra banks 🤝 NVIDIA training models
1
2
528
one of the keys to unlocking plg in healthcare is reducing friction in data exchange for data that contains PHI, HIPAA presents major blockers i defined most of the viable paths in this tweet thread, but there's one i didn't touch on: de-identification xitter.cf/_btlee_/status/1681723…
what are the typical swim lanes you can use to build for end users at Covered Entity organizations, and potentially perform PLG? 1. Product-Led Excitement 2. Non-PHI Workflows 3. Cash Pay Transactions 4. End User Represents Covered Entity 5. Patient Authorizations
2
1
241
combining local real-time de-id w/ re-id is pretty powerful you can utilize a 3rd-party app to improve your own service (currently, commonly a closed-source LLM) or covered entity end-users can use your service w/ clinical context below: diagram of potential workflow unlocks
2
1
100
going one step further (s/o @SamirUnni) Nabla's data service is stateless for workflows where you want statefulness (inevitable at scale, and with certain types of workflow), a decentralized build could be interesting to pursue
1
1
738
If you're into product-led growth in digital health, @_btlee_ two-part piece on product-led growth is so good substack.com/notes/post/p-13…
2
4
5
603
what are the typical swim lanes you can use to build for end users at Covered Entity organizations, and potentially perform PLG? 1. Product-Led Excitement 2. Non-PHI Workflows 3. Cash Pay Transactions 4. End User Represents Covered Entity 5. Patient Authorizations
2
1
2
688
End User Represents Covered Entity target orgs where distance to BAA signer ➡️ 0 - aka sole practitioners & SMBs - and give standard BAAs @GetHealthie does this physician consolidation is a main headwind, but independence is increasingly championed xitter.cf/jayparkinson/status/16…
I met a physician founder yesterday who built an entirely online practice with 20 providers to $5m in AR, traditional FFS insurance, bootstrapped. I haven’t seen that before and I’m very encouraged by this.
2
1
253
Patient Authorization present data consent flows thoughtfully to the CE end user and patient, and this has potential you can find large patient hubs like @ciitizen did provide patient side value for further unlock, like @AbridgeHQ or @WeareElaborate
1
45