New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pick up the latest dstu2 changes to _include #240

wdebeau1 opened this Issue Oct 6, 2015 · 2 comments


None yet
3 participants

wdebeau1 commented Oct 6, 2015

As far as I can tell, what used to be*
should now be*

My reading of the spec is that the :recurse shouldn't be required, but HealthIntersections at least requires it.


This comment has been minimized.


jamesagnew commented Oct 6, 2015

Hi Bill,
Recursion used to be unspecified- you'd do _include=foo and the server got to choose whether or not to recurse. As of DSTU2 at search would be non-recursive and you would specify _include:recurse=foo if you wanted it to recurse.

Hapi should support both- is that not working for you? This sounds like maybe an issue needs to be filed against HealthIntersections Server :)


This comment has been minimized.

jportner commented Nov 20, 2015

Since this falls under the same topic, I'm replying to this thread rather than open a new issue...

The spec outlines three parameters for _include, each separated by a ":" character...

  1. The name of the source resource from which the join comes
  2. The name of the search parameter which must be of type reference
  3. (Optional) A specific of type of target resource (for when the search parameter refers to multiple possible target types)

HAPI only appears to support the first two parameters.
Support for the third (optional) parameter would be excellent.
E.g. GET /baseDstu2/CarePlan?_include=CarePlan:activityreference:Goal would only include activityreference resources that are of the Goal type.

jamesagnew added a commit that referenced this issue Dec 14, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment