Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-25514

The ait-1 invariant requires populating clinicalStatus which is not appropriate for "no known" allergy cases.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Patient Care
    • AllergyIntolerance
    • Hide

      Removing the ait-1 invariant.

      Add a comment that says:  AllergyIntolerance.clinicalStatus should be present if verificationStatus is not entered-in-error and the AllergyIntolerance.code isn't negated (No Known Allergy, No Drug Allergy, No Food Allergy, No Latex Allergy).

      Show
      Removing the ait-1 invariant. Add a comment that says:  AllergyIntolerance.clinicalStatus should be present if verificationStatus is not entered-in-error and the AllergyIntolerance.code isn't negated (No Known Allergy, No Drug Allergy, No Food Allergy, No Latex Allergy).
    • Stephen Chu/Thom Kuhn: 4-0-1
    • Enhancement
    • Non-compatible
    • R5

    Description

      The ait-1 invariant requires that the clinicalStatus element must be populated if verificationStatus is not 'entered-in-error'.  But populating clinicalStatus is not appropriate when representing cases of "no known" allergy, as something that is "not known" can neither be clinically "active" or "inactive".  If a "record status" element (e.g. AllergyIntolerance.status) element was available it could be populated in these cases, but currently that does not exist in the resource. 

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhausam Robert Hausam
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: