DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Valueset-message-significance-category.xml

Raw XML (canonical form)

Definition for Value SetMessageSignificanceCategory

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="message-significance-category"/>
  <meta>
    <lastUpdated value="2015-10-24T07:41:03.495+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>MessageSignificanceCategory</h2>
      <p>The impact of the content of a message.</p>
      <p>This value set has an inline code system http://hl7.org/fhir/message-significance-category,
         which defines the following codes:</p>
      <table class="codes">
        <tr>
          <td>
            <b>Code</b>
          </td>
          <td>
            <b>Display</b>
          </td>
          <td>
            <b>Definition</b>
          </td>
        </tr>
        <tr>
          <td>Consequence
            <a name="Consequence"> </a>
          </td>
          <td>Consequence</td>
          <td>The message represents/requests a change that should not be processed more than once;
             e.g. Making a booking for an appointment.</td>
        </tr>
        <tr>
          <td>Currency
            <a name="Currency"> </a>
          </td>
          <td>Currency</td>
          <td>The message represents a response to query for current information. Retrospective processing
             is wrong and/or wasteful.</td>
        </tr>
        <tr>
          <td>Notification
            <a name="Notification"> </a>
          </td>
          <td>Notification</td>
          <td>The content is not necessarily intended to be current, and it can be reprocessed, though
             there may be version issues created by processing old notifications.</td>
        </tr>
      </table>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.4.642.2.88"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/message-significance-category"/>
  <version value="1.0.2"/>
  <name value="MessageSignificanceCategory"/>
  <status value="draft"/>
  <experimental value="false"/>
  <publisher value="HL7 (FHIR Project)"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="fhir@lists.hl7.org"/>
    </telecom>
  </contact>
  <date value="2015-10-24T07:41:03+11:00"/>
  <description value="The impact of the content of a message."/>
  <codeSystem>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
      <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.88"/>
    </extension>
    <system value="http://hl7.org/fhir/message-significance-category"/>
    <version value="1.0.2"/>
    <caseSensitive value="true"/>
    <concept>
      <code value="Consequence"/>
      <display value="Consequence"/>
      <definition value="The message represents/requests a change that should not be processed more than once;
       e.g. Making a booking for an appointment."/>
    </concept>
    <concept>
      <code value="Currency"/>
      <display value="Currency"/>
      <definition value="The message represents a response to query for current information. Retrospective processing
       is wrong and/or wasteful."/>
    </concept>
    <concept>
      <code value="Notification"/>
      <display value="Notification"/>
      <definition value="The content is not necessarily intended to be current, and it can be reprocessed, though
       there may be version issues created by processing old notifications."/>
    </concept>
  </codeSystem>
</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.