Best API for Replacing TRUD CSV Downloads – DSE or FHIR?

As we prepare for the deprecation of the ODS ORD TRUD packs this September, I’m evaluating the best approach for replacing our current setup.

Our workflow involves downloading selected CSV reports and loading them into our internal database. Given this, I’m wondering whether it would be more appropriate to use the DSE API rather than the ODS FHIR API.

While I’m comfortable developing against either API, my understanding is that the FHIR API is primarily designed for real-time healthcare software integrations, which doesn’t align with our use case. The DSE API, on the other hand, seems to replicate the functionality of the TRUD packs more closely and supports automated CSV downloads.

Would appreciate any thoughts or recommendations from others who’ve faced similar decisions.

Thanks

1 Like

I wasn’t aware of that realtime focus.

I’ve gone for periodic ODS CSV downloads and then loaded them into an off the shelf FHIR repo (for real time use) - we also include practitioner downloads and link them to organisations.

1 Like

Thanks Kevin. I have just gone ahead to develop a process that does the periodic ODS csv download. However, there is still a worry about the unavailability of the gridall csv in the DSE API.