Skip to content
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

Support Message-based operations (e.g. $process-message operation) #2655

Closed
ewoutkramer opened this issue Jan 9, 2024 Discussed in #2601 · 2 comments
Closed

Support Message-based operations (e.g. $process-message operation) #2655

ewoutkramer opened this issue Jan 9, 2024 Discussed in #2601 · 2 comments

Comments

@ewoutkramer
Copy link
Member

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:

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?

@LodewijkSioen
Copy link
Contributor

Can I say duplicate of #2605 😉

@ewoutkramer
Copy link
Member Author

Ah, this sneaked in before christmas. I just heared it was an excellent PR ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants