Remove clinicalStatus requirement constraint - STU #31

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • Condition
    • 9.2.3.2 Constraints
    • Hide
      • Condition.category 0..* with extensible binding to a value set with problem-list-item and encounter-diagnosis
        * Change *con-3 *invariant to require clinicalStatus when not entered-in-error AND (none of categories are encounter-diagnosis OR one of the categories is problem-list-item)
      Show
      Condition.category 0..* with extensible binding to a value set with problem-list-item and encounter-diagnosis * Change *con-3 *invariant to require clinicalStatus when not entered-in-error AND (none of categories are encounter-diagnosis OR one of the categories is problem-list-item)
    • Danielle/Corey: 7-1-1
    • Correction
    • Non-compatible
    • STU3

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

      Comment:

      This constraint is problematic in the event that the condition 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: