Operation-capabilitystatement2-implements.json

Operation Definition

{
  "resourceType" : "OperationDefinition",
  "id" : "CapabilityStatement2-implements",
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 0
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use"
  }],
  "url" : "http://hl7.org/fhir/OperationDefinition/CapabilityStatement2-implements",
  "version" : "4.4.0",
  "name" : "Test if a server implements a client's required operations",
  "status" : "draft",
  "kind" : "operation",
  "date" : "2020-05-03T08:43:35+10:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "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 its capability statement. The client provides its capability statement inline, or by referring the server to the canonical URL of its capability 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    Technically, this operation is implemented as follows:   \n\n* The server's capability statement must have an entry for each resource in the client's capability statement    \n* The server's resource support must have matching flags for updateCreate, conditionalCreate, conditionalRead, conditionalUpdate, conditionalDelete, searchInclude, searchRevInclude   \n* The server's capability statement must have a matching interaction for each interaction in the client capability statement (whether or not it is on a resource)   \n* The server's capability statement must have a search parameter with matching name and definition for any search parameters in the client capability statement   \n* The server must have an operation definition with a matching reference for any operations in the client capability statement   \n\nIf the capability 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 capability statement doesn't match, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity >= error",
  "resource" : ["CapabilityStatement2"],
  "system" : false,
  "type" : true,
  "instance" : true,
  "parameter" : [{
    "name" : "server",
    "use" : "in",
    "min" : 0,
    "max" : "1",
    "documentation" : "A canonical reference to the server capability statement - use this if the implements is not invoked on an instance (or on the /metadata end-point)",
    "type" : "canonical"
  },
  {
    "name" : "client",
    "use" : "in",
    "min" : 0,
    "max" : "1",
    "documentation" : "A canonical reference to the client capability statement - use this if the implements is not invoked on an instance (or on the /metadata end-point)",
    "type" : "canonical"
  },
  {
    "name" : "resource",
    "use" : "in",
    "min" : 0,
    "max" : "1",
    "documentation" : "The client capability statement, provided inline",
    "type" : "CapabilityStatement2"
  },
  {
    "name" : "return",
    "use" : "out",
    "min" : 1,
    "max" : "1",
    "documentation" : "Outcome of the CapabilityStatement2 test",
    "type" : "OperationOutcome"
  }]
}