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

HTTP return preference support #304

Open
andy-a-o opened this issue Nov 29, 2020 · 0 comments
Open

HTTP return preference support #304

andy-a-o opened this issue Nov 29, 2020 · 0 comments

Comments

@andy-a-o
Copy link
Contributor

Is your feature request related to a problem? Please describe.
https://www.hl7.org/fhir/STU3/http.html#2.21.0.5.2

These interactions are performed using POST, PUT or PATCH, and it may be appropriate for a server to return either only a status code, or also return the entire resource that is the outcome of the create or update (which may be different to that provided by the client). In the case of transactions this means returning a Bundle with just the Bundle.entry.response populated for each entry, and not the Bundle.entry.resource values.

The client can indicate whether the entire resource is returned using the HTTP return preference :

Prefer: return=minimal
Prefer: return=representation
Prefer: return=OperationOutcome

Describe the solution you'd like
Prefer header support implemented as in the spec.

Failed tests
TransactionAndBatchTest (XFER5)

andy-a-o added a commit to incendilabs/plan_executor-archive that referenced this issue Nov 30, 2020
andy-a-o added a commit to incendilabs/plan_executor-archive that referenced this issue Nov 30, 2020
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

1 participant