Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was in the physical therapy space for over 15 years. The penny pinching that comes from healthcare giants towards their software vendors are dreadful. It prevents any serious software engineering from happening. One customer billed over a billion dollars in a year to Medicare through our software and paid us $1M that year. I'm still not certain that we didn't take a loss to take that client.

Passing around financial data on SFTP drops is something that irked me. Having the total not add up from the line items is also pretty ridiculous. The systems in place are all about edge cases that have formed over decades.

Software engineers are not invited to the discussions in a lot of these companies. The area is gate kept by healthcare people, which tend to be people who don't know how to do technical writing or planning.

Our company wasn't a huge one. But the huge ones looked to me as run by accountants. If you can't establish an income stream for them, they won't even talk to you.



> Passing around financial data on SFTP drops is something that irked me.

I see this a moderate amount in fintech, or perhaps at least older fintech?

Had a colleague tell me about a new financial info provider he was supposed to connect with for data. "Oh this one will be easy" he was told. "They use oauth". OK... well... you oauth in, then you hit an endpoint that triggers a data build which then puts your data file in to an FTP account of your configuration. But you can't even configure it via hitting the endpoint behind the oauth. You have to log in to a web app to configure the FTP account for your account.

You hit the API endpoint and get 'OK'. But... that's it. You might get a file in your FTP account 5 minutes later. Or an hour later. It's just whenever it gets processed on their end. And... if it doesn't show up - you have no indication whether something broke, or perhaps the data service "just doesn't have any data for you today - you can't expect data every single day".

It's insanely crazy how across-the-board poor so many of these mid-level data vendors are. Colleague is currently supporting 8 different integration ingests like this - some deliver FTP daily, some you have to pull down, etc.

One delivers data which is only ever a delta. You have to continually request previous daily info from them to get to the 'first record' for that account, which can sometimes go back years, but... you don't know that up front. So you have to loop and request "day before", pull down data, parse it, then check the day before, until you don't get anything for that customer, then presume the previous was "initial balance". But you also can't just do that once, because... there may not have been any data the day before because... holiday? system down? So in practice you need to go back 3-4 days at least to verify. Oh... and don't keep looping and requesting too fast... you'll exceed the low rate limit ("we don't want people abusing our API").

I can only barely imagine how systems evolve like this, because they don't really seem to serve anyone's interest fully.


No, I also see this in InsurTech. These companies are so deathly afraid of data breaches and system compromises that anything remotely modern frightens them...sadly.

And btw, that description given by your colleague brought cringy mental flashbacks on meetings I've recently attended.


I had a client medical clinic that had to use encrypted files on FTP. their old version of SunOS they ran on did not support SFTP or ssh. This was in 2017.

I also worked with a state medicaid office. They refused to use DNS, they decided it was insecure. Which was lots of fun any time we changed datacenters (3 times over my 7 years there). They would also go down, and nothing would happen until around 9:30-10am the following work day when they would finally come around and fix it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: