Medplum is the fasted way to build high quality, scalable and compliant healthcare applications

medplum

Is it possible that fetching resource pages could be volatile?

Hi <@1083764540237422642> - could you define volatile in this context?

returning a duplicate resource in a later bundle

<@1083764540237422642> Yes, if data us updated while iterating through pages, we could see duplicate data appear later in the search. 

We actually have a pretty in-depth discussion of the tradeoffs of implementing keyset pagination here: https://github.com/medplum/medplum/discussions/1231

Using the `Connection` api for graphQL (defined by the FHIR spec) , you can mitigate some, but not all of these issues. I'd refer you to the discussion for more information about the tradeoffs

Hey <@963922231224844359> I just mean using the count and offset params

seems like duplicates appear if you're not using a sort param

I see. yes, a basic search doesn't guarantee a sort order, so you may get a different ordering between calls