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
Originally posted by LodewijkSioen October 4, 2023
We're working with FHIR messaging. For this we opted to use the $process-message operation. This line in the specifications is giving me headaches:
This operation does not use the parameters resource; the parameters "async" and "response-url" always go in the URL, if they are used, and the "content" parameter is always the body of the HTTP message.
I don't think it is possible to do this with the FhirClient. All the operation-based functions take a Parameter object and post it to the server.
Is this something that is missing on the SDK?
The text was updated successfully, but these errors were encountered:
Discussed in #2601
Originally posted by LodewijkSioen October 4, 2023
We're working with FHIR messaging. For this we opted to use the $process-message operation. This line in the specifications is giving me headaches:
I don't think it is possible to do this with the FhirClient. All the
operation
-based functions take aParameter
object and post it to the server.Is this something that is missing on the SDK?
The text was updated successfully, but these errors were encountered: