Allergy Intolerance example for UNKNOWN allergy status does not use unknown

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • 3.2.0 [deprecated]
    • Cross-Group Projects
    • AllergyIntolerance Example
      USCore [deprecated]
    • Examples
    • Hide

      Update:
      If a patient has not been asked about their allergies, this would be represented as:
      AllergyIntolerance.code = “716186003” (No known allergy (situation))
      AllergyIntolerance.verificationStatus = “unconfirmed”

      TO
      If a patient has not been asked about their allergies, this would be represented as:
      AllergyIntolerance.code = “1631000175102" Patient not asked
      AllergyIntolerance.verificationStatus = “unconfirmed” or empty

      Show
      Update: If a patient has not been asked about their allergies, this would be represented as: AllergyIntolerance.code = “716186003” (No known allergy (situation)) AllergyIntolerance.verificationStatus = “unconfirmed” TO If a patient has not been asked about their allergies, this would be represented as: AllergyIntolerance.code = “1631000175102" Patient not asked AllergyIntolerance.verificationStatus = “unconfirmed” or empty
    • Rob McClure/Russ Leftwich: 12-0-1
    • Correction
    • Non-compatible

      The allergy status unknown example:
      If a patient has not been asked about their allergies, this would be represented as:

      AllergyIntolerance.code = “716186003” (No known allergy (situation))

      AllergyIntolerance.verificationStatus = “unconfirmed”

      I'm surprised this is the decision. I suggest the justification for this approach, and to not use "UNKNOWN" in some form, needs to be provided via a link to either the discussion, JIRA, or something.

        1. image-2021-04-08-12-41-56-632.png
          37 kB
          Cooper Thompson

            Assignee:
            Unassigned
            Reporter:
            Rob McClure
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: