FHIR Server Read Optimization

[dubdabasoduba]

Three strategies: 1) HTTP Caching 2) DB Indexing 3) Memoization

• Business requirements 1: -- The ability to optimize the User and sync strategy identification on the server for every request. The proposed solution is highlighted below. This is a result of Implementing API RBAC (Role Based Access Control) & Remote Sync ( from the server) for FHIR Core -- Data Access Filter

Optimizing the app and app sync strategy

• We would save the Application ID & Sync Strategy on Redis for easier identification.
• We should only save one entry per Application ID. The Redis key would be the Application ID and the value would be the sync strategy
  e.g

key	Value
ecbis-saa	Location

• We would try to fetch the sync strategy from Redis first before performing the search on the Composition resource.

• The Redis cache can be cleared after every 1 - 2 hours. We can make this configurable.

• Business requirements 2: -- To allow for fast access of the server response in case it hasn't changed from the last request.