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

Condition recordedDate (first) and recorder (last) definitions are not aligned

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Care
    • Condition
    • Hide

      1. Update the comment on recordedDate 

      • Comment:  When onset date is unknown, recordedDate can be used to establish if the condition was present on or before a given date.  If the recordedDate is known and provided by a sending system, it is preferred that the receiving system preserve that recordedDate value. If the recordedDate is not provided by the sending system, the receipt timestamp is sometimes used as the recordedDate.  By contrast, the recorder is the most recent author. 

      2. Add comment to recorder 

      • Comment:  Because the <recorder> takes responsibility for accurately recording information in the record, the <recorder> is the most recent author.  The <recorder> may or may not be the asserter.  By contrast, the recordedDate is when the condition was first recorded
      Show
      1. Update the comment on  recordedDate   Comment :  When onset date is unknown, recordedDate can be used to establish if the condition was present on or before a given date.  If the recordedDate is known and provided by a sending system, it is preferred that the receiving system preserve that recordedDate value. If the recordedDate is not provided by the sending system, the receipt timestamp is sometimes used as the recordedDate.  By contrast, the recorder is the most recent author .  2. Add comment to  recorder   Comment :  Because the <recorder> takes responsibility for accurately recording information in the record, the <recorder> is the most recent author.  The <recorder> may or may not be the asserter.  By contrast, the recordedDate is when the condition was first recorded
    • Larry McKnight / David Riddle : 5-0-0
    • Clarification
    • Non-substantive
    • R5

    Description

      Condition recordedDate and recorder definitions are not aligned

      • recordedDate prefers the FIRST (oldest) sending system's date 
      • recorder prefers the LAST (most recent) author who takes responsibility for the content

      Do we want to rename the elements since they aren't "paired" together as the names might imply?

      Per jlyle's email on 11/30/2021

      2020-06-10 MCC Care Plan Meeting - Patient Care - Confluence (hl7.org) created FHIR-27808 Clarification is needed on definition and use of RecordedDate - Jira (hl7.org), resulting in this text added to Recorded Date:

      "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."

      2020 Sept WGM Patient Care Agenda and Minutes - Patient Care - Confluence (hl7.org) clarified that the reason for this logic is that "recorded date [is a] proxy for the onset date," when onset date is not recorded.

       I.e., Recorded Date is the First recorded date. If transferring a record from one system to another, the original Recorded Date should persist, if available.

      The Recorder, however, is "Individual who recorded the record and takes responsibility for its content." If someone updates the record, that person is now the most knowledgeable, and should be the recorder.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: