FHIR Chat · Pagination in bundles · implementers

Stream: implementers

Topic: Pagination in bundles


view this post on Zulip Jaime Olivares (Aug 17 2018 at 20:24):

Whenever we receive a bundle, there is usually first, previous, next and last urls for navigating (as explained here: https://www.hl7.org/fhir/http.html#paging ).
Each server implementation have their own additional query parameters to indicate the pagination like page, _skip or _getpagesoffset.
Are there plans to have a standard way to do this? If we have _count we should have this one as well.

view this post on Zulip Grahame Grieve (Aug 17 2018 at 20:28):

no we have declined to standardise this because servers approach this so differently.

view this post on Zulip Jaime Olivares (Aug 17 2018 at 20:34):

I really want to understand the rationale here: this is a standard defining a REST API. How it can depend on particular servers' approaches? If the standard norms to use _skip or _page then all implements MUST follow it. Just as all the other "underscore" search parameters.

Anyway, let's say the pagination urls are opaque or at least semi-opaque. At least it should be stated to use pagination directives with underscore, for not confusing with regular search parameters. Does it make sense?

view this post on Zulip Grahame Grieve (Aug 17 2018 at 20:46):

why would that make sense? at what point would it matter?

view this post on Zulip Lloyd McKenzie (Aug 17 2018 at 20:47):

Some architectures may find it very easy to skip to page 57 of 300. Others might find that very challenging. The functionality that's standardized is what we believe all servers, regardless of persistence architecture, can manage.


Last updated: Apr 12 2022 at 19:14 UTC