Create
Last updated
Was this helpful?
Last updated
Was this helpful?
FHIR API id in POST requests, but Aidbox API respects id inside the request body and creates a resource with a specific id. This decision was made because we didn't find any reasons to ignore it and to make Aidbox API be closer to the SQL INSERT query. As a result, a new response code 409 Conflict appeared.
201
Created
Resource successfully created
400
Bad Request
Resource could not be parsed or fail basic FHIR validation rules
409
Conflict
Resource with such id already exists
422
Unprocessable
The proposed resource violated applicable FHIR profiles or server business rules
Instead of using the If-None-Exist header, Aidbox uses query parameters as in ordinary read operation. This is done to make all conditional operations to look the same (use search query parameters).
No matches: The server performs a create interaction (Aidbox version of create)
One Match: The server returns the found resource and 200 OK
Multiple matches: The server returns a 412 Precondition Failed error indicating the client's criteria were not selective enough
This is one of the most basic interactions which gives an ability to create resources. It uses the POST HTTP method accepting a resource type via path parameters and the resource as a body of the request. A response to this interaction may be one of the following:
201
Created
Resource successfully created
400
Bad Request
Resource could not be parsed or fail basic FHIR validation rules
409
Conflict
Resource with such id already exists
422
Unprocessable
The proposed resource violated applicable FHIR profiles or server business rules
A successful response (2xx) also contains a created resource as a body and additional headers Location, ETag, Last-Modified which contain the full path to a resource (base url, resource type and id of a newly created resource), additionally information about version (vid) and modification time of that resource.
An unsuccessful response (4xx) contains OperationOutcome resource which describes issues the server faced during the creation of this resource.
201 Created422 Unprocessable entityNo matches: The server performs a create interaction
One Match: The server returns the found resource and 200 OK
Multiple matches: The server returns a 412 Precondition Failed error indicating the client's criteria were not selective enough
200 OKCreate a patient if there is no patient with the name Bob.
A patient was not created, an existing patient was returned.
Aidbox REST API doesn't ignoreid and treats it as all other attributes in contrast to FHIR API. Read more about differences .
A more complex way to create a resource (it requires the knowledge of ) but it gives some additional flexibility. If you provide search parameters, create becomes conditional create and works in the following way (depending on the number of search results):