Details
-
Change Request
-
Resolution: Persuasive with Modification
-
High
-
FHIR Core (FHIR)
-
R5
-
FHIR Infrastructure
-
Search
-
-
Grahame Grieve/Bryn Rhodes: 12-0-0
-
Clarification
-
Non-compatible
-
R5
Description
The specification is current silent on including a POST-based search request in a transaction. It needs to be explicit in either specifying:
- POST-based search is NOT allowed in a batch; or
- the format for a POST-based search.
One challenge with allowing POST-based search in a batch is that batch operations use the Bundle.entry.resource as the 'body' of the request, but POST-based searches are encoded as x-www-form-urlencoded for consistency between GET and POST.
This could be overcome by specifying that POST-based searches use a Parameters resource with name/value pairs - I would lean towards using only valueString and keeping URL encoding in order to maintain consistency with the rest of search (e.g., special character escaping, modifiers, etc.).
If the preference is that POST-based search is not allowed in batches, documenting that is important for implementers. E.g., if GET-based search is generally not used on an implementation, an implementation may try to fail a batched search with an HTTP 405.
Attachments
Issue Links
- relates to
-
FHIR-36098 Search in Messaging limits functionality
- Published
- mentioned in
-
Page Loading...