Aidbox doesn't have an atomic update yet. It also allows omitting id in the resource body.
Response code
Text
Description
200
OK
Resource successfully updated
201
Created
Resource successfully created
422
Unprocessable Entity
The proposed resource violated applicable FHIR profiles or server business rules
Conditional Update
PUT [base]/[type]?[search parameters]
In contrast to FHIR, Aidbox conditional update allows creating a resource with a specific id. In case of one match, conditional update ignores the id coming in the request body. That means that resource id can't be changed by any update operation.
No matches: The server performs a create interaction (Aidbox version of create)
One Match: The server performs the update against the matching resource
Multiple matches: The server returns a 412 Precondition Failed error indicating the client's criteria were not selective enough
Versioned Update
While you update, there is a risk of overriding the latest changes done by another operation. To escape this situation, you can use a versioned update by sending with update If-Match header with versionId of resource you want to update. If the server has the same version of resources, the update will be successful. If versions do not match, you will get OperationOutcome with conflict code.
Example
Let say we created a patient:
create-patient-request
POST /fhir/Patient
id: pt-1
name: [{family: 'Wrong'}]
create-patient-request
POST /Patient
id: pt-1
name: [{family: 'Wrong'}]
If a patient with the name Julie already exists, update interaction will be performed and id will be ignored.
Update
PUT [base]/[type]/[id]
This interaction allows modifying an existing resource (creating a new version of it). After performing this interaction, the resource will be replaced with a new version of the resource provided in the body of the request. id of a resource can't be changed (at least cause of versioning) and id in the body of the resource is ignored in update interaction (in order to make a conditional update possible without knowing the logical id of the resource). If a resource with id (provided in the url) doesn't exist, a new resource will be created. Following codes can be returned by the server:
Response code
Text
Description
200
OK
Resource successfully updated
201
Created
Resource successfully created
422
Unprocessable Entity
The proposed resource violated applicable FHIR profiles or server business rules
200 OK
Update a patient by a given id:
PUT /fhir/Patient/17b69d79-3d9b-45f8-af79-75f958502763
name: [{given: ["Bob"]}]
PUT /Patient/17b69d79-3d9b-45f8-af79-75f958502763
name: [{given: ["Bob"]}]
This is a more complex way to update a resource, but it gives more power. You can update a resource without knowing the id , but it requires the knowledge of . Different response codes will be returned (based on the number of search results):
