2015May core #1179 - Condition.dateAsserted definition clarification

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • Condition
    • 4.3.6
    • Hide

      rename "assertedDate" to "recordedDate"

      Change definition to:

      "Date the Condition statement was documented"

      Show
      rename "assertedDate" to "recordedDate" Change definition to: "Date the Condition statement was documented"
    • Viet/Emma: 7-0-1
    • Clarification
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: Condition.dateAsserted = Estimated or actual date the condition/problem/diagnosis was first detected/suspected

      Additional URL: http://hl7.org/fhir/2015May/condition-definitions.html#Condition.onset_x

      Condition.onset = Estimated or actual date or date-time the condition began, in the opinion of the clinician

      Proposed Wording: Condition.dateAsserted = date the condition/problem/diagnosis was first documented

      Comment:

      The definition of Condition.dateAsserted overlaps with Condition.onset, which raises questions about whether the dateAsserted is the when.recorded or when.init. The http://hl7-fhir.github.io/w5.html implies that condition.dateAsserted is aligned with when.recorded, yet the definition reads as if it is when.init. Update definition to reflect that the dateAsserted is aligned with when the condition was first recorded. Also, the Condition.asserter (who.author) should be consistent with the Condition.dateAsserted (when.recorded)

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

              Created:
              Updated:
              Resolved: