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

Allow mediators to update resources with PUT requests #116

Open
witash opened this issue Mar 14, 2024 · 0 comments
Open

Allow mediators to update resources with PUT requests #116

witash opened this issue Mar 14, 2024 · 0 comments
Assignees
Labels
Type: Feature Add something new

Comments

@witash
Copy link
Contributor

witash commented Mar 14, 2024

If a FHIR resource needs to be updated on a remote endpoint, the mediator needs to send a request to the endpoint with method PUT, instead of POST. If POST is used, it will be treated as trying to create a new resource and the request will usually fail due to duplicates.

This requires either the mediator or outbound push to be able to differentiate between a new resource and an existing resource. Note that "existing resource" means existing for the remote endpoint; although it may be possible to assume that an existing resource on the CHT side has already been created on the remote endpoint.

The current mediator implementation only uses POST.
Outbound push from CHT also only uses POST; it does send requests for updates, but these requests have method POST.

Either outbound push needs to send PUT requests for existing resources, assuming they have already been created on the remote, and the mediator needs to support PUT requests.

Or the mediator itself needs a way to tell if a resource is being created or updated

@witash witash added the Type: Feature Add something new label Mar 14, 2024
@Phil-Mwago Phil-Mwago assigned Phil-Mwago and witash and unassigned Phil-Mwago Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Add something new
Projects
Status: Next Week's Commitments
Development

No branches or pull requests

2 participants