STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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

Codesystem-message-significance-category.json

Raw JSON (canonical form)

Definition for Code System MessageSignificanceCategory

{
  "resourceType": "CodeSystem",
  "id": "message-significance-category",
  "meta": {
    "lastUpdated": "2016-12-06T12:22:34.981+11:00"
  },
  "text": {
    "status": "generated",
    "div": "<div>!-- Snipped for Brevity --></div>"
  },
  "url": "http://hl7.org/fhir/message-significance-category",
  "identifier": {
    "system": "urn:ietf:rfc:3986",
    "value": "urn:oid:2.16.840.1.113883.4.642.1.88"
  },
  "version": "1.8.0",
  "name": "MessageSignificanceCategory",
  "status": "draft",
  "experimental": false,
  "publisher": "HL7 (FHIR Project)",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://hl7.org/fhir"
        },
        {
          "system": "email",
          "value": "fhir@lists.hl7.org"
        }
      ]
    }
  ],
  "date": "2016-12-06T12:22:34+11:00",
  "description": "The impact of the content of a message.",
  "caseSensitive": true,
  "valueSet": "http://hl7.org/fhir/ValueSet/message-significance-category",
  "content": "complete",
  "concept": [
    {
      "code": "Consequence",
      "display": "Consequence",
      "definition": "The message represents/requests a change that should not be processed more than once; e.g. Making a booking for an appointment."
    },
    {
      "code": "Currency",
      "display": "Currency",
      "definition": "The message represents a response to query for current information. Retrospective processing is wrong and/or wasteful."
    },
    {
      "code": "Notification",
      "display": "Notification",
      "definition": "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."
    }
  ]
}

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.