HN user

kunle

5,501 karma

1JHPSV5xoib3Q6hBAQQivhuJ9SCiBRTM9e

Cash.app

Mailform.io

Faxrocket.com

Sendovernightmail.com

splitcsv.com

easytts.com

easymailmerge.com

finepostcards.com

matchboxvideo.com

carbonhealth.com

healthplanexplorer.com

www.refract.vc

www.substrate.cc

Posts426
Comments385
View on HN
www.substrateai.com 29d ago

Show HN: An eligibility agent focused on claims denials

kunle
3pts0
writing.kunle.app 6mo ago

Coding Agents Are for Everyone

kunle
3pts1
writing.kunle.app 6mo ago

Synthesis Is Now the Bottleneck

kunle
2pts0
writing.kunle.app 8mo ago

Sovereign Stablecoins

kunle
1pts0
writing.kunle.app 11mo ago

A Deep Research Agent for Healthcare Claims

kunle
2pts1
writing.kunle.app 1y ago

The AI Agent schism: deterministic vs. non deterministic

kunle
1pts0
writing.kunle.app 1y ago

Patients need an AI scribe of their own

kunle
1pts0
writing.kunle.app 1y ago

Red Team/Blue Team: AI Agents as adversaries for building fraud models

kunle
3pts1
writing.kunle.app 1y ago

Enterprise use cases for stablecoins are coming into focus

kunle
1pts0
writing.kunle.app 1y ago

How to solve 2FA/multi-factor auth for AI Agents (and bots)

kunle
1pts0
writing.kunle.app 1y ago

The glasses are the way (on Facebook Glasses being the next great platform)

kunle
3pts0
writing.kunle.app 2y ago

Price transparency and how to fix patient eligibility/registration in healthcare

kunle
1pts1
news.ucr.edu 2y ago

Planet hunters reveal catalog of worlds

kunle
2pts0
writing.kunle.app 2y ago

Stablecoins will become the largest holder of US Government debt

kunle
3pts2
writing.kunle.app 2y ago

Receipts API as a Service

kunle
1pts0
writing.kunle.app 2y ago

Common Problems with Bank Partners (for fintech companies)

kunle
1pts0
writing.kunle.app 2y ago

Building differentiation in technology enabled healthcare

kunle
1pts0
writing.kunle.app 2y ago

Electric Vehicle charging orchestration as-a-service

kunle
1pts0
ayokunle.substack.com 3y ago

JPMChase doesn't care about your deposits

kunle
16pts5
www.healthplanexplorer.com 3y ago

Show HN: HealthPlanExplorer.com: Search & parse insurance plan MRF Files

kunle
22pts19
kunle.app 3y ago

Exploring the Transparency in Coverage final rule – a petabyte of data a month

kunle
2pts1
kunle.app 3y ago

Bank portability for startups – when to get it, why and how to prep

kunle
3pts1
tether.to 3y ago

Hey Bloomberg, Here’s the Short of It

kunle
2pts1
kunle.app 3y ago

Networked Notebooks – engineering serendipity with GPT-3

kunle
1pts0
kunle.app 4y ago

Crypto primitives – real world use cases for crypto/Web3/DeFi

kunle
3pts0
kunle.app 4y ago

The Durbin Amendment is responsible for modern fintech as we know it

kunle
2pts3
carbonhealth.com 4y ago

An API for Health Insurance Coverage as a Service

kunle
1pts0
carbonhealth.com 4y ago

Show HN: Price transparency in healthcare (putting healthcare prices online)

kunle
1pts0
kunle.app 4y ago

Show HN: Add a payment card to the browser's autofill (Safari and Chrome only)

kunle
2pts0
kunle.app 4y ago

Driving payment card adoption with deeplinks, applinks, long cards, and autofill

kunle
19pts6

Put together a deep dive into healthcare price transparency, the patient registration and eligibility process, how it's broken, and how it leads to providers not getting fairly compensated, and drives higher costs for all healthcare.

Covers: - how our current tools fail providers and patients - how payors benefit from the status quo and have no incentive to fix it systemically - how providers can provide price transparency to patients (mostly in outpatient settings) - other things providers can do to improve their processes & technology

If you're trying to improve your patient registration process, provide price transparency to patients, or building patient collections infrastructure, this is for you. Feedback is super welcome

I mean it is going to be so good to watch. you couldn't write a conspiracy theory this good.

I do think that other than for the censorship resistance use case, this was always going to be inevitable for whatever the reserve currency was. It was only a matter of time.

(Also makes me think a gold backed stable is inevitable on some time horizon)

I think on this basis most banks in the us are functionally insolvent.

Not defending SVB - just calling out that the dynamics that make svb insolvent (400bp rate rise in a couple years after a spike in deposits with lots of deployment in fixed income securities) are essentially true for all banks in the us.

What do you mean insurance agent? The process of picking health insurance in the US doesn't utilize agents.

And also because after a plan is selected, copays and deductibles are essentially fixed so consumer would have no need to price shop.

This assumes that the service you're picking costs more than the deductible. If the service you're shopping for costs less than your deductible, you're paying for all of it up front...

Few things

API endpoints that provide clean, abstracted negotiated rates data could be a great infrastructural product for both traditional providers and digital health companies.

Cascade Health (who I've been working with) have this API on the roadmap

Patients that I've interviewed generally want a completely abstracted process - send or upload a picture of their bill and their insurance, and then hand it off. This would be similar to the cushion.ai experience.

Mixed on this. I think a way to select your insurance and know what you'd pay out of pocket, and to compare your out of pocket costs between multiple providers, is SUPER valuable. By the time you have a bill, you already owe money. Before the visit, you actually have a shot at making a decision that costs you less.

Employers on the other hand want to ensure that they aren't being overcharged by their current stack. They are always looking for solutions for reducing costs and better understanding the drivers of those costs, which tools like springbuk.com address.

Cascade is also doing this.

I have less familiarity with the provider side, but the cost of maintaining an insurance billing program has always seemed manual and inefficient.

Have a writeup coming about this one actually. I believe there's room for "Contract Streaming" which allows you to use the published data to a) ingest your contracted rates with every payor and b)know in advance what the out of network rates are for any payor, so you can tell a patient in advance exactly what their visit will cost them before they walk out the door. (There's also a bunch of other benefits around forecasting and stuff, but this is the start).

Oh hell yeah this is coming. I built healthplanexplorer because the files were too unwieldy, but the ultimate consumer format for this is a map like https://carbonhealth.com/flu/flu-vaccination-centers

With 1. A way to choose your plan 2. A way to see all providers in network with that plan 3. A way to see contract rates 4. A way to estimate your out of pocket costs (copay plus deductible) if you go for a specific service

So your point on items covered by insurers is right with the caveat that way more patients are now on high deductible plans, so your out of pocket cost still gets impacted by the contract rates even if the provider is in network.

Agree on electives - there’s something to do there price wise but it’s not the most straightforward.

Re: pricing in general, it def matters in the decision but how you present it makes a huge difference. For uninsured people our flu map has actually been super critical (people are more likely to choose an option with a price at all and marginally more likely to choose a lower priced option (the price spreads are lower bc it’s a simple procedure but there are some places where you can pay over $100 for a flu shot - no one chooses those once they know)

The nit here is you have to give a person the ability to a) select their insurance, and b) show them the full out of pocket cost (copay + deductible) and then it makes a difference, which favors a logged in experience (like solv or Zocdoc) over a logged out experience. But I’m convinced that the reason it’s hard to see today is not because people don’t care about price. It’s because they don’t get to price discriminate at all.

Thanks for this color. I have a ton of thoughts about this. . . A few:

1. The best way I think we can enable patients/consumers to price discriminate is about pushing pricing into the moment when they're making a decision. An example of how to do this is: https://carbonhealth.com/flu/flu-vaccination-centers . .. we created a map, that indexes well, for where to find the lowest cost flu shot (this was done before the price transparency data was available, but I fully intend to a) incorporate the price transparency data for our existing maps and b) create new health maps for basically every service that tells you the relative rate for your plan

2. There's going to be real demand for an API that returns pricing data, for marketplaces that aggregate patients (like Solv, Zocdoc, Sesamecare, healthgrades etc) because pricing is probably the most in-demand decision driver that no one has.

3. Ultimately, I expect Google and Apple to incorporate these prices into maps. Then you'll see it have a real impact on consumer behavior, because most healthcare journeys (whether we like it or not) start with a search.

While I think you should make pricing available for everything (bc after all, there is a price for everything) I think it's most effective to start with diagnostics (mammograms, xrays, STD tests etc) because there's pretty low variance in outcomes (ie it kinda doesn't matter where you get them, you're getting the same thing). When it comes to complex therapeutic searches (eg oncology, chronic care) while pricing is one dimension, patients probably want to see pricing along with a proxy for quality (eg that specialists quality metrics, number of times the MD has done that procedure, etc), bc the healing process for those are not linearly related to price, and the cost of a visit is just a fraction of going down the wrong therapeutic pathway, for both the patient and the system.

For anyone interested in exploring the data yourself, here are a few tools

https://dadroit.com/: desktop tool for processing large JSON files.There’s a free version so you can get pretty far with it if you’re patient

https://www.dolthub.com/repositories/dolthub/quest: they’re running a bounty program for some healthcare providers to process the machine readable files, and have some useful code snippets in case you’re a little bit technical

ChatGPT (https://chat.openai.com/): I know it sounds weird, but this helped adapt some simple python scripts when I got stuck

https://cascadehealth.ai/: if you’re doing this at scale, they can help you

https://www.healthplanexplorer.com/: I built this with some collaborators over the last couple of weeks to help process the files more quickly into formats useful for me. Costs a bit to pay for the box. If you have feedback, I’d love to hear it.

Prior to the regulatory actions aimed at banks that underwrite startup fintech companies over the last few years (Column, Radius, Blue Ridge etc) I didn't think startups would have to care about this, but they do. This piece covers bank portability: - who needs it (startups issuing financial instruments) - when to get it (when you're scaling) - how to prep for it (get a bin, routing number, and abstracted ledger)

I think FedNow impact on debit will be missed. Cost and speed are only 2 parts of the problem to solve. The debit card instrument is still a materially better interface/experience than the account + routing number instrument; people have a debit card on them most of the time, you can swipe it in places etc. Without changing the UX of fednow, hard to imagine it competes.

I think fednow probably cannibalizes a bunch of ACH (because its same UX but faster) and a bunch of wires (bc its the same speed but cheaper) but less debit.

Couple points of feedback I'm interested in for this essay

1. Add card to autofill (feels so obvious, not sure why no one's done it): https://kunle.app/checkouttarget.html#/creditCard/4242424242...

2. Using Web3 models of authentication for credential exchange (I feel like this is simpler than typing in a card because every financial institution has a mobile app at this point? What am I missing)

3. Using a well known URL for credential exchange (similar to the well known URL scheme being proposed for password resets: https://w3c.github.io/webappsec-change-password-url/)

"I was still under the false belief that all varieties of law enforcement are designed to protect the public from harm. It was a sign of my privilege, and of my naive faith in the system."

Systems are designed first, to benefit their creators, and subsequently their controllers, and then everyone else. Unless you designed the system, you should assume it's not designed to benefit you by default.