Condition.abatement from 0..1 to 0..* - 2016-09 core #312

XMLWordPrintableJSON

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

      abatementString can be used to convey edge use cases like 2-4 months in 1985 (when date is not known)

      abatementPeriod can be used to convey specific dates in 1985 (e.g. 1/1/1985 through 4/1/2985)

      Resource history/versioning can be used to track multiple abatement periods.

      Show
      abatementString can be used to convey edge use cases like 2-4 months in 1985 (when date is not known) abatementPeriod can be used to convey specific dates in 1985 (e.g. 1/1/1985 through 4/1/2985) Resource history/versioning can be used to track multiple abatement periods.
    • David/Josh: 19-0-0
    • Enhancement

      Comment:

      Condition.abatement cardinality = 0..1 does not support entry of abatement value = 2-4 months and abatement date = 1985

      Samilar use case as Condition.onset. onsetRange

      Relax cardinality to 0..*

      Include implementation guideline to disallow/discourage entry of another value which may be accurately derived from another, e.g. only abatementDateTime or abatement.Age and not both

      Summary:

      Condition.abatement from 0..1 to 0..*

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

              Created:
              Updated:
              Resolved: