Stream: implementers
Topic: Paging Operation responses
Cooper Thompson (May 03 2017 at 14:45):
Is there a suggested way to page Operation responses (I'm looking more for guidance/ideas than for a spec answer, since I don't think there is anything in the spec)? My current thought is to have the Operation include an out parameter that is the "next-archive" pointer (from RFC 5005 Archived Feeds).
The specific use case is Provider Directory. We are currently thinking of an Operation to pull down the directory. However there are a few components of the directry:
1. A parameter containing a Bundle (type=collection) of Endpoint/Organization/Practitioner/PractitionerRole/etc.
2. A parameter containing "metadata" about the directory. TBD on the structure of that.
I don't think the normal Bundle paging approach would work well because you want to page the entire set of parameters, not just the bundle parameter.
An alternative is to just have the Operation return a Bundle at the top (i.e. no Parameters/parameter), and find a way to fit the metadata inside the bundle. I'm open to ideas/opinions on approach.
Grahame Grieve (May 04 2017 at 00:31):
I'm not following why this isn't just a paged search
Brian Postlethwaite (Jun 05 2017 at 10:44):
The standard bundle paging should be fine. Its just to keep getting the next data, it's not for a single type.
So the operation should return a bundle.
It's not a search, as there are multiple resource types, and could also include deletes (I would hope - not sure if you've documented that @Cooper Thompson got the sample operationdefinition somewhere?)
Grahame Grieve (Jun 07 2017 at 01:26):
still not understanding why it's not a search - you can search across multiple resources
Last updated: Apr 12 2022 at 19:14 UTC
