Lee Surprenant

I believe conditional update is implemented as according to https://www.hl7.org/fhir/http.html#cond-update (and I think it should work from a bundle). In your sample request, you have: ``` "request": { "method": "PUT",...

I wonder if we could/should add a warning to the output when a user sets one of these Bundle.entry.request fields (`ifNoneMatch`, `ifModifiedSince`, `ifMatch`, or `ifNoneExist`) on a request method that...

> I wonder if we could/should add a warning to the output when a user sets one of these Bundle.entry.request fields (ifNoneMatch, ifModifiedSince, ifMatch, or ifNoneExist) on a request method...

https://linuxforhealth.github.io/FHIR/Conformance/#http-headers does link to https://hl7.org/fhir/R4B/http.html#summary which lists various headers. Its somewhat typical for us to document our deviations from the specification without repeating all of the information in the spec....

QA tip: might be able to change the time on the system to force this one

> Introduce a fhir-server-config property that controls the server behavior when no fhirVersion is specified by the client. The default value for this property should result in the server only...

an edge case for this one might be a conditional create/update/delete where the search resolves to the same resource

team decision: lets do this one JUST FOR TRANSACTION (and leave batch processing alone)

I've taken a closer look at this one and unfortunately its quite tricky. The current Patient/Group export works something like this: 1. fhir-operation-bulkdata takes the incoming request, computes the set...

As a workaround, you can use our system-level export to export all instances of a given resource type and then perform client-side processing.