Prevent conflicts between Condition.clinicalStatus and Condition.abatement - 2016-09 core #313

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium

      Comment:

      There is no invariant constraint in the Condition resource to prevent conflicting information to be entered for Condition.clinicalStatus value and Condition.Abatement values

      Consequence: the Condition.clincalStatus value may = active

      Condition.Abatement may contain a dateTime value, or a "yes" boolean value

      Include a variant value to constrain the Condition.clinicalStatus and Condition.Abatement values to disallow conflicting values between these two elements

      Summary:

      Prevent conflicts between Condition.clinicalStatus and Condition.abatement

            Assignee:
            Unassigned
            Reporter:
            Stephen Chu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: