You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/fhir/overview-of-search.md
-60Lines changed: 0 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,66 +144,6 @@ Note:
144
144
145
145
By default, the FHIR service in Azure Health Data Services is set to lenient handling. This means that the server ignores any unknown or unsupported parameters. If you want to use strict handling, you can include the `Prefer` header and set `handling=strict`.
146
146
147
-
##### _include and _revinclude searches
148
-
149
-
The FHIR service supports search queries using the `_include` and `_revinclude` parameters. These parameters allow for the retrieval of reference resources in the search results.
150
-
151
-
The `_include` search parameter enables the retrieval of a particular clinical resource, and any other resources that it references. When included in the query, the `_include` parameter returns both the specified resource and its referenced resources.
152
-
153
-
The `_revinclude` search parameter allows for the retrieval of a resource along with any other resources that reference it, providing a way to search for resources based on their relationships with other resources. For detailed information on `_include` and `_revinclude` in search parameters, refer to the [FHIR Search Documentation](https://www.hl7.org/fhir/R4/search.html#revinclude).
154
-
155
-
##### Request parameters
156
-
157
-
When executing a search request with the `_include` and `_revinclude` parameter, the following optional parameters can be used to control the count.
158
-
159
-
|**Name**|**Value**|**Description**|
160
-
| -------- | --------- | --------------- |
161
-
|`_count`| Default value: 10, Max value: 1000 | The value represents the number of targeted resources to be retrieved per request. The value can be set up to 1000. When the parameter isn't provided, it's set to 10. |
162
-
|`_includesCount`| Default value: 1000 | The value represents the number of matching resources referenced by target resources to be retrieved per request. |
163
-
164
-
For matched items from `_include` and `_revinclude` searches, a maximum of 1,000 items is included in the response. If the number of matched items exceeds 1,000, a link is provided which allows you to navigate the complete result set.
165
-
166
-
Example:
167
-
168
-
In the following example, a search request for Observations is made for Patient with Identifier 123.
169
-
170
-
```
171
-
GET {{FHIR_URL}}/Observation?subject.identifier=123&_include=Observation:subject&_includesCount=10
172
-
```
173
-
174
-
The response returned contains observation data for Patient 123. The matched resource references are given 10 per page, and a link is provided which contains the $include operation. You can follow the link to move through the result set.
> Queries with wild card *.* for `_revinclude` are limited to 100 matches overall.
206
-
207
147
## Chained & reverse chained searching
208
148
209
149
A [chained search](https://www.hl7.org/fhir/search.html#chaining) allows you to perform fine-targeted queries for resources that have a reference to another resource. For example, if you want to find encounters where the patient’s name is Jane, use:
0 commit comments