0xUncleBill Profile Banner
Eitan Bill Profile
Eitan Bill

@0xUncleBill

Followers
140
Following
33
Media
1
Statuses
70

Ethereum core dev & Brazilian Jiu Jitsu

Joined January 2022
Don't wanna be here? Send us removal request.
@0xUncleBill
Eitan Bill
2 months
RT @sigp_io: Lighthouse dev @jimmygchen makes the case for a spec freeze for PeerDAS and lays out a path for mainnet in 2025 🚀.
0
4
0
@0xUncleBill
Eitan Bill
2 months
RT @jih2nn: FOCIL’s technical readiness? FOCIL already interops with half of all clients. More than happy to welcome Lighthouse on board!….
0
3
0
@0xUncleBill
Eitan Bill
2 months
RT @soispoke: FOCIL interop with Lighthouse! . gg @0xUncleBill .
0
1
0
@0xUncleBill
Eitan Bill
4 months
RT @sigp_io: 🚨 New blog post: An exploration of the issues and fixes in the Lighthouse client brought on by the Pectra Holesky incident. W….
0
10
0
@0xUncleBill
Eitan Bill
5 months
RT @sigp_io: Lighthouse Team on Fulu 🧵👇. Fulu is all about PeerDAS (EIP-7594)—the heart of this fork. Given its complexity, let's keep the….
0
21
0
@0xUncleBill
Eitan Bill
6 months
RT @hwwonx: Thank you @sassal0x! 🙏. Pay It Forward - Three underfollowed people: . 1. @fradamt - The Consensus Layer Fork-Choice Great Mas….
0
86
0
@0xUncleBill
Eitan Bill
6 months
RT @TimBeiko: Pectra is going live 🥳. Holesky will fork at slot 3710976 (Mon, Feb 24 at 21:55:12 UTC).Sepolia will fork at slot 7118848 (We….
0
205
0
@0xUncleBill
Eitan Bill
8 months
RT @urkle91: Lebron is 40, this fuckery won't go on for much longer, thank god.
0
10K
0
@0xUncleBill
Eitan Bill
8 months
Private insurance companies will never do this on their own. We must introduce federal mandates that protect patients and doctors, while reducing unnecessary friction in the healthcare industry.
0
0
0
@0xUncleBill
Eitan Bill
8 months
Some ideas I had.1. Financial penalties for erroneous claim denial.2. Publicly available reports about percentage of denied claims, appeals, etc. without revealing individual patient information.3. Common API for insurance companies to share their data with authorized entities.
1
0
0
@0xUncleBill
Eitan Bill
8 months
That alone would save so much time and money. But the incentives aren't there. The regulation aren't there. Insurance companies are operating like its still 1997. Instead of murder we should be DEMANDING the US government to effectively regulate these dogshit insurance companies.
1
0
0
@0xUncleBill
Eitan Bill
8 months
Imagine instead, if these insurance companies were required to provide a fucking API that allowed authorized entities to fetch up to date data. Imagine if the US government required ALL insurance companies to build these API's under a common specification.
1
0
0
@0xUncleBill
Eitan Bill
8 months
My idea was to build web scrappers to automate portions of this process. The web scrappers I built improved their workflow. The problem was web scrapping is the least maintainable piece of software ever, a small change to the websites UI could easily break the scrapper.
1
0
0
@0xUncleBill
Eitan Bill
8 months
I was in absolute shock at how awful this process was and was impressed at how creative these data entry employees were. They were, in my opinion, geniuses at their work. The tricks they found to recognize patterns was absolutely incredible. Of course they were paid minimum wage.
1
0
0
@0xUncleBill
Eitan Bill
8 months
In the first few months of my employment at MedPOINT I learned all about this hellish process. It was my first job out of college and I was tasked with making these peoples job easier.
1
0
0
@0xUncleBill
Eitan Bill
8 months
For example, they filter the data by insurance company, OP code, and effective date. They cross reference a few of these patients against the insurance company website. If a discrepancy is found, it then requires more manual checks to understand what the underlying issue is.
1
0
0
@0xUncleBill
Eitan Bill
8 months
Data entry employees at MedPOINT have come up with extravagant ways to find patterns in these spreadsheets and cross check them against insurance companies web portals. If they were to simply accept the spreadsheet as is, 1000's of patients data would potentially be incorrect.
1
0
0
@0xUncleBill
Eitan Bill
8 months
The crazy part is that the CSV's received from insurance companies are not necessarily the source of the truth. The actual source of truth are insurance companies web portals.
1
0
0
@0xUncleBill
Eitan Bill
8 months
So MedPOINT resorts to receiving CSV's via secure email from 20+ different insurance companies at different cadences. It then hires people to manually enter this data into MedPOINTS HIPAA compliant databases.
1
0
0