Others titles

  • FHIR Meta Datatype
  • Electronic Health Records Exchange Through FHIR


  • FHIR
  • HL7
  • Medical Terminology
  • Processes Data
  • Processes Information
  • Processes Documentation
  • Health Information Exchange
  • Electronic Health Records
  • FHIR Smart
  • Smart on FHIR


Each resource contains an element “meta”, of type “Meta”, which is a set of metadata that provides technical and workflow context to the resource. The metadata items are all optional, though some or all of them may be required in particular implementations or contexts of use.

Log in to download

Get The Data

  • The data in CSV format DOWNLOAD
  • Metadata in Human Readable format (PDF) DOWNLOAD
  • Metadata in Machine Readable format (JSON) DOWNLOAD
Your Data License
  • Research
    Non-Commercial, Share-Alike, Attribution Free Forever
  • Commercial
    Commercial Use, Remix & Adapt, White Label Buy Subscription


The meta indicates the metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. The RESTful application program interface (API) defines some Operations that provide direct read and write access to the meta element.

Metadata types are a set of types for use with metadata resources. 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, last updated 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

The Metadata types include:
– Contact Detail
– Contributor
– Data Requirement
– Expression
– Parameter Definition
– Related Artifact
– Trigger Definition
– Usage Context

About this Dataset

Data Info

Date Created


Last Modified




Update Frequency


Temporal Coverage


Spatial Coverage

United States


John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements


Source Citation



FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Meta Datatype, Electronic Health Records Exchange Through FHIR

Data Fields

Name Description Type Constraints
Concept_NameName of the concept in the FHIR structure.stringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-

Data Preview

Concept NameComputer Ready NameTypeDollar RefDescriptionItems
Metaid#/definitions/stringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
MetaextensionarrayMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension there is a set of requirements that SHALL be met as part of the definition of the extension.{'$ref': '#/definitions/Extension'}
MetaversionId#/definitions/idThe version specific identifier as it appears in the version portion of the URL. This value changes when the resource is created updated or deleted.
Meta_versionId#/definitions/ElementExtensions for versionId
MetalastUpdated#/definitions/instantWhen the resource last changed - e.g. when the version changed.
Meta_lastUpdated#/definitions/ElementExtensions for lastUpdated
Metasource#/definitions/uriA uri that identifies the source system of the resource. This provides a minimal amount of [[[Provenance]]] information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server document message database
Meta_source#/definitions/ElementExtensions for source
MetaprofilearrayA list of profiles (references to [[[StructureDefinition]]] resources) that this resource claims to conform to. The URL is a reference to [[[StructureDefinition.url]]].{'$ref': '#/definitions/canonical'}
MetasecurityarraySecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.{'$ref': '#/definitions/Coding'}