How to assert "looked for but not found"? - 2016-09 core #97

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • Observation
    • Hide

      Feb 2,2107 motion to defer and mark Not Persuasive.

      Eric Haas/Riki Merrick: 8-1-3

      --------------------------------------------------------------------------Motion to reopen and redisposition: Eric Haas/Robert Dieterle: 6-0-0

      Put the negative resutl in the value field ( e.g blood in urine --> negative). if there is an exceptional use the dataAbsentReason.

      see the comments for these fields whih discuss this.

      Show
      Feb 2,2107 motion to defer and mark Not Persuasive. Eric Haas/Riki Merrick: 8-1-3 --------------------------------------------------------------------------Motion to reopen and redisposition: Eric Haas/Robert Dieterle: 6-0-0 Put the negative resutl in the value field ( e.g blood in urine --> negative). if there is an exceptional use the dataAbsentReason. see the comments for these fields whih discuss this.
    • Eric Haas/Robert Dieterle: 6-0-0
    • Clarification

      Comment:

      How does one assert that the something was looked for but not found? e.g., no blood in the urine, no vision in the left eye? I don't think it's appropriate to punt this to terminology, as I don't believe any terminology system handles this fully

      Summary:

      How to assert "looked for but not found"?

            Assignee:
            Unassigned
            Reporter:
            Galen Mulrooney
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: