Explain how to achieve the behavior or "valueBoolean" for Observations

XMLWordPrintableJSON

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

      Agree to add to notes see #7547 and explanation why choosing code over bool ( most obs are never really bool due to exceptional values so code always work and bool rarely) as well as link to appropriate value set /v2/0136/index.html

      Show
      Agree to add to notes see #7547 and explanation why choosing code over bool ( most obs are never really bool due to exceptional values so code always work and bool rarely) as well as link to appropriate value set /v2/0136/index.html
    • Eric Haas /Patrick Loyd:10-4-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      The issue of whether Observation.valueBoolean is needed has come up before. I think it would be useful, but if we're not going to define this field, then we should at least explain why in http://hl7-fhir.github.io/observation.html, and we should link to an appropriate ValueSet that can be used to simulate this behavior with Observation.valueCodeableConcept

            Assignee:
            Unassigned
            Reporter:
            Josh Mandel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: