Remove clinicalStatus requirement constraint - STU #29

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • AllergyIntolerance
    • 9.1.3.2 Constraints
    • Hide

      Keep the invariant, but add a comment saying

      "Refer to http://build.fhir.org/extensibility.html#Special-Case if clincalStatus is missing data."

      Show
      Keep the invariant, but add a comment saying "Refer to http://build.fhir.org/extensibility.html#Special-Case if clincalStatus is missing data."
    • Steven/Mike: 10-0-0
    • Non-substantive
    • STU3

      Existing Wording: AllergyIntolerance.clinicalStatus SHALL be present if verificationStatus is not entered-in-error.

      Comment:

      This constraint is problematic in the event that the allergy was communicated in a means besides FHIR (entered directly into a system, HL7 message, etc. It would mean that this allergyIntolerance cannot be communicated if the current status is unknown. This could be problematic, especially in the case of a severe allergy. This constraint should be removed.

      Summary:

      Remove clinicalStatus requirement constraint

            Assignee:
            Unassigned
            Reporter:
            corey_spears#1
            corey_spears#1
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: