Searching should provide method to ensure consistent sort order

When performing the same FHIR search request multiple times, the order of the search results should be consistent across requests.

ie, for example, if you are searching for encounters and sorting by date and two encounters have the exact same encounter date time, although there's nothing specific in the query to determine with encounter should be sorted first in this case, the same encounter should be sorted first on multiple queries.

Perhaps the best way to do this would be to add at the end of any specified sort chain to then sort by uuid.

ibacher  thoughts?  Perhaps this has already been accounted for in some way I'm missing?  (But it does seem to be happening... in the Dispensing app I noticed jumping/switching of ordering when the SWR refreshed the data behind the scenes, and I confirmed that the order appears to be inconsistent when testing the query via Postman)

fyi mseaton