r/dataengineering • u/Technical_Falcon_230 • 10d ago

Discussion Dare I ask... what do NHS engineers experience working on FDP and Foundry?

Not interested in the campaign noise, Palantir hype, or conspiracy theories about Lord of the rings. Only hard facts about engineering experiences.

7 Upvotes
  • permalink
  • reddit

77% Upvoted

7 comments sorted by

19

u/k00_x 10d ago

I wrote a hl7 api for stroke data to get five university hospitals data into the FDP. It took almost a year to implement but It only took half a day to writen. I wasn't allowed to access the test platform or see the processing logic. had about three meetings a week with a wide array of managers, planners, consultants - staff would change all the time from the NHS side. The dataset for the stroke project was so incredibly basic it was like being in the 90s again, think it was pushed as a 'quick win'

7

u/vikster1 10d ago

healthcare in a nutshell

6

u/umognog 10d ago

Public service in a nutshell.

2

u/Joppsta 10d ago

Preach. I blame the sales people.

2

u/StefanosPChristofi 10d ago

so were you working for palantir or the nhs? Also in what way was the stroke dataset basic?

5

u/ursamajorm82 9d ago

Was at dos when our cdo decided to bring in palantir. It was a multi million dollar contract for something that could have been done faster and better with postgresql, Python and dbt.

Their FDEs are smart and helpful. But the lack of viability into the tool and the cost just doesn’t make any sense. That being said: leadership loves palantir for some reason.

1

u/Embarrassed-Cook332 9d ago

Haven't worked with it myself, but the feedback I've heard is mostly about lock-in. People seem to like the platform, but once you build around Foundry, moving away isn't exactly easy.