As a victim of claude derangement syndrome, hard to imagine working without these.
5,501 karma · joined March 3, 2011
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 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)
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.
Are you insured through your employer or via an exchange?
> 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...
> 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).
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
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.
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.
Cascadehealth.ai and serifhealth.com are as well.
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.
"On Nov. 10, Mr. Ardoino had already expressed concerns that Alameda was trying to push down the price of tether and drag other cryptocurrencies with it, according to one of the people. "
https://www.wsj.com/articles/rivals-worried-sam-bankman-frie...
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.
I don't even care for peanut butter and this just hits. Super smooth, not too sweet - i eat it by the spoonful. I literally did not think there was any difference between different peanut butter brands until I had Pic's.
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/)
> 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.