Stream: implementers
Topic: Implementing paging..
Richard Kavanagh (Nov 30 2017 at 16:57):
We have been looking at how to implement paging through search bundles in STU3 and it's proving hard to understand what the FHIR says about this. We've looked at a few of the public test servers and they seem quite inconsistent.
http://test.fhir.org/r3/Patient
http://sqlonfhir-stu3.azurewebsites.net/fhir/Patient
http://wildfhir.aegis.net/fhir1-8-0/Patient
http://fhirtest.uhn.ca/baseDstu3/Patient
They all seem to support the self, first, next & last links (not 100% consistently but close enough).
However, across the servers, there are mixed ways of doing paging involving the use of the following query constructs
&page=xx
&_page=xx
&search-offset=xx
&_getpagesoffse=xx
So, two questions;
1) How should paging be performed?
2) Where is this described in the spec?
thanks
Richard Ettema (Nov 30 2017 at 17:04):
Richard, paging support is described here http://hl7.org/fhir/http.html#paging. The RFC 5005 spec uses the &page=xx format which is what I followed for wildfhir.
Lloyd McKenzie (Nov 30 2017 at 20:48):
There's no constraints on what the links look like. They could use page numbers, record numbers, GUIDs or anything else. All an implementer can count on is the links will do what they say they'll do. You can't count on being able to parse them.
Grahame Grieve (Nov 30 2017 at 21:15):
"The client must use the server supplied links in order to traverse the pages" - only the server needs to understand the links
Richard Kavanagh (Nov 30 2017 at 22:06):
Ah I see - thanks..
Last updated: Apr 12 2022 at 19:14 UTC
