Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4

Example ValueSet/definition-resource-types (XML)

Terminology Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Value SetDefinition Resource Types

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

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="definition-resource-types"/> 
  <meta> 
    <lastUpdated value="2023-03-26T15:21:02.749+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="extensions"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <ul> 
        <li> Include these codes as defined in 
          <a href="codesystem-fhir-types.html">
            <code> http://hl7.org/fhir/fhir-types</code> 
          </a> 
          <table class="none">
            <tr> 
              <td style="white-space:nowrap">
                <b> Code</b> 
              </td> 
              <td> 
                <b> Display</b> 
              </td> 
              <td> 
                <b> Definition</b> 
              </td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-ActivityDefinition">ActivityDefinition</a> 
              </td> 
              <td> ActivityDefinition</td> 
              <td> This resource allows for the definition of some activity to be performed, independent
                 of a particular patient, practitioner, or other performance context.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-ChargeItemDefinition">ChargeItemDefinition</a> 
              </td> 
              <td> ChargeItemDefinition</td> 
              <td> The ChargeItemDefinition resource provides the properties that apply to the (billing)
                 codes necessary to calculate costs and prices. The properties may differ largely
                 depending on type and realm, therefore this resource gives only a rough structure
                 and requires profiling for each type of billing code system.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-ClinicalUseDefinition">ClinicalUseDefinition</a> 
              </td> 
              <td> ClinicalUseDefinition</td> 
              <td> A single issue - either an indication, contraindication, interaction or an undesirable
                 effect for a medicinal product, medication, device or procedure.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-EventDefinition">EventDefinition</a> 
              </td> 
              <td> EventDefinition</td> 
              <td> The EventDefinition resource provides a reusable description of when a particular
                 event can occur.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-Measure">Measure</a> 
              </td> 
              <td> Measure</td> 
              <td> The Measure resource provides the definition of a quality measure.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-MessageDefinition">MessageDefinition</a> 
              </td> 
              <td> MessageDefinition</td> 
              <td> Defines the characteristics of a message that can be shared between systems, including
                 the type of event that initiates the message, the content to be transmitted and
                 what response(s), if any, are permitted.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-ObservationDefinition">ObservationDefinition</a> 
              </td> 
              <td> ObservationDefinition</td> 
              <td> Set of definitional characteristics for a kind of observation or measurement produced
                 or consumed by an orderable health care service.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-OperationDefinition">OperationDefinition</a> 
              </td> 
              <td> OperationDefinition</td> 
              <td> A formal computable definition of an operation (on the RESTful interface) or a
                 named query (using the search interaction).</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-PlanDefinition">PlanDefinition</a> 
              </td> 
              <td> PlanDefinition</td> 
              <td> This resource allows for the definition of various types of plans as a sharable,
                 consumable, and executable artifact. The resource is general enough to support
                 the description of a broad range of clinical and non-clinical artifacts such as
                 clinical decision support rules, order sets, protocols, and drug quality specifications.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-Questionnaire">Questionnaire</a> 
              </td> 
              <td> Questionnaire</td> 
              <td> A structured set of questions intended to guide the collection of answers from
                 end-users. Questionnaires provide detailed control over order, presentation, phraseology
                 and grouping to allow coherent, consistent data collection.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-Requirements">Requirements</a> 
              </td> 
              <td> Requirements</td> 
              <td> The Requirements resource is used to describe an actor - a human or an application
                 that plays a role in data exchange, and that may have obligations associated with
                 the role the actor plays.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-SubscriptionTopic">SubscriptionTopic</a> 
              </td> 
              <td> SubscriptionTopic</td> 
              <td> Describes a stream of resource state changes identified by trigger criteria and
                 annotated with labels useful to filter projections from this topic.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-TestPlan">TestPlan</a> 
              </td> 
              <td> TestPlan</td> 
              <td> A plan for executing testing on an artifact or specifications</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-fhir-types.html#fhir-types-TestScript">TestScript</a> 
              </td> 
              <td> TestScript</td> 
              <td> A structured set of tests against a FHIR server or client implementation to determine
                 compliance against the FHIR specification.</td> 
            </tr> 
          </table> 
        </li> 
      </ul> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="normative"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="5"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/definition-resource-types"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.3.1056"/> 
  </identifier> 
  <version value="5.0.0"/> 
  <name value="DefinitionResourceTypes"/> 
  <title value="Definition Resource Types"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2023-03-26T15:21:02+11: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="All Resource Types that represent definition resources"/> 
  <jurisdiction> 
    <coding> 
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> 
      <code value="001"/> 
      <display value="World"/> 
    </coding> 
  </jurisdiction> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://hl7.org/fhir/fhir-types"/> 
      <concept> 
        <code value="ActivityDefinition"/> 
      </concept> 
      <concept> 
        <code value="ChargeItemDefinition"/> 
      </concept> 
      <concept> 
        <code value="ClinicalUseDefinition"/> 
      </concept> 
      <concept> 
        <code value="EventDefinition"/> 
      </concept> 
      <concept> 
        <code value="Measure"/> 
      </concept> 
      <concept> 
        <code value="MessageDefinition"/> 
      </concept> 
      <concept> 
        <code value="ObservationDefinition"/> 
      </concept> 
      <concept> 
        <code value="OperationDefinition"/> 
      </concept> 
      <concept> 
        <code value="PlanDefinition"/> 
      </concept> 
      <concept> 
        <code value="Questionnaire"/> 
      </concept> 
      <concept> 
        <code value="Requirements"/> 
      </concept> 
      <concept> 
        <code value="SubscriptionTopic"/> 
      </concept> 
      <concept> 
        <code value="TestPlan"/> 
      </concept> 
      <concept> 
        <code value="TestScript"/> 
      </concept> 
    </include> 
  </compose> 
</ValueSet> 

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.