samply
Implement Acquiring SNOMED CT Release Files via MLDS API
Doing so would remove the need to download the release files manually and mount them for use at startup.
However, we would need some way to store the data downloaded once. Blaze currently reads the release files on every start. Blaze doesn't have its own way to store SNOMED CT. There are no durable indices. Everything is build in memory on each start. As we can't depend on downloading the release files on every start, we have to at least provide a storage for them.
As a non-technical user, I can't help but feel curious. From a software architecture perspective, is it possible to mimic how Hermes handles and stores SNOMED-CT? The developer also created a wrapper with HAPI to enable the service as FHIR-ready. To my understanding, Hermes stores and indexes SNOMED-CT locally, which is then loaded to a FHIR server.
