FHIR Chat · CapabilityStatement: recurse searchInclude? · implementers

Stream: implementers

Topic: CapabilityStatement: recurse searchInclude?

Jorn Duwel (Feb 16 2022 at 11:17):

Hi. In a CapabilityStatement, can recursive searchIncludes that we require to be supported, but that belong to a resource that we do not require any other interaction with, be placed in the .resource of the resourceType that we would like to be supported?

For example, when we require the query GET [base]/CarePlan?_include=CarePlan:activity-reference:DeviceRequest&_include:recurse=DeviceRequest:device to be supported, is:

<resource>
   <type value="CarePlan"/>
   <interaction>
      <code value="search-type"/>
   </interaction>
   <searchInclude value="CarePlan:activity-reference:DeviceRequest"/>
   <searchInclude value="DeviceRequest:device"/>
</resource>

allowed if we do not require any other interaction with DeviceRequest?

Or do we need to specificy DeviceRequest in its own resource, like:

<resource>
   <type value="CarePlan"/>
   <interaction>
      <code value="search-type"/>
   </interaction>
   <searchInclude value="CarePlan:activity-reference:DeviceRequest"/>
</resource>
<resource>
   <type value="DeviceRequest"/>
   <interaction>
      <code value="???"/>
   </interaction>
   <searchInclude value="DeviceRequest:device"/>
</resource>

where I wouldn't know what to fill in resource.interaction.code, but it is required. Or is the recursive include in itself enough to state that we do require some sort of 'search-type' on the DeviceRequest resource?

Lloyd McKenzie (Feb 16 2022 at 19:56):

This seems like something that should be clarified in the spec. Can you submit a change request?

Jorn Duwel (Feb 17 2022 at 19:29):

https://jira.hl7.org/browse/FHIR-36051

Last updated: Apr 12 2022 at 19:14 UTC