Release 4

Operation-resource-meta-add.xml

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

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

Jump past Narrative

Operation Definition

<?xml version="1.0" encoding="UTF-8"?>

<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="Resource-meta-add"/> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> Add profiles, tags, and security labels to a resource</h2> 
      <p> OPERATION: Add profiles, tags, and security labels to a resource</p> 
      <p> The official URL for this operation definition is: </p> 
      <pre> http://hl7.org/fhir/OperationDefinition/Resource-meta-add</pre> 
      <div> 
        <p> This operation takes a meta, and adds the profiles, tags, and security labels found in
           it to the nominated resource</p> 

      </div> 
      <p> URL: [base]/Resource/[id]/$meta-add</p> 
      <p> Parameters</p> 
      <table class="grid">
        <tr> 
          <td> 
            <b> Use</b> 
          </td> 
          <td> 
            <b> Name</b> 
          </td> 
          <td> 
            <b> Cardinality</b> 
          </td> 
          <td> 
            <b> Type</b> 
          </td> 
          <td> 
            <b> Binding</b> 
          </td> 
          <td> 
            <b> Documentation</b> 
          </td> 
        </tr> 
        <tr> 
          <td> IN</td> 
          <td> meta</td> 
          <td> 1..1</td> 
          <td> 
            <a href="resource.html#Meta">Meta</a> 
          </td> 
          <td/>  
          <td> 
            <div> 
              <p> Profiles, tags, and security labels to add to the existing resource. Note that profiles,
                 tags, and security labels are sets, and duplicates are not created.  The identity of a
                 tag or security label is the system+code. When matching existing tags during adding, version
                 and display are ignored. For profiles, matching is based on the full URL</p> 

            </div> 
          </td> 
        </tr> 
        <tr> 
          <td> OUT</td> 
          <td> return</td> 
          <td> 1..1</td> 
          <td> 
            <a href="resource.html#Meta">Meta</a> 
          </td> 
          <td/>  
          <td> 
            <div> 
              <p> Resulting meta for the resource</p> 

            </div> 
          </td> 
        </tr> 
      </table> 
      <div/>  
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="3"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/> 
  </extension> 
  <url value="http://hl7.org/fhir/OperationDefinition/Resource-meta-add"/> 
  <version value="4.2.0"/> 
  <name value="Add profiles, tags, and security labels to a resource"/> 
  <status value="draft"/> 
  <kind value="operation"/> 
  <date value="2020-03-26T16:39:19+00:00"/> 
  <publisher value="HL7 (FHIR Project)"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="This operation takes a meta, and adds the profiles, tags, and security labels found in
   it to the nominated resource"/> 
  <code value="meta-add"/> 
  <resource value="Resource"/> 
  <system value="false"/> 
  <type value="false"/> 
  <instance value="true"/> 
  <parameter> 
    <name value="meta"/> 
    <use value="in"/> 
    <min value="1"/> 
    <max value="1"/> 
    <documentation value="Profiles, tags, and security labels to add to the existing resource. Note that profiles,
     tags, and security labels are sets, and duplicates are not created.  The identity of a
     tag or security label is the system+code. When matching existing tags during adding, version
     and display are ignored. For profiles, matching is based on the full URL"/> 
    <type value="Meta"/> 
  </parameter> 
  <parameter> 
    <name value="return"/> 
    <use value="out"/> 
    <min value="1"/> 
    <max value="1"/> 
    <documentation value="Resulting meta for the resource"/> 
    <type value="Meta"/> 
  </parameter> 
</OperationDefinition> 

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.