Operation-resource-validate.json

Operation Definition

{
  "resourceType": "OperationDefinition",
  "id": "Resource-validate",
  "text": {
    "status": "generated",
    "div": "<div>!-- Snipped for Brevity --></div>"
  },
  "url": "http://hl7.org/fhir/OperationDefinition/Resource-validate",
  "name": "Validate a resource",
  "publisher": "HL7 (FHIR Project)",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://hl7.org/fhir"
        },
        {
          "system": "email",
          "value": "fhir@lists.hl7.org"
        }
      ]
    }
  ],
  "description": "The validate interaction checks whether the attached content would be acceptable either generally, or as a create, or an update or delete to an existing resource.\n\nThe action the server takes depends on the mode parameter:\n\n* [missing]: The server checks the content of the resource against any schema, constraint rules, and other general terminology rules\n* create: The server checks the content, and then checks that the content would be acceptable as a create (e.g. that the content would not validate any uniqueness constraints)\n* update: The server checks the content, and then checks that it would accept it as an update against the nominated specific resource (e.g. that there are no changes to immutable fields the server does not allow to change, and checking version integrity if appropriate)\n* delete: The server ignores the content, and checks that the nominated resource is allowed to be deleted (e.g. checking referential integrity rules)\n\nModes update and delete can only be used when the operation is invoked at the resource level. \n\nThe return from this operation is an OperationOutcome",
  "status": "draft",
  "date": "2015-04-03T14:24:32+11:00",
  "kind": "operation",
  "code": "validate",
  "notes": "This operation may be used during design and development to validate application design. It can also be used at run-time. One possible use might be that a client asks the server whether a proposed update is valid as the user is editing a dialog, and displays an updated error to the user. The operation can be used as part of a light-weight two phase commit protocol but there is no expectation that the server will hold the content of the resource after this operation is used, or that the server guarantees to succesfully perform an actual create, update or delete after the validation operation completes.",
  "system": false,
  "type": [
    "Resource"
  ],
  "instance": true,
  "parameter": [
    {
      "name": "resource",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "Must be present unles the mode is \"delete\"",
      "type": "Resource"
    },
    {
      "name": "mode",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "Default is 'no action; (e.g. general validation)",
      "type": "string"
    },
    {
      "name": "profile",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "If this is nominated, then the resource is validated against this specific profile. If a profile is nominated, and the server cannot validate agsinst the nominated profile, it SHALL return an error",
      "type": "uri"
    },
    {
      "name": "return",
      "use": "out",
      "min": 1,
      "max": "1",
      "documentation": "If the operation outcome does not list any errors, and a mode was specified, then this is an indication that the operation would be expected to succeed (excepting for transactional integrity issues, see below)",
      "type": "OperationOutcome"
    }
  ]
}