Release 5 Draft Ballot

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions


FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

Raw JSON (canonical form + also see JSON Format Specification)

Operation Definition

  "resourceType" : "OperationDefinition",
  "id" : "Resource-meta",
  "text" : {
    "status" : "extensions",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  "extension" : [{
    "url" : "",
    "valueInteger" : 3
    "url" : "",
    "valueCode" : "trial-use"
  "url" : "",
  "version" : "4.6.0",
  "name" : "meta",
  "title" : "Access a list of profiles, tags, and security labels",
  "status" : "draft",
  "kind" : "operation",
  "date" : "2022-07-01T20:18:23+00:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : ""
      "system" : "email",
      "value" : ""
  "description" : "This operation retrieves a summary of the profiles, tags, and security labels for the given scope; e.g. for each scope:  \n\n* system-wide: a list of all profiles, tags and security labels in use by the system \n* resource-type level: A list of all profiles, tags, and security labels for the resource type \n* individual resource level: A list of all profiles, tags, and security labels for the current version of the resource.  Also, as a special case, this operation (and other meta operations) can be performed on a historical version of a resource)",
  "affectsState" : false,
  "code" : "meta",
  "comment" : "At the system and type levels, the $meta operation is used to get a summary of all the labels that are in use across the system. The principal use for this operation is to support search e.g. what tags can be searched for. At these levels, the meta will not contain versionId, lastUpdated etc. Systems are not obligated to implement the operation at this level (and should return a 4xx error if they don't). At the resource and historical entry level, the $meta operation returns the same meta as would be returned by accessing the resource directly. This can be used to allow a system to get access to the meta-information for the resource without accessing the resource itself, e.g. for security reasons",
  "resource" : ["Resource"],
  "system" : true,
  "type" : true,
  "instance" : true,
  "parameter" : [{
    "name" : "return",
    "use" : "out",
    "min" : 1,
    "max" : "1",
    "documentation" : "The meta returned by the operation",
    "type" : "Meta"

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.