Operation-conformance-implements.json

Operation Definition

{
  "resourceType": "OperationDefinition",
  "id": "Conformance-implements",
  "text": {
    "status": "generated",
    "div": "<div>!-- Snipped for Brevity --></div>"
  },
  "url": "http://hl7.org/fhir/OperationDefinition/Conformance-implements",
  "name": "Test if a server implements a client's required operations",
  "status": "draft",
  "kind": "operation",
  "date": "2016-08-11T17:02:54+10:00",
  "publisher": "HL7 (FHIR Project)",
  "contact": [
    {
      "telecom": [
        {
          "system": "other",
          "value": "http://hl7.org/fhir"
        },
        {
          "system": "email",
          "value": "fhir@lists.hl7.org"
        }
      ]
    }
  ],
  "description": "This operation asks the server to check that it implements all the resources, interactions, search parameters, and operations that the client provides in it's conformance statement. The client provides it's conformance statement inline, or by referring the server to the canonical URL of it's conformance statement",
  "code": "implements",
  "comment": "The operation does not perform a full conformance check; in particular it does not check that the profiles align. It merely checks that the behaviors the client wishes to use are provided\n\nTechnically, this operation is implemented as follows:\n * The server's conformance statement must have an entry for each resource in the client's conformance statement \n * The servers' resource support must have matching flags for updateCreate, conditionalCreate, conditionalRead, conditionalUpdate, conditionalDelete, searchInclude, searchRevInclude\n * The server conformance statement must have a matching interaction for each interaction in the client conformance statement (whether or not it is on a resource)\n * The server must have a search parameter with matching name and definition for any search parameters in the client conformance statement\n * The server must have an operation definitions with a matching reference for any operations in the client conformance statement\n\nIf the conformance statements match by these rules, then the return value is a 200 OK with an operation outcome that contains no issues with severity >= error. If the conformance statement doesn't match, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity >= error",
  "system": false,
  "type": [
    "Conformance"
  ],
  "instance": true,
  "parameter": [
    {
      "name": "server",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "The canonical URL for the server conformance statement - use this if the subset is not invoked on an instance (or on the /metadata end-point)",
      "type": "uri"
    },
    {
      "name": "client",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "The canonical URL for the client conformance statement - use this if the subset is not invoked on an instance (or on the /metadata end-point)",
      "type": "uri"
    },
    {
      "name": "resource",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "The client conformance statement, provided inline",
      "type": "Conformance"
    },
    {
      "name": "return",
      "use": "out",
      "min": 1,
      "max": "1",
      "documentation": "Outcome of the conformance test",
      "type": "OperationOutcome"
    },
    {
      "name": "issues",
      "use": "out",
      "min": 1,
      "max": "1",
      "documentation": "Outcome of the conformance test",
      "type": "OperationOutcome"
    },
    {
      "name": "union",
      "use": "out",
      "min": 0,
      "max": "1",
      "documentation": "The intersection of the functionality described by the conformance resources",
      "type": "Bundle"
    },
    {
      "name": "intersection",
      "use": "out",
      "min": 0,
      "max": "1",
      "documentation": "The union of the functionality described by the conformance resources",
      "type": "Bundle"
    }
  ]
}