Condition.onset from 0..1 to 0..* - 2016-09 core #311

XMLWordPrintableJSON

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

      onsetDateTime can be used to convey 1972 - if year is all that is known

      onsetString can be used to convey edge use cases like "2-4 months in 1972" - doesn't need to be computable since the exact dates aren't known

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

      Show
      onsetDateTime can be used to convey 1972 - if year is all that is known onsetString can be used to convey edge use cases like "2-4 months in 1972" - doesn't need to be computable since the exact dates aren't known Resource history/versioning can be used to track multiple onset periods.
    • Viet/Larry: 12-0-1
    • Enhancement

      Comment:

      Condition.onset cardinality = 0..1 and Condition.onset.onsetRange can be used to express value such as 2-4 months. But due to cardinality constraint, it is not possible to state that the onset year = 1972

      Use case - patient vaguely remembers that the condition occured in 1972 over 2-4 months and canot remember which months

      Relax cardinality to 0..*

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

      Summary:

      Condition.onset from 0..1 to 0..*

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

              Created:
              Updated:
              Resolved: