Rename AllergyIntolerance.type

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: High
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • STU
    • AllergyIntolerance
    • Hide

      We're revamping the value set to say "allergy", "intolerance" or "allergy and intolerance" (see 8313). We're not thrilled with "type", but it's consistent with what's used in other specs and none of the other names we could come up with are implementer-friendly or better. Will leave the name as it is.

      Show
      We're revamping the value set to say "allergy", "intolerance" or "allergy and intolerance" (see 8313). We're not thrilled with "type", but it's consistent with what's used in other specs and none of the other names we could come up with are implementer-friendly or better. Will leave the name as it is.
    • Russ/Rob: 8-0-0
    • Clarification

      In general, "type" is a confusing name for a property. In this case, the property appears to exist exclusively to communicate whether the mechanism of the allergy is immune vs. other. So it might make sense to call the field "mechanism" (with values of "immune | non-immune"), or just make it a boolean like "immuneCause".

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

              Created:
              Updated:
              Resolved: