2015May core #281 - but reference ranges are almost always specified as X1-X2 -this seems to demand a new syntax.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Retracted
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Orders & Observations
    • Observation
    • 4.20.4.2
    • Hide

      invarients are to prevent errors in implementation. Withdrawn on OO on FHIR call

      Show
      invarients are to prevent errors in implementation. Withdrawn on OO on FHIR call
    • Clarification

      Existing Wording: 4.20.4.2 Constraints (observation.html#4.20.4.2)

      obs-3: On Observation.referenceRange: Must have at least a low or a high or text (xpath on f:Observation/f:referenceRange:

      (exists(f:low) or exists(f:high)or exists(f:text)))

      obs-4: On Observation.referenceRange.low: Low range comparators can only be '>' or '>=' or empty (xpath on

      f:Observation/f:referenceRange/f:low: not(exists(f:comparator)) or boolean(f:comparator/@value = '<') or

      boolean(f:comparator/@value = '<='))

      obs-5: On Observation.referenceRange.high: High range comparators can only be '<' or '<=' or empty (xpath on

      f:Observation/f:referenceRange/f:high: not(exists(f:comparator)) or boolean(f:comparator/@value = '>') or

      boolean(f:comparator/@value = '>='))

      obs-6: Shall only be present if Observation.value[x] is not present (xpath: not(exists(f:dataAbsentReason)) or

      (not(exists(*[starts-with(local-name(.), 'value')]))))

      Comment:

      but reference ranges are almost always specified as X1-X2 -this seems to demand a new syntax.

            Assignee:
            Unassigned
            Reporter:
            clemmcdonald
            clemmcdonald
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: