### ----------------------------------------------------
### -- FHIR
### -- Licenses: Artistic-2.0
### -- Authors: Hugh Simpson
### -- File: t/resources/structureDefinition/observation.json
### ----------------------------------------------------
### -- Chunk 16 of 16
": "1",
        "type": [
          {
            "code": "Quantity"
          },
          {
            "code": "CodeableConcept"
          },
          {
            "code": "string"
          },
          {
            "code": "boolean"
          },
          {
            "code": "integer"
          },
          {
            "code": "Range"
          },
          {
            "code": "Ratio"
          },
          {
            "code": "SampledData"
          },
          {
            "code": "time"
          },
          {
            "code": "dateTime"
          },
          {
            "code": "Period"
          }
        ],
        "isSummary": true,
        "mapping": [
          {
            "identity": "sct-concept",
            "map": "363714003 |Interprets| < 441742003 |Evaluation finding|"
          },
          {
            "identity": "v2",
            "map": "OBX.2, OBX.5, OBX.6"
          },
          {
            "identity": "rim",
            "map": "value"
          },
          {
            "identity": "sct-attr",
            "map": "363714003 |Interprets|"
          }
        ]
      },
      {
        "id": "Observation.component.dataAbsentReason",
        "path": "Observation.component.dataAbsentReason",
        "short": "Why the component result is missing",
        "definition": "Provides a reason why the expected value in the element Observation.component.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  \"test not done\". \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.  Because of these options, use-case agreements are required to interpret general observations for exceptional values.",
        "requirements": "For many results it is necessary to handle exceptional values in measurements.",
        "min": 0,
        "max": "1",
        "type": [
          {
            "code": "CodeableConcept"
          }
        ],
        "condition": [
          "obs-6"
        ],
        "binding": {
          "extension": [
            {
              "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName",
              "valueString": "ObservationValueAbsentReason"
            }
          ],
          "strength": "extensible",
          "description": "Codes specifying why the result (`Observation.value[x]`) is missing.",
          "valueSet": "http://hl7.org/fhir/ValueSet/data-absent-reason"
        },
        "mapping": [
          {
            "identity": "v2",
            "map": "N/A"
          },
          {
            "identity": "rim",
            "map": "value.nullFlavor"
          }
        ]
      },
      {
        "id": "Observation.component.interpretation",
        "path": "Observation.component.interpretation",
        "short": "High, low, normal, etc.",
        "definition": "A categorical assessment of an observation value.  For example, high, low, normal.",
        "comment": "Historically used for laboratory results (known as 'abnormal flag' ),  its use extends to other use cases where coded interpretations  are relevant.  Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.",
        "requirements": "For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.",
        "alias": [
          "Abnormal Flag"
        ],
        "min": 0,
        "max": "*",
        "type": [
          {
            "code": "CodeableConcept"
          }
        ],
        "binding": {
          "extension": [
            {
              "url": "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName",
              "valueString": "ObservationInterpretation"
            }
          ],
          "strength": "extensible",
          "description": "Codes identifying interpretations of observations.",
          "valueSet": "http://hl7.org/fhir/ValueSet/observation-interpretation"
        },
        "mapping": [
          {
            "identity": "sct-concept",
            "map": "< 260245000 |Findings values|"
          },
          {
            "identity": "v2",
            "map": "OBX-8"
          },
          {
            "identity": "rim",
            "map": "interpretationCode"
          },
          {
            "identity": "sct-attr",
            "map": "363713009 |Has interpretation|"
          }
        ]
      },
      {
        "id": "Observation.component.referenceRange",
        "path": "Observation.component.referenceRange",
        "short": "Provides guide for interpretation of component result",
        "definition": "Guidance on how to interpret the value by comparison to a normal or recommended range.",
        "comment": "Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.",
        "requirements": "Knowing what values are considered \"normal\" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.",
        "min": 0,
        "max": "*",
        "contentReference": "#Observation.referenceRange",
        "mapping": [
          {
            "identity": "v2",
            "map": "OBX.7"
          },
          {
            "identity": "rim",
            "map": "outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]"
          }
        ]
      }
    ]
  }
}


