I might be missing something here, but it appears the AllergyIntolerance endpoint doesn't support pagination?
The endpoint doesn't support passing a _count parameter and doesn't return a count of the resources returned in the entry either, so that seems like a safe assumption. Confusingly, however, the "link" field returns only one item, which has the relation as "next" (and no "self" link):
[{"relation"=>"next", "url"=>"https://fhir-ehr.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/AllergyIntolerance?patient=4342012&status=active"}]
Given that the url for that link doesn't have the typical "-pageContext" and "-pageDirection" parameters of I might see a paginated response on another endpoint, I'm guessing it's the "self" link, not truly a "next" link?
My big question here is: can I safely assume that when I query the AllergyIntolerance endpoint I'm getting *all* the scoped Allergy Intolerances for the patient, and that there's no potential "next" page/pagination of the records I need to worry about?
Best,
Michael