Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-33180

Further clarify boundaries between Condition assertedDate (extension) and recordedDate

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Extensions Pack (FHIR)
    • Patient Care
    • Condition Asserted Date
    • Hide

      Update HL7.FHIR.UV.EXTENSIONS\Condition Asserted Date - FHIR v5.0.0 definition to be "When the asserter identified the condition, problem, or diagnosis or other event, situation, issue, or clinical concept that may have risen to a level of or remains a concern.  For example, when the patient experiences chest pain, the asserted date represents when the clinician began following the chest pain - not when the patient experienced the chest pain.  Asserted date supports the recognition that information is not always entered in a system immediately.  Assertion and recording are different acts, so asserted date and recorded date are semantically different. However, they may be the same date and close in time.  If this difference is significant for your use case, assertion date may be useful.

      Show
      Update  HL7.FHIR.UV.EXTENSIONS\Condition Asserted Date - FHIR v5.0.0  definition to be "When the asserter identified the condition, problem, or diagnosis or other event, situation, issue, or clinical concept that may have risen to a level of or remains a concern.  For example, when the patient experiences chest pain, the asserted date represents when the clinician began following the chest pain - not when the patient experienced the chest pain.  Asserted date supports the recognition that information is not always entered in a system immediately.  Assertion and recording are different acts, so asserted date and recorded date are semantically different. However, they may be the same date and close in time.  If this difference is significant for your use case, assertion date may be useful.
    • Jay Lyle / Emma Jones : 6-0-0
    • Clarification
    • Non-substantive

    Description

      Clarify the boundaries between http://build.fhir.org/extension-condition-asserteddate.html given we updated Condition.recordedDate (per  FHIR-27808)

      If the recordedDate is known via a sending system, it is preferred that the receiving system preserve the date. If the recorded date is not provided by the sending system, it is acceptable for the receiving system to assert their system-generated date.

      Perhaps an example would help illustrate:

      assertedDate is when a human makes the assertion (when.done), but recordedDate is when recorded in the system (e.g. there can be a delay between when assertion is made and when it gets documented and entered in the system)

      Attachments

        Activity

          People

            Unassigned Unassigned
            michelle.m.miller Michelle Miller
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: