Handling spurious allergy records - 2016-09 core #43

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Care
    • AllergyIntolerance
    • 9.1.3 allergy
    • Hide

      DetectedIssue should be used to represent any warnings or alerts (e.g. proposed therapy may cause an adverse reaction based on a documented allergy intolerance).

      The elements to support a process to update the AllergyIntolerance resource after an alert or DetectedIssue was overridden is outside of the scope of the AllergyIntolerance resource structure.

      Show
      DetectedIssue should be used to represent any warnings or alerts (e.g. proposed therapy may cause an adverse reaction based on a documented allergy intolerance). The elements to support a process to update the AllergyIntolerance resource after an alert or DetectedIssue was overridden is outside of the scope of the AllergyIntolerance resource structure.
    • Elaine/Viet: 8-0-0
    • Enhancement

      Comment:

      WRT the high proportion of spurious allergy records, a useful distinction might be, in the allergy record, whether a warning has been overridden as incorrect (in which case it should be marked "refuted"--possibly with some delay or confirmation step) or as "acknowledged; will monitor" (in which case criticality should be "low").

      Summary:

      Handling spurious allergy records

            Assignee:
            Unassigned
            Reporter:
            Jay Lyle
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: