Add Condition invariant, so abatement and clinicalStatus don't conflict

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Care
    • STU
    • Condition
    • Hide

      abatement.empty() or (abatement as boolean).not() or clinicalStatus='resolved' or clinicalStatus='remission' or clinicalStatus='inactive'

      xpath: not(f:abatementBoolean='true' or (not(exists(f:abatementBoolean)) and exists(*[starts-with(local-name(.), 'abatement')])) or f:clinicalStatus/@value=('resolved', 'remission', 'inactive')

      Add comment "When abatementString exists, it implies the condition is abated."

      Show
      abatement.empty() or (abatement as boolean).not() or clinicalStatus='resolved' or clinicalStatus='remission' or clinicalStatus='inactive' xpath: not(f:abatementBoolean='true' or (not(exists(f:abatementBoolean)) and exists(* [starts-with(local-name(.), 'abatement')] )) or f:clinicalStatus/@value=('resolved', 'remission', 'inactive') Add comment "When abatementString exists, it implies the condition is abated."
    • Stephen/Elaine: 6-0-0
    • Enhancement
    • Non-compatible
    • Yes
    • DSTU2

      Add Condition invariant, so abatement and clinicalStatus don't conflict

            Assignee:
            Unassigned
            Reporter:
            Michelle Miller
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: