Cross-Version Extension for Observation.dataAbsentReason in R4

Context of Use

This extension may be used in the following contexts:

Name	Flags	Card.	Type	Description & Constraints
Extension		0..1	Extension	Why the result is missing
extension		..0
value[x]		1..	CodeableConcept
url				"http://hl7.org/fhir/4.0/StructureDefinition/extension-Observation.dataAbsentReason"
Documentation for this format

{
  "resourceType" : "StructureDefinition",
  "id" : "xv-r4-obs.dataAbsentReason",
  "url" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-Observation.dataAbsentReason",
  "name" : "XVerExtensionObservation.dataAbsentReasonR4",
  "title" : "Cross-Version Extension for Observation.dataAbsentReason in R4",
  "status" : "active",
  "experimental" : false,
  "publisher" : "Health Level Seven International (Orders and Observations)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    }]
  },
  {
    "telecom" : [{
      "system" : "url",
      "value" : "http://www.hl7.org/Special/committees/orders/index.cfm"
    }]
  }],
  "description" : "Cross-Version Extension for Observation.dataAbsentReason. Valid in versions R2, R3\r\n\r\nThis is a valid extension because it has the following codes that are not in other versions not-permitted, not-applicable (http://terminology.hl7.org/CodeSystem/data-absent-reason)",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001"
    }]
  }],
  "fhirVersion" : "5.0.0",
  "kind" : "complex-type",
  "abstract" : false,
  "type" : "Extension",
  "baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Extension",
  "derivation" : "constraint",
  "differential" : {
    "element" : [{
      "path" : "Extension",
      "short" : "Why the result is missing",
      "definition" : "Provides a reason why the expected value in the element Observation.value[x] is missing.",
      "comment" : "Null or exceptional values can be represented two ways in FHIR Observations.  One way is to simply include them in the value set and represent the exceptions in the value.  For example, measurement values for a serology test could be  \"detected\", \"not detected\", \"inconclusive\", or  \"specimen unsatisfactory\".   \n\nThe alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values.  For example, the dataAbsentReason code \"error\" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0.  Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.",
      "requirements" : "For many results it is necessary to handle exceptional values in measurements.",
      "min" : 0,
      "max" : "1",
      "isModifier" : false,
      "mapping" : [{
        "identity" : "v2",
        "map" : "N/A"
      },
      {
        "identity" : "rim",
        "map" : "value.nullFlavor"
      }]
    },
    {
      "path" : "Extension.extension",
      "max" : "0"
    },
    {
      "path" : "Extension.value[x]",
      "min" : 1,
      "type" : [{
        "code" : "CodeableConcept"
      }]
    },
    {
      "path" : "Extension.url",
      "fixedUri" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-Observation.dataAbsentReason"
    }]
  }
}