The tool introduced by FHIR to provide a separate validation mechanism for 2-steps commit workflow or for development needs. It works for create, update and delete operations, is called using
?mode= query parameter with values
delete but changes won't be committed, instead a requester will get an
OperationOutcome with information about validation results. See http://hl7.org/fhir/resource-operation-validate.html for the official documentation.
POST [base]/[type]/$validatePOST [base]/[type]/[id]/$validate
Such requests check resource structure, internal business rules and return a list of problems if some exist.
200 OK — those requests always return status 200
Success and failure of a validation request is determined by
validationfail are self-descriptive.
Request contains valid
Patient resource inside the body.
POST /Patient/$validate?mode=createname: 
id: allokresourceType: OperationOutcome
Patient name must be an array,
test is a non-existing field.
POST /Patient/example/$validate?mode=updatename: "Bob"test: value
id: validationfailresourceType: OperationOutcomeerrors:- path: [name]message: expected array- path: [test]message: extra propertywarnings: