Ok. You are suggesting a CacheKey = patient.100. After the client submits and patient data was updated, patient.100 would be a global cache variable. Update the cache after database update. This appears as a better approach than what I visualized, which was delete all keys associated as patient.100.%.
Yes, the collection of patients was brought to my attention after your response and now I feel like Peter and the window blinds.
Updated Medium response after 30 minutes of pondering about cache: I’ve decided to not update the cache record in a list based on my current design. I will clear all keys that are associated with the patient.100. Memory can be volatile. As of now, my interface looks like this: