2.26.6.2 获取资源元数据的操作（$meta）

工作组:FHIR Infrastructure

成熟度: 3

试用

隔间: N/A

此操作用于获取指定范围的配置、标签和安全信息的摘要：

• 系统范围：系统使用的所有配置、标签和安全信息的列表
• 资源类型层级：资源类型的所有配置、标签和安全信息的列表
• 单个资源实例级别：资源实例当前版本的所有配置、标签和安全信息的列表。 此外，作为特殊情况，此操作（和其他获取资源元数据的操作）可以在资源的历史版本上执行。

此操作的官方定义URL是

 http://hl7.org/fhir/OperationDefinition/Resource-meta

此 正式定义 是一个 操作定义资源（OperationDefinition）

URL: [base]/$meta

URL: [base]/[Resource]/$meta

URL: [base]/[Resource]/[id]/$meta

这是一个等幂等操作

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

2.26.6.2.1 Examples

Request: Get all the tags, profiles, and security labels used on patient resources

GET /fhir/Patient/$meta

Response: All the tags, profiles, and security labels used on patient resources

HTTP/1.1 200 OK
[other headers]

<Parameters xmlns="http://hl7.org/fhir">
  <parameter>
    <name value="return"/>
    <valueMeta>
      <profile value="http://hl7.org/fhir/StructureDefinition/daf-patient"/>
      <profile value="http://hl7.org/fhir/StructureDefinition/uslab-patient"/>
      <security>
        <system value="http://hl7.org/fhir/v3/ActCode"/>
        <code value="EMP"/>
        <display value="employee information sensitivity"/>
      </security>
      <tag>
        <system value="http://example.org/codes/tags"/>
        <code value="current"/>
        <display value="Current Inpatient"/>
      </tag>
    </valueMeta>
  </parameter>
</Parameters>

For more information about operations, including how they are invoked, see Operations.