2015May core #576 - Differentiate "doesn't have" from "refuted"

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Very Low
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • Extensibility
    • 1.16.0.2
    • Hide

      Modify the example to:

      Using the Condition resource to record an assertion that the patient has a family history of the condition rather than the condition itself.

      Show
      Modify the example to: Using the Condition resource to record an assertion that the patient has a family history of the condition rather than the condition itself.
    • Russ/Rob: 7-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: Using the Condition resource to record an assertion that a patient doesn't have a particular diagnosis (as opposed to refuted)

      Proposed Wording: Using the Condition resource to record an assertion that a patient doesn't have a [particular diagnosis (as opposed to refuted). [Explain the subtle difference between "doesn't have" and "refuted"…]

      Comment:

      This is an example where I thought that the resource-specific elements would make it unnecessary to define a modifier extension for a common clinical case. But when I look in 1.23.2.1.1848.1 at the definition, "refuted – This condition has been ruled out by diagnostic and clinical evidence." That sounds essentially the same as "We assert that the patient doesn't have this condition." The difference is too subtle. I wouldn't want someone defining the modifier extension if they could have used "refuted" from the core.

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

              Created:
              Updated:
              Resolved: