FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example CodeSystem/observation-triggeredbytype (JSON)

Orders and Observations Work GroupMaturity Level: N/AStandards Status: Informative

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

Definition for Code SystemTriggeredBytype

{
  "resourceType" : "CodeSystem",
  "id" : "observation-triggeredbytype",
  "meta" : {
    "lastUpdated" : "2024-03-27T22:56:58.316+11:00",
    "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablecodesystem"]
  },
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>This case-sensitive code system <code>http://hl7.org/fhir/observation-triggeredbytype</code> defines the following codes in a Is-A heirarchy:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style=\"white-space:nowrap\">reflex<a name=\"observation-triggeredbytype-reflex\"> </a></td><td>Reflex</td><td>Performance of one or more other tests depending on the results of the initial test.  This may include collection of additional specimen. While a new ServiceRequest is not required to perform the additional test, where it is still needed (e.g., requesting another laboratory to perform the reflex test), the Observation.basedOn would reference the new ServiceRequest that requested the additional test to be performed as well as the original ServiceRequest to reflect the one that provided the authorization.</td></tr><tr><td style=\"white-space:nowrap\">repeat<a name=\"observation-triggeredbytype-repeat\"> </a></td><td>Repeat (per policy)</td><td>Performance of the same test again with the same parameters/settings/solution.</td></tr><tr><td style=\"white-space:nowrap\">re-run<a name=\"observation-triggeredbytype-re-run\"> </a></td><td>Re-run (per policy)</td><td>Performance of the same test but with different parameters/settings/solution.</td></tr></table></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "oo"
  }],
  "url" : "http://hl7.org/fhir/observation-triggeredbytype",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.4.2098"
  }],
  "version" : "6.0.0-cibuild",
  "name" : "TriggeredBytype",
  "title" : "triggered Bytype",
  "status" : "active",
  "experimental" : true,
  "date" : "2022-03-16T16:55:11+11:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "Codes providing the triggeredBy type of observation.",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001",
      "display" : "World"
    }]
  }],
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/observation-triggeredbytype",
  "hierarchyMeaning" : "is-a",
  "content" : "complete",
  "concept" : [{
    "code" : "reflex",
    "display" : "Reflex",
    "definition" : "Performance of one or more other tests depending on the results of the initial test.  This may include collection of additional specimen. While a new ServiceRequest is not required to perform the additional test, where it is still needed (e.g., requesting another laboratory to perform the reflex test), the Observation.basedOn would reference the new ServiceRequest that requested the additional test to be performed as well as the original ServiceRequest to reflect the one that provided the authorization."
  },
  {
    "code" : "repeat",
    "display" : "Repeat (per policy)",
    "definition" : "Performance of the same test again with the same parameters/settings/solution."
  },
  {
    "code" : "re-run",
    "display" : "Re-run (per policy)",
    "definition" : "Performance of the same test but with different parameters/settings/solution."
  }]
}

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.